From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Deak, Imre" <imre.deak@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 5/8] drm/i915/psr: Clear pr_dpcd as well on disconnect
Date: Wed, 3 Dec 2025 15:10:54 +0000 [thread overview]
Message-ID: <f6877a4bf35a867b13fcd4d2d32499cae0d41664.camel@intel.com> (raw)
In-Reply-To: <aTBLQkd57Nz4VE7s@ideak-desk>
On Wed, 2025-12-03 at 16:37 +0200, Imre Deak wrote:
> On Mon, Dec 01, 2025 at 01:23:41PM +0200, Jouni Hogander wrote:
> > On Mon, 2025-12-01 at 12:53 +0200, Imre Deak wrote:
> > > On Fri, Nov 21, 2025 at 01:16:52PM +0200, Jouni Högander wrote:
> > > > Currently we are leaving pr_dpcd containing Panel Replay
> > > > capability
> > > > DPCD registers as it is on disconnect. Clear it as well on
> > > > disconnect.
> > > >
> > > > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > > > ---
> > > > drivers/gpu/drm/i915/display/intel_dp.c | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
> > > > b/drivers/gpu/drm/i915/display/intel_dp.c
> > > > index 62808cd35f5f2..7195c408d93ab 100644
> > > > --- a/drivers/gpu/drm/i915/display/intel_dp.c
> > > > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> > > > @@ -6050,6 +6050,7 @@ intel_dp_detect(struct drm_connector
> > > > *_connector,
> > > > if (status == connector_status_disconnected) {
> > > > intel_dp_test_reset(intel_dp);
> > > > memset(connector->dp.dsc_dpcd, 0,
> > > > sizeof(connector->dp.dsc_dpcd));
> > > > + memset(connector->dp.pr_dpcd, 0,
> > > > sizeof(connector->dp.pr_dpcd));
> > >
> > > What about psr_dpcd?
> >
> > PSR is only for eDP and can't be disconnected.
>
> Ok. Panel Replay used on non-eDP has also Selective Update for
> instance,
> but that has separate PR specific capability registers. The same is
> true
> I presume for any other functionality that could be used both on PSR2
> and PR.
>
> It's still a bit strange that intel_dp_detect() ->
> intel_psr_init_dpcd()
> -> _psr_init_dpcd() reads psr_dpcd (aka dp.psr_caps.dpcd after your
> patch) for non-eDP as well. Even though the values should not be used
> anywhere based on the above, I'd still avoid explicitly reading them
> out
> for non-eDP (only as a follow-up imo, no need to change this now).
Ok, I will take care of that.
Another thing I have been recently wondering is the eDP/DP version.
Generally speaking: should I check eDP/DP version before checking the
feature of some specific version. I have now seen couple of cases where
panel is stating Panel Replay support, but still saying it's eDP
version 1.4. and Panel Replay is non-functional.(Related patch in
trybot: https://patchwork.freedesktop.org/series/157760/)
BR,
Jouni Högander
>
> > > All these resetting of the caps cause a problem if the connector
> > > needs to be modeset after the sink is disconnected (since then
> > > the
> > > state computation for the connector will fail seeing these caps
> > > being reset). Instead the caps should be kept intact here,
> > > resetting/reiniting them only when a new sink is connected. Since
> > > this is a pre-existing issue, could you add for now a
> > > corrsponding
> > > FIXME: comment in this patch?
> >
> > Thank you for pointing this out. I will add the FIXME.
> >
> > BR,
> >
> > Jouni Högander
> >
> > >
> > > > intel_dp->psr.sink_panel_replay_support =
> > > > false;
> > > > intel_dp->psr.sink_panel_replay_su_support =
> > > > false;
> > > > intel_dp->psr.sink_panel_replay_dsc_support =
> > > > --
> > > > 2.43.0
next prev parent reply other threads:[~2025-12-03 15:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 11:16 [PATCH 0/8] Move PSR/Panel Replay sink data into intel_connector Jouni Högander
2025-11-21 11:16 ` [PATCH 1/8] drm/i915/psr: Add panel granularity information " Jouni Högander
2025-12-01 9:54 ` Imre Deak
2025-11-21 11:16 ` [PATCH 2/8] drm/i915/psr: Use SU granularity information available in intel_connector Jouni Högander
2025-12-01 10:14 ` Imre Deak
2025-11-21 11:16 ` [PATCH 3/8] drm/i915/psr: Compute Panel Replay/Adaptive coexistence behavior Jouni Högander
2025-11-21 11:24 ` Jani Nikula
2025-12-01 10:28 ` Imre Deak
2025-11-21 11:16 ` [PATCH 4/8] drm/i915/psr: Move pr_dpcd and psr_dpcd to intel_connector Jouni Högander
2025-12-01 10:45 ` Imre Deak
2025-11-21 11:16 ` [PATCH 5/8] drm/i915/psr: Clear pr_dpcd as well on disconnect Jouni Högander
2025-12-01 10:53 ` Imre Deak
2025-12-01 11:23 ` Hogander, Jouni
2025-12-03 14:37 ` Imre Deak
2025-12-03 15:10 ` Hogander, Jouni [this message]
2025-11-21 11:16 ` [PATCH 6/8] drm/i915/psr: Move Panel Replay DSC sink support data to intel_connector Jouni Högander
2025-12-01 10:55 ` Imre Deak
2025-11-21 11:16 ` [PATCH 7/8] drm/i915/psr: Move sink PSR and Panel Replay booleans " Jouni Högander
2025-12-01 10:59 ` Imre Deak
2025-11-21 11:16 ` [PATCH 8/8] drm/i915/psr: Move sink_sync_latency " Jouni Högander
2025-12-01 11:03 ` Imre Deak
2025-11-24 20:41 ` ✓ i915.CI.BAT: success for Move PSR/Panel Replay sink data into intel_connector Patchwork
2025-11-25 1:09 ` ✗ 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=f6877a4bf35a867b13fcd4d2d32499cae0d41664.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=imre.deak@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;
as well as URLs for NNTP newsgroup(s).