public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Almahallawy, Khaled" <khaled.almahallawy@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Deak, Imre" <imre.deak@intel.com>,
	"Navare, Manasi D" <manasi.d.navare@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dp: Add missing TPS4 programming bits
Date: Wed, 20 Oct 2021 22:18:19 +0000	[thread overview]
Message-ID: <5baef710b9ef65b0f62b75538fa57b2bb797f03e.camel@intel.com> (raw)
In-Reply-To: <YW6zi+fooHa+IG4r@intel.com>

On Tue, 2021-10-19 at 15:01 +0300, Ville Syrjälä wrote:
> On Tue, Oct 19, 2021 at 02:52:15PM +0300, Jani Nikula wrote:
> > On Mon, 19 Jul 2021, Khaled Almahallawy <
> > khaled.almahallawy@intel.com> wrote:
> > > Bits 20:19 are used to set CP2520 Patterns 1/2/3 (refer to
> > > Specs:50484).
> > > TPS4 is CP2520 Pattern 3 (refer to DP2.0 spaces Table 3-11, DPCD
> > > 00248h
> > > LINK_QUAL_PATTERN_SELECT, and DP PHY 1.4 CTS - Appendix A -
> > > Compliance
> > > EYE Pattern(CP2520; Normative))
> > > 
> > > For TPS4, setting bits 20:19 to value != 00b, leads to a non-TPS4 
> > > pattern.
> > > This is confirmed using DP Scope running DP1.4 PHY CTS.
> > > 
> > > To avoid any accidental wrong setting of bits 20:19, set it
> > > correctly for
> > > TPS4 LT pattern selection. This programming sequence is the same
> > > used by EV.
> > 
> > Do we need this?
> 
> I think what we need is some place to initialize DP_TP_CTL fully.
> Right now it seems to be just all RMW.

The  intention for this patch is to call “intel_dp->set_link_train”
inside “intel_dp_phy_pattern_update” when adding CP2520_PAT3/TPS4
instead of following this approach: 
https://patchwork.freedesktop.org/patch/378522/ 
 
Unfortunately, the only way to set TPS4 is through DP_TP_CTL unlike the
rest of PHY test patterns in DP_COMP_CTL(specs:50482) 
 
Could you please suggest what is the recommended way to add the support
of TPS4 PHY pattern to compliance code?

Thank you
Khaled
> 
> > BR,
> > Jani.
> > 
> > > Cc: Manasi Navare <manasi.d.navare@intel.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > CC: José Roberto de Souza <jose.souza@intel.com>
> > > Cc: Imre Deak <imre.deak@intel.com>
> > > Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/display/intel_ddi.c | 2 ++
> > >  drivers/gpu/drm/i915/i915_reg.h          | 4 ++++
> > >  2 files changed, 6 insertions(+)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c
> > > b/drivers/gpu/drm/i915/display/intel_ddi.c
> > > index 26a3aa73fcc4..54b4b28fdc74 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_ddi.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
> > > @@ -3412,6 +3412,8 @@ static void intel_ddi_set_link_train(struct
> > > intel_dp *intel_dp,
> > >  		break;
> > >  	case DP_TRAINING_PATTERN_4:
> > >  		temp |= DP_TP_CTL_LINK_TRAIN_PAT4;
> > > +		temp &= ~DP_TP_CTL_TRAIN_PAT4_SEL_MASK;
> > > +		temp |= DP_TP_CTL_TRAIN_PAT4_SEL_TP4a;
> > >  		break;
> > >  	}
> > >  
> > > diff --git a/drivers/gpu/drm/i915/i915_reg.h
> > > b/drivers/gpu/drm/i915/i915_reg.h
> > > index 943fe485c662..a65998df9994 100644
> > > --- a/drivers/gpu/drm/i915/i915_reg.h
> > > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > > @@ -10176,6 +10176,10 @@ enum skl_power_gate {
> > >  #define  DP_TP_CTL_MODE_SST			(0 << 27)
> > >  #define  DP_TP_CTL_MODE_MST			(1 << 27)
> > >  #define  DP_TP_CTL_FORCE_ACT			(1 << 25)
> > > +#define  DP_TP_CTL_TRAIN_PAT4_SEL_MASK		(3 << 19)
> > > +#define  DP_TP_CTL_TRAIN_PAT4_SEL_TP4a		(0 << 19)
> > > +#define  DP_TP_CTL_TRAIN_PAT4_SEL_TP4b		(1 << 19)
> > > +#define  DP_TP_CTL_TRAIN_PAT4_SEL_TP4c		(2 << 19)
> > >  #define  DP_TP_CTL_ENHANCED_FRAME_ENABLE	(1 << 18)
> > >  #define  DP_TP_CTL_FDI_AUTOTRAIN		(1 << 15)
> > >  #define  DP_TP_CTL_LINK_TRAIN_MASK		(7 << 8)
> > 
> > -- 
> > Jani Nikula, Intel Open Source Graphics Center

      reply	other threads:[~2021-10-20 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 23:59 [Intel-gfx] [PATCH] drm/i915/dp: Add missing TPS4 programming bits Khaled Almahallawy
2021-07-20  0:19 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-07-20  0:24 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-07-20  0:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-20  3:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-10-19 11:52 ` [Intel-gfx] [PATCH] " Jani Nikula
2021-10-19 12:01   ` Ville Syrjälä
2021-10-20 22:18     ` Almahallawy, Khaled [this message]

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=5baef710b9ef65b0f62b75538fa57b2bb797f03e.camel@intel.com \
    --to=khaled.almahallawy@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=manasi.d.navare@intel.com \
    --cc=ville.syrjala@linux.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