From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v9 8/8] drm/i915/psr: Use TRANS_PUSH to trigger frame change event
Date: Thu, 22 Jan 2026 11:43:34 +0000 [thread overview]
Message-ID: <28f217a118eb4058f068bc27926412b10eb8ae46.camel@intel.com> (raw)
In-Reply-To: <8fb7e836-7ee2-4bb1-8f6b-abb7906b61da@intel.com>
On Thu, 2026-01-22 at 16:34 +0530, Nautiyal, Ankit K wrote:
>
> On 12/23/2025 4:21 PM, Jouni Högander wrote:
> > Now we have everything in place for triggering PSR "frame change"
> > event
> > using TRANS_PUSH: use TRANS_PUSH for LunarLake and onwards.
> >
> > v3: use HAS_PSR_FRAME_CHANGE macro
> > v2: use AND instead of OR in intel_psr_use_trans_push
> >
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_psr.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> > b/drivers/gpu/drm/i915/display/intel_psr.c
> > index ee70d0ceeb5b..353924f8c975 100644
> > --- a/drivers/gpu/drm/i915/display/intel_psr.c
> > +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> > @@ -4569,6 +4569,7 @@ int intel_psr_min_guardband(struct
> > intel_crtc_state *crtc_state)
> >
> > bool intel_psr_use_trans_push(const struct intel_crtc_state
> > *crtc_state)
> > {
> > - /* TODO: Enable using trans push when everything is in
> > place */
> > - return false;
> > + struct intel_display *display =
> > to_intel_display(crtc_state);
> > +
> > + return HAS_PSR_FRAME_CHANGE(display) && crtc_state-
> > >has_psr;
>
>
> Can we just always enable this bit for LNL+ platforms.
>
> I mean if no PSR/PSR2/Panel Replay are enabled, if we still have this
> bit set, can there be any issue?
>
> The frame change event will be generated but the PSR/PR logic will
> not
> get activated.
I think this should be ok. I still need to have this
intel_psr_use_trans_push to have correct sequence in dsb execution.
I'll guess I can use HAS_PSR_FRAME_CHANGE in that trans_vrr_push
discussed on patch 3.
BR,
Jouni Högander
>
>
> Regards,
>
> Ankit
>
> > }
next prev parent reply other threads:[~2026-01-22 11:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 10:51 [PATCH v9 0/8] Use trans push mechanism to generate frame change event Jouni Högander
2025-12-23 10:51 ` [PATCH v9 1/8] drm/i915/psr: Add TRANS_PUSH register bit definition for PSR Jouni Högander
2025-12-23 10:51 ` [PATCH v9 2/8] drm/i915/psr: Add intel_psr_use_trans_push to query if TRANS_PUSH is used Jouni Högander
2025-12-23 10:51 ` [PATCH v9 3/8] drm/i915/vrr: Prepare to Use TRANS_PUSH mechanism for PSR frame change Jouni Högander
2026-01-22 11:04 ` Nautiyal, Ankit K
2026-01-22 11:39 ` Hogander, Jouni
2025-12-23 10:51 ` [PATCH v9 4/8] drm/i915/dsb: Set DSB_SKIP_WAITS_EN chicken bit for LunarLake and onwards Jouni Högander
2026-01-23 4:41 ` Nautiyal, Ankit K
2026-01-23 6:19 ` Hogander, Jouni
2025-12-23 10:51 ` [PATCH v9 5/8] drm/i915/display: Wait for vblank in case of PSR is using trans push Jouni Högander
2025-12-23 10:51 ` [PATCH v9 6/8] drm/i915/psr: Wait for idle only after possible send push Jouni Högander
2026-01-23 5:12 ` Nautiyal, Ankit K
2026-01-23 6:37 ` Hogander, Jouni
2026-01-23 11:33 ` Nautiyal, Ankit K
2025-12-23 10:51 ` [PATCH v9 7/8] drm/i915/psr: Do PSR exit on frontbuffer flush on LunarLake and onwards Jouni Högander
2026-01-23 6:18 ` Nautiyal, Ankit K
2025-12-23 10:51 ` [PATCH v9 8/8] drm/i915/psr: Use TRANS_PUSH to trigger frame change event Jouni Högander
2026-01-22 11:04 ` Nautiyal, Ankit K
2026-01-22 11:43 ` Hogander, Jouni [this message]
2025-12-23 12:23 ` ✓ i915.CI.BAT: success for Use trans push mechanism to generate " Patchwork
2025-12-24 17:26 ` ✓ 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=28f217a118eb4058f068bc27926412b10eb8ae46.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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