From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dibin Moolakadan Subrahmanian
<dibin.moolakadan.subrahmanian@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jouni.hogander@intel.com, gustavo.sousa@intel.com,
ankit.k.nautiyal@intel.com
Subject: Re: [PATCH v2 3/3] drm/i915/psr: Use DMC wakelock instead of DC state for VBI
Date: Tue, 12 May 2026 14:11:11 +0300 [thread overview]
Message-ID: <78aeb45ca7f758089337b644814d195ad2dfdbe3@intel.com> (raw)
In-Reply-To: <20260430134505.1728443-4-dibin.moolakadan.subrahmanian@intel.com>
On Thu, 30 Apr 2026, Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com> wrote:
> Use the DMC wakelock mechanism for preventing DC entry.
> platforms without wakelock support will continue to use
> set_target_dc_state() to disable DC entry during active vblank.
Why? Every commit message needs to answer the question *why*. I can
match the "what" above with the code, but it doesn't explain at all why
we should make this change.
BR,
Jani.
>
> Changes in v2:
> - Use intel_dmc_wl_supported() instead of
> DISPLAY_VER check (Gustavo Sousa).
>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/2296
> Fixes: acfc688bc51b ("drm/i915/dmc: Reduce wakelock hold time")
> Signed-off-by: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_psr.c | 26 +++++++++++++++---------
> 1 file changed, 16 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index 9acd47392192..5b48a677bf39 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -4151,16 +4151,22 @@ void intel_psr_notify_vblank_enable_disable(struct intel_display *display,
> mutex_unlock(&intel_dp->psr.lock);
> break;
> }
> -
> - /*
> - * NOTE: intel_display_power_set_target_dc_state is used
> - * only by PSR * code for DC3CO handling. DC3CO target
> - * state is currently disabled in * PSR code. If DC3CO
> - * is taken into use we need take that into account here
> - * as well.
> - */
> - intel_display_power_set_target_dc_state(display, enable ? DC_STATE_DISABLE :
> - DC_STATE_EN_UPTO_DC6);
> + if (!intel_dmc_wl_supported(display)) {
> + /*
> + * NOTE: intel_display_power_set_target_dc_state is used
> + * only by PSR code for DC3CO handling. DC3CO target
> + * state is currently disabled in PSR code. If DC3CO
> + * is taken into use we need take that into account here
> + * as well.
> + */
> + intel_display_power_set_target_dc_state(display, enable ? DC_STATE_DISABLE :
> + DC_STATE_EN_UPTO_DC6);
> + } else {
> + if (enable)
> + intel_dmc_wl_get_noreg(display);
> + else
> + intel_dmc_wl_put_noreg(display);
> + }
> }
>
> static void
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-05-12 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 13:45 [PATCH v2 0/3] drm/i915/psr: DC entry prevention during active vblank Dibin Moolakadan Subrahmanian
2026-04-30 13:45 ` [PATCH v2 1/3] drm/i915/psr: Unify DC state handling for PSR and Panel Replay on VBI enable Dibin Moolakadan Subrahmanian
2026-04-30 13:45 ` [PATCH v2 2/3] drm/i915/dmc_wl: Expose intel_dmc_wl_supported() Dibin Moolakadan Subrahmanian
2026-04-30 13:45 ` [PATCH v2 3/3] drm/i915/psr: Use DMC wakelock instead of DC state for VBI Dibin Moolakadan Subrahmanian
2026-05-12 11:11 ` Jani Nikula [this message]
2026-04-30 14:53 ` ✗ i915.CI.BAT: failure for drm/i915/psr: DC entry prevention during active vblank (rev2) Patchwork
2026-05-04 5:50 ` ✓ i915.CI.BAT: success for drm/i915/psr: DC entry prevention during active vblank (rev3) Patchwork
2026-05-04 8:20 ` ✓ i915.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=78aeb45ca7f758089337b644814d195ad2dfdbe3@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dibin.moolakadan.subrahmanian@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@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