Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: [PATCH 4/4] drm/i915/opregion: Flush asle_work during runtime suspend
Date: Tue,  8 Jul 2025 19:03:20 +0300	[thread overview]
Message-ID: <20250708160320.5653-4-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20250708160320.5653-1-ville.syrjala@linux.intel.com>

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

For good measure make sure asle_work has finished whatever it
was doing before we runtime suspend the device.

This probably isn't really necessary as long asle_work only
pokes at the mailbox as it should remain accessible even if
the device has been suspended. But seems better to play it
safe in case there is ever any need to do more stuff in
asle_work.

Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
 drivers/gpu/drm/i915/display/intel_opregion.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/i915/display/intel_opregion.c b/drivers/gpu/drm/i915/display/intel_opregion.c
index e99616ea2ae6..08d36411668d 100644
--- a/drivers/gpu/drm/i915/display/intel_opregion.c
+++ b/drivers/gpu/drm/i915/display/intel_opregion.c
@@ -1294,6 +1294,8 @@ void intel_opregion_runtime_suspend(struct intel_display *display)
 		 */
 		intel_opregion_notify_adapter(display, PCI_D1);
 	}
+
+	flush_work(&opregion->asle_work);
 }
 
 void intel_opregion_unregister(struct intel_display *display)
-- 
2.49.0


  parent reply	other threads:[~2025-07-08 16:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 16:03 [PATCH 1/4] drm/i915/display: Disable wakeref asserts around GU_MISC irq handling Ville Syrjala
2025-07-08 16:03 ` [PATCH 2/4] drm/i915/opregion: Extract intel_opregion_runtime_{suspend, resume}() Ville Syrjala
2025-10-08  6:40   ` Imre Deak
2025-07-08 16:03 ` [PATCH 3/4] drm/i915/opregion: Make intel_opregion_notify_adapter() static Ville Syrjala
2025-10-08  6:41   ` Imre Deak
2025-07-08 16:03 ` Ville Syrjala [this message]
2025-10-08  6:47   ` [PATCH 4/4] drm/i915/opregion: Flush asle_work during runtime suspend Imre Deak
2025-07-08 16:28 ` ✓ CI.KUnit: success for series starting with [1/4] drm/i915/display: Disable wakeref asserts around GU_MISC irq handling Patchwork
2025-07-08 16:43 ` ✗ CI.checksparse: warning " Patchwork
2025-07-08 17:06 ` ✓ Xe.CI.BAT: success " Patchwork
2025-07-08 18:54 ` ✓ Xe.CI.Full: " 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=20250708160320.5653-4-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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