From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>,
"Luca Coelho" <luciano.coelho@intel.com>
Subject: Re: [PATCH v2 1/3] drm/i915/dmc_wl: Extract intel_dmc_wl_flush_release_work()
Date: Fri, 29 Nov 2024 13:25:14 -0500 [thread overview]
Message-ID: <Z0oHCjw8ElDRLLai@intel.com> (raw)
In-Reply-To: <20241129164010.29887-2-gustavo.sousa@intel.com>
On Fri, Nov 29, 2024 at 01:37:54PM -0300, Gustavo Sousa wrote:
> We will need to flush the release work from outside in an upcoming
> change. Let's put that into a public interface and call it
> intel_dmc_wl_flush_release_work().
>
> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dmc_wl.c | 12 +++++++++++-
> drivers/gpu/drm/i915/display/intel_dmc_wl.h | 1 +
> 2 files changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dmc_wl.c b/drivers/gpu/drm/i915/display/intel_dmc_wl.c
> index 853d75610489..09075830c12f 100644
> --- a/drivers/gpu/drm/i915/display/intel_dmc_wl.c
> +++ b/drivers/gpu/drm/i915/display/intel_dmc_wl.c
> @@ -349,7 +349,7 @@ void intel_dmc_wl_disable(struct intel_display *display)
> if (!__intel_dmc_wl_supported(display))
> return;
>
> - flush_delayed_work(&wl->work);
> + intel_dmc_wl_flush_release_work(display);
>
> spin_lock_irqsave(&wl->lock, flags);
>
> @@ -377,6 +377,16 @@ void intel_dmc_wl_disable(struct intel_display *display)
> spin_unlock_irqrestore(&wl->lock, flags);
> }
>
> +void intel_dmc_wl_flush_release_work(struct intel_display *display)
> +{
> + struct intel_dmc_wl *wl = &display->wl;
> +
> + if (!__intel_dmc_wl_supported(display))
> + return;
> +
> + flush_delayed_work(&wl->work);
> +}
> +
> void intel_dmc_wl_get(struct intel_display *display, i915_reg_t reg)
> {
> struct intel_dmc_wl *wl = &display->wl;
> diff --git a/drivers/gpu/drm/i915/display/intel_dmc_wl.h b/drivers/gpu/drm/i915/display/intel_dmc_wl.h
> index 147eeb4d8432..5488fbdf29b8 100644
> --- a/drivers/gpu/drm/i915/display/intel_dmc_wl.h
> +++ b/drivers/gpu/drm/i915/display/intel_dmc_wl.h
> @@ -32,6 +32,7 @@ struct intel_dmc_wl {
> void intel_dmc_wl_init(struct intel_display *display);
> void intel_dmc_wl_enable(struct intel_display *display, u32 dc_state);
> void intel_dmc_wl_disable(struct intel_display *display);
> +void intel_dmc_wl_flush_release_work(struct intel_display *display);
> void intel_dmc_wl_get(struct intel_display *display, i915_reg_t reg);
> void intel_dmc_wl_put(struct intel_display *display, i915_reg_t reg);
> void intel_dmc_wl_get_noreg(struct intel_display *display);
> --
> 2.47.0
>
next prev parent reply other threads:[~2024-11-29 18:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 16:37 [PATCH v2 0/3] Flush DMC wakelock release work at the end of runtime suspend Gustavo Sousa
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 [this message]
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=Z0oHCjw8ElDRLLai@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=luciano.coelho@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