✓ CI.checkpatch: success for Flush DMC wakelock release work at the end of runtime suspend

[Patchwork]

== Series Details ==

Series: Flush DMC wakelock release work at the end of runtime suspend
URL   : https://patchwork.freedesktop.org/series/141931/
State : success

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 99f82964f289a34ab3ab1867a9eefb7109497ba0
Author: Gustavo Sousa <gustavo.sousa at intel.com>
Date:   Fri Nov 29 12:17:46 2024 -0300

    drm/xe/display: Flush DMC wakelock release work on runtime suspend
    
    We currently are not calling display runtime suspend functions when
    D3cold is not allowed. Because of that, we endup not disabling dynamic
    DC states (and do not go to DC9). With dynamic DC states enabled, we
    will also have DMC wakelock enabled. Since we use a delayed work to
    release the DMC wakelock, the work might get executed a little too late
    (after the PCI device has been put to D3hot) and we get a timeout
    warning ("DMC wakelock release timed out") because the MMIO for
    releasing the wakelock will be invalid after that point.
    
    To fix that, make sure we flush the release work at the end of
    xe_display_pm_runtime_suspend_late(). We can do that unconditionally
    because, if there is no pending work, that turns into a no-op.
    
    Signed-off-by: Gustavo Sousa <gustavo.sousa at intel.com>
+ /mt/dim checkpatch 108f610005f88de624c1a8c4f85d5cab9f530ddb drm-intel
71fd044ac240 drm/i915/dmc_wl: Extract intel_dmc_wl_flush_release_work()
c788111562b4 drm/xe/display: Extract xe_display_pm_runtime_suspend_late()
99f82964f289 drm/xe/display: Flush DMC wakelock release work on runtime suspend