From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v10 04/10] drm/i915/vrr: Prepare to Use TRANS_PUSH mechanism for PSR frame change
Date: Tue, 27 Jan 2026 10:48:53 +0530 [thread overview]
Message-ID: <d4988550-e0cf-490d-873d-ce55878b240a@intel.com> (raw)
In-Reply-To: <20260126075959.925413-5-jouni.hogander@intel.com>
On 1/26/2026 1:29 PM, Jouni Högander wrote:
> On Lunarlake and onwards it is possible to generate PSR "frame change"
> event using TRANS_PUSH mechanism. Implement function to enable this and
> take PSR into account in intel_vrr_send_push.
>
> v7:
> - HAS_PSR_FRAME_CHANGE macro moved to separate patch and renamed as
> HAS_PSR_TRANS_PUSH_FRAME_CHANGE
> - use intel_psr_use_trans_push instead of HAS_PSR_FRAME_CHANGE in
> intel_psr_trigger_frame_change
> - moved calling intel_vrr_psr_frame_change_enable away from this patch
> v6:
> - add HAS_PSR_FRAME_CHANGE macro
> - use TRANS_PUSH in instead of TRAN_VRR_CTL
> v5: use intel_psr_use_trans_push for intel_vrr_psr_frame_change_enable
> v4:
> - use rmw when enabling/disabling transcoder
> - set TRANS_PUSH_EN conditionally in intel_vrr_send_push
> - do not call intel_vrr_send_push from intel_psr_trigger_frame_change
> - do not enable using TRANS_PUSH mechanism for PSR "Frame Change"
> v3:
> - use rmw when enabling/disabling
> - keep LNL_TRANS_PUSH_PSR_PR_EN set always on LunarLake and onwards
> v2: use intel_vrr_trans_push_enabled_set_clear instead of rmw
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_crtc.c | 4 +++-
> drivers/gpu/drm/i915/display/intel_psr.c | 8 +++++---
> drivers/gpu/drm/i915/display/intel_vrr.c | 14 ++++++++++++--
> drivers/gpu/drm/i915/display/intel_vrr.h | 1 +
> 4 files changed, 21 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_crtc.c b/drivers/gpu/drm/i915/display/intel_crtc.c
> index 778ebc5095c3..ed3c6c4ce025 100644
> --- a/drivers/gpu/drm/i915/display/intel_crtc.c
> +++ b/drivers/gpu/drm/i915/display/intel_crtc.c
> @@ -747,7 +747,9 @@ void intel_pipe_update_end(struct intel_atomic_state *state,
> * which would cause the next frame to terminate already at vmin
> * vblank start instead of vmax vblank start.
> */
> - if (!state->base.legacy_cursor_update)
> + if (!state->base.legacy_cursor_update ||
> + (intel_psr_use_trans_push(new_crtc_state) &&
> + !new_crtc_state->vrr.enable))
> intel_vrr_send_push(NULL, new_crtc_state);
>
> local_irq_enable();
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index b0d72c04db45..9613c50623dc 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -2516,9 +2516,11 @@ void intel_psr_trigger_frame_change_event(struct intel_dsb *dsb,
> intel_pre_commit_crtc_state(state, crtc);
> struct intel_display *display = to_intel_display(crtc);
>
> - if (crtc_state->has_psr)
> - intel_de_write_dsb(display, dsb,
> - CURSURFLIVE(display, crtc->pipe), 0);
> + if (!crtc_state->has_psr || intel_psr_use_trans_push(crtc_state))
> + return;
> +
> + intel_de_write_dsb(display, dsb,
> + CURSURFLIVE(display, crtc->pipe), 0);
> }
>
> /**
> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
> index f26989c74268..8a072f90049f 100644
> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
> @@ -698,7 +698,7 @@ void intel_vrr_send_push(struct intel_dsb *dsb,
> struct intel_display *display = to_intel_display(crtc_state);
> enum transcoder cpu_transcoder = crtc_state->cpu_transcoder;
>
> - if (!crtc_state->vrr.enable)
> + if (!crtc_state->vrr.enable && !intel_psr_use_trans_push(crtc_state))
> return;
>
> if (dsb)
> @@ -920,7 +920,8 @@ static void intel_vrr_tg_disable(const struct intel_crtc_state *old_crtc_state)
> VRR_STATUS_VRR_EN_LIVE, 1000))
> drm_err(display->drm, "Timed out waiting for VRR live status to clear\n");
>
> - intel_de_write(display, TRANS_PUSH(display, cpu_transcoder), 0);
> + intel_de_rmw(display, TRANS_PUSH(display, cpu_transcoder),
> + TRANS_PUSH_EN, 0);
> }
>
> void intel_vrr_enable(const struct intel_crtc_state *crtc_state)
> @@ -973,6 +974,15 @@ void intel_vrr_transcoder_disable(const struct intel_crtc_state *old_crtc_state)
> intel_vrr_tg_disable(old_crtc_state);
> }
>
> +void intel_vrr_psr_frame_change_enable(const struct intel_crtc_state *crtc_state)
I think introduction to this helper can be a separate patch.
So in the current patch, we are essentially preparing PSR HW to hook to
the new frame change enable based on intel_psr_use_trans_push().
IMO, the helper to enable this new functionality can be a separate thing.
Overall I agree with the changes.
Regards,
Ankit
> +{
> + struct intel_display *display = to_intel_display(crtc_state);
> + enum transcoder cpu_transcoder = crtc_state->cpu_transcoder;
> +
> + intel_de_write(display, TRANS_PUSH(display, cpu_transcoder),
> + trans_vrr_push(crtc_state, false));
> +}
> +
> bool intel_vrr_is_fixed_rr(const struct intel_crtc_state *crtc_state)
> {
> return crtc_state->vrr.flipline &&
> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.h b/drivers/gpu/drm/i915/display/intel_vrr.h
> index bedcc8c4bff2..4f16ca4af91f 100644
> --- a/drivers/gpu/drm/i915/display/intel_vrr.h
> +++ b/drivers/gpu/drm/i915/display/intel_vrr.h
> @@ -33,6 +33,7 @@ void intel_vrr_dcb_increment_flip_count(struct intel_crtc_state *crtc_state,
> struct intel_crtc *crtc);
> bool intel_vrr_is_push_sent(const struct intel_crtc_state *crtc_state);
> void intel_vrr_disable(const struct intel_crtc_state *old_crtc_state);
> +void intel_vrr_psr_frame_change_enable(const struct intel_crtc_state *crtc_state);
> void intel_vrr_get_config(struct intel_crtc_state *crtc_state);
> int intel_vrr_vmax_vtotal(const struct intel_crtc_state *crtc_state);
> int intel_vrr_vmin_vtotal(const struct intel_crtc_state *crtc_state);
next prev parent reply other threads:[~2026-01-27 5:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 7:59 [PATCH v10 00/10] Use trans push mechanism to generate frame change event Jouni Högander
2026-01-26 7:59 ` [PATCH v10 01/10] drm/i915/psr: Add TRANS_PUSH register bit definition for PSR Jouni Högander
2026-01-26 7:59 ` [PATCH v10 02/10] drm/i915/psr: Add intel_psr_use_trans_push to query if TRANS_PUSH is used Jouni Högander
2026-01-27 5:20 ` Nautiyal, Ankit K
2026-01-26 7:59 ` [PATCH v10 03/10] drm/i915/vrr: Add helper for parsing value to be written into TRANS_PUSH Jouni Högander
2026-01-27 5:25 ` Nautiyal, Ankit K
2026-01-26 7:59 ` [PATCH v10 04/10] drm/i915/vrr: Prepare to Use TRANS_PUSH mechanism for PSR frame change Jouni Högander
2026-01-27 5:18 ` Nautiyal, Ankit K [this message]
2026-01-26 7:59 ` [PATCH v10 05/10] drm/i915/dsb: Set DSB_SKIP_WAITS_EN chicken bit for LunarLake and onwards Jouni Högander
2026-01-27 5:32 ` Nautiyal, Ankit K
2026-01-26 7:59 ` [PATCH v10 06/10] drm/i915/display: Wait for vblank in case of PSR is using trans push Jouni Högander
2026-01-27 5:41 ` Nautiyal, Ankit K
2026-01-26 7:59 ` [PATCH v10 07/10] drm/i915/psr: Wait for idle only after possible send push Jouni Högander
2026-01-26 7:59 ` [PATCH v10 08/10] drm/i915/psr: Do PSR exit on frontbuffer flush on LunarLake and onwards Jouni Högander
2026-01-26 7:59 ` [PATCH v10 09/10] drm/i915/display: Add HAS_PSR_TRANS_PUSH_FRAME_CHANGE macro Jouni Högander
2026-01-27 7:48 ` Nautiyal, Ankit K
2026-01-26 7:59 ` [PATCH v10 10/10] drm/i915/psr: Use TRANS_PUSH to trigger frame change event Jouni Högander
2026-01-27 8:35 ` Nautiyal, Ankit K
2026-01-26 8:44 ` ✓ i915.CI.BAT: success for Use trans push mechanism to generate " Patchwork
2026-01-26 10:32 ` ✗ 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=d4988550-e0cf-490d-873d-ce55878b240a@intel.com \
--to=ankit.k.nautiyal@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