From: "Michał Grzelak" <michal.grzelak@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/i915/psr: Block DC states on vblank enable when Panel Replay supported
Date: Mon, 11 May 2026 15:24:03 +0200 (CEST) [thread overview]
Message-ID: <6e9aff22-6ca1-92cb-c8c0-3fcd2fcfaef3@intel.com> (raw)
In-Reply-To: <20260511121551.2373824-1-jouni.hogander@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2594 bytes --]
On Mon, 11 May 2026, Jouni Högander wrote:
> Currently we are blocking DC states only when Panel Replay is enabled on
> vblank enable. It may happen that Panel Replay is getting enabled when
> vblank is already enabled. Fix this by blocking DC states always if Panel
> Replay is supported.
>
> While at it take care of possible dual eDP case by looping all encoders
> supporting PSR.
>
> Fixes: 0c427ac78a1d ("drm/i915/psr: Add interface to notify PSR of vblank enable/disable")
> Cc: <stable@vger.kernel.org> # v6.16+
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_psr.c | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index 9958230a3dd9..657b1614cd65 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -4141,32 +4141,33 @@ void intel_psr_notify_vblank_enable_disable(struct intel_display *display,
> bool enable)
> {
> struct intel_encoder *encoder;
> + bool block_dc_states = false;
>
> for_each_intel_encoder_with_psr(display->drm, encoder) {
> struct intel_dp *intel_dp = enc_to_intel_dp(encoder);
>
> mutex_lock(&intel_dp->psr.lock);
> - if (intel_dp->psr.panel_replay_enabled) {
> - mutex_unlock(&intel_dp->psr.lock);
> - break;
> - }
> + if (CAN_PANEL_REPLAY(intel_dp))
> + block_dc_states = true;
>
> - if (intel_dp->psr.enabled && intel_dp->psr.pkg_c_latency_used)
> + if (intel_dp->psr.enabled && !intel_dp->psr.panel_replay_enabled &&
> + intel_dp->psr.pkg_c_latency_used)
> intel_psr_apply_underrun_on_idle_wa_locked(intel_dp);
>
> mutex_unlock(&intel_dp->psr.lock);
> - return;
> }
>
> /*
> * NOTE: intel_display_power_set_target_dc_state is used
> - * only by PSR * code for DC3CO handling. DC3CO target
> + * only by PSR code for DC3CO handling. DC3CO target
> * state is currently disabled in * PSR code. If DC3CO
Here '*' could be dropped as well. Anyways it doesn't make much
difference since next patch will remove the whole block.
Reviewed-by: Michał Grzelak <michal.grzelak@intel.co>
BR,
Michał
> * 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 (block_dc_states)
> + intel_display_power_set_target_dc_state(display, enable ?
> + DC_STATE_DISABLE :
> + DC_STATE_EN_UPTO_DC6);
> }
>
> static void
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-05-11 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 12:15 [PATCH 1/2] drm/i915/psr: Block DC states on vblank enable when Panel Replay supported Jouni Högander
2026-05-11 12:15 ` [PATCH 2/2] drm/i915/psr: Use DC_OFF wake reference to block DC6 on vblank enable Jouni Högander
2026-05-11 13:25 ` Michał Grzelak
2026-05-11 13:24 ` Michał Grzelak [this message]
2026-05-11 17:28 ` ✓ i915.CI.BAT: success for series starting with [1/2] drm/i915/psr: Block DC states on vblank enable when Panel Replay supported Patchwork
2026-05-11 23:46 ` ✗ 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=6e9aff22-6ca1-92cb-c8c0-3fcd2fcfaef3@intel.com \
--to=michal.grzelak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@intel.com \
--cc=stable@vger.kernel.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