Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 4/4] drm/i915/opregion: Flush asle_work during runtime suspend
Date: Wed, 8 Oct 2025 09:47:21 +0300	[thread overview]
Message-ID: <aOYI-cbvRVssZQ_L@ideak-desk> (raw)
In-Reply-To: <20250708160320.5653-4-ville.syrjala@linux.intel.com>

On Tue, Jul 08, 2025 at 07:03:20PM +0300, Ville Syrjala wrote:
> 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);

asle_work() -> asle_set_backlight() takes connection_mutex and
runtime_pm references can be taken with connection_mutex held, isn't
that a problem?

>  }
>  
>  void intel_opregion_unregister(struct intel_display *display)
> -- 
> 2.49.0
> 

  reply	other threads:[~2025-10-08  6:47 UTC|newest]

Thread overview: 9+ 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 ` [PATCH 4/4] drm/i915/opregion: Flush asle_work during runtime suspend Ville Syrjala
2025-10-08  6:47   ` Imre Deak [this message]
2025-07-08 18:29 ` ✓ i915.CI.BAT: success for series starting with [1/4] drm/i915/display: Disable wakeref asserts around GU_MISC irq handling Patchwork
2025-07-09  0:03 ` ✗ i915.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=aOYI-cbvRVssZQ_L@ideak-desk \
    --to=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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