Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/4] drm/i915/psr: Read Intel DPCD workaround register
Date: Thu, 7 May 2026 12:35:16 +0000	[thread overview]
Message-ID: <26a2456c93e47c77ec0b837c65691beebbd9b9ff.camel@intel.com> (raw)
In-Reply-To: <DM3PPF208195D8D5A61CDAC6A255BC5D27AE33F2@DM3PPF208195D8D.namprd11.prod.outlook.com>

On Wed, 2026-05-06 at 06:39 +0000, Kandpal, Suraj wrote:
> > Subject: [PATCH 2/4] drm/i915/psr: Read Intel DPCD workaround
> > register
> > 
> > Read Intel DPCD workaround register and store it into
> > intel_connector-
> > > dp.psr_caps. Psr_caps was chosen as currently it contains only
> > > PSR
> 
> Nit: psr_caps
> 
> > workaround for PSR2 SDP on prior scanline implementation.
> > 
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_display_types.h | 1 +
> >  drivers/gpu/drm/i915/display/intel_psr.c           | 8 +++++++-
> >  2 files changed, 8 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h
> > b/drivers/gpu/drm/i915/display/intel_display_types.h
> > index ee076106be85..ec00fcb46734 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> > +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> > @@ -584,6 +584,7 @@ struct intel_connector {
> > 
> >  		struct {
> >  			u8 dpcd[EDP_PSR_RECEIVER_CAP_SIZE];
> > +			u8 intel_wa_dpcd;
> > 
> >  			bool support;
> >  			bool su_support;
> > diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> > b/drivers/gpu/drm/i915/display/intel_psr.c
> > index b4ca5843d098..1f3f0d35d52a 100644
> > --- a/drivers/gpu/drm/i915/display/intel_psr.c
> > +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> > @@ -44,6 +44,7 @@
> >  #include "intel_display_wa.h"
> >  #include "intel_dmc.h"
> >  #include "intel_dp.h"
> > +#include "intel_dpcd.h"
> >  #include "intel_dp_aux.h"
> >  #include "intel_dp_tunnel.h"
> >  #include "intel_dsb.h"
> > @@ -717,8 +718,13 @@ static void _psr_init_dpcd(struct intel_dp
> > *intel_dp,
> > struct intel_connector *co
> >  			    connector->dp.psr_caps.su_support ? ""
> > : "not ");
> >  	}
> > 
> > -	if (connector->dp.psr_caps.su_support)
> > +	if (connector->dp.psr_caps.su_support) {
> > +		ret = drm_dp_dpcd_read_byte(&intel_dp->aux,
> > INTEL_WA_REGISTER_CAPS,
> > +					    &connector-
> > > dp.psr_caps.intel_wa_dpcd);
> > +		if (ret < 0)
> > +			return;
> 
> Any particular reason for caching this I see that this can be easily
> read when required ? Maybe I missed something ?

I was thinking we don't want to read this on each compute_config. It is
anyways reading DPCD register from panel.

> Also we are returning early now, was this missed, do we require a
> fixes ? Also some explanation why this makes sense.

This is returning early if reading the INTEL_WA_REGISTER_CAPS fails.
That is supposed to be unexpected event so returning early due to that.
There is a fixes tag in next patch in the set.

BR,
Jouni Högander

> 
> Regards,
> Suraj Kandpal
> 
> >  		_psr_compute_su_granularity(intel_dp, connector);
> > +	}
> >  }
> > 
> >  void intel_psr_init_dpcd(struct intel_dp *intel_dp, struct
> > intel_connector
> > *connector)
> > --
> > 2.43.0
> 


  reply	other threads:[~2026-05-07 12:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15  5:39 [PATCH 0/4] PSR2 SDP on Prior Scanline workarounds Jouni Högander
2026-04-15  5:39 ` [PATCH 1/4] drm/i915/psr: Add defininitions for INTEL_WA_REGISTER_CAPS DPCD register Jouni Högander
2026-04-15  7:28   ` Jani Nikula
2026-04-15  5:39 ` [PATCH 2/4] drm/i915/psr: Read Intel DPCD workaround register Jouni Högander
2026-05-06  6:39   ` Kandpal, Suraj
2026-05-07 12:35     ` Hogander, Jouni [this message]
2026-04-15  5:39 ` [PATCH 3/4] drm/i915/psr: Apply Intel DPCD workaround when SDP on prior line used Jouni Högander
2026-05-06  7:24   ` Kandpal, Suraj
2026-05-07 12:42     ` Hogander, Jouni
2026-04-15  5:40 ` [PATCH 4/4] drm/i915/psr: Apply SDP on prior scanline workaround for NVL Jouni Högander
2026-05-06  7:29   ` Kandpal, Suraj
2026-05-07 12:52     ` Hogander, Jouni
2026-04-15  5:49 ` ✗ CI.checkpatch: warning for PSR2 SDP on Prior Scanline workarounds Patchwork
2026-04-15  5:50 ` ✓ CI.KUnit: success " Patchwork
2026-04-15  6:54 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-15  7:40 ` ✓ Xe.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=26a2456c93e47c77ec0b837c65691beebbd9b9ff.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@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