Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: Luca Coelho <luciano.coelho@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH v2 0/3] Flush DMC wakelock release work at the end of runtime suspend
Date: Fri, 29 Nov 2024 13:37:53 -0300	[thread overview]
Message-ID: <20241129164010.29887-1-gustavo.sousa@intel.com> (raw)

We currently are not calling display runtime suspend functions when
D3cold is not allowed. That end up causing DMC wakelock to be enabled
because of dynamic DC states. Because of that, we need to make sure we
flush the release worker at the end of display runtime suspend.

v2:
  - Fixes for "drm/xe/display: Extract xe_display_pm_runtime_suspend_late()",
    see the patch changelog for details.

Gustavo Sousa (3):
  drm/i915/dmc_wl: Extract intel_dmc_wl_flush_release_work()
  drm/xe/display: Extract xe_display_pm_runtime_suspend_late()
  drm/xe/display: Flush DMC wakelock release work on runtime suspend

 drivers/gpu/drm/i915/display/intel_dmc_wl.c | 12 +++++++++++-
 drivers/gpu/drm/i915/display/intel_dmc_wl.h |  1 +
 drivers/gpu/drm/xe/display/xe_display.c     | 19 +++++++++++++++++++
 drivers/gpu/drm/xe/display/xe_display.h     |  2 ++
 drivers/gpu/drm/xe/xe_pm.c                  |  4 ++--
 5 files changed, 35 insertions(+), 3 deletions(-)

-- 
2.47.0


             reply	other threads:[~2024-11-29 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 16:37 Gustavo Sousa [this message]
2024-11-29 16:37 ` [PATCH v2 1/3] drm/i915/dmc_wl: Extract intel_dmc_wl_flush_release_work() Gustavo Sousa
2024-11-29 18:25   ` Rodrigo Vivi
2024-11-30 17:09     ` Rodrigo Vivi
2024-11-29 16:37 ` [PATCH v2 2/3] drm/xe/display: Extract xe_display_pm_runtime_suspend_late() Gustavo Sousa
2024-11-29 18:25   ` Rodrigo Vivi
2024-11-29 16:37 ` [PATCH v2 3/3] drm/xe/display: Flush DMC wakelock release work on runtime suspend Gustavo Sousa
2024-11-29 18:26   ` Rodrigo Vivi
2024-11-29 16:45 ` ✓ CI.Patch_applied: success for Flush DMC wakelock release work at the end of runtime suspend (rev2) Patchwork
2024-11-29 16:45 ` ✓ CI.checkpatch: " Patchwork
2024-11-29 16:46 ` ✓ CI.KUnit: " Patchwork
2024-11-29 17:04 ` ✓ CI.Build: " Patchwork
2024-11-29 17:07 ` ✓ CI.Hooks: " Patchwork
2024-11-29 17:08 ` ✗ CI.checksparse: warning " Patchwork
2024-11-29 17:27 ` ✓ Xe.CI.BAT: success " Patchwork
2024-11-30  3:01 ` ✗ Xe.CI.Full: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241129164010.29887-1-gustavo.sousa@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=luciano.coelho@intel.com \
    --cc=rodrigo.vivi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox