From: "Souza, Jose" <jose.souza@intel.com>
To: "Mun, Gwan-gyeong" <gwan-gyeong.mun@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/5] drm/i915/display/adlp: Add new PSR2 workarounds
Date: Mon, 13 Sep 2021 17:00:09 +0000 [thread overview]
Message-ID: <b8fea6042bf07bb1dc9a45482ada74fc9f5d0f95.camel@intel.com> (raw)
In-Reply-To: <9d949ff3-9e78-ef10-501b-b68625cc10fa@intel.com>
On Mon, 2021-09-13 at 19:09 +0300, Gwan-gyeong Mun wrote:
>
> On 9/10/21 7:29 PM, Souza, Jose wrote:
> > On Fri, 2021-09-10 at 16:38 +0300, Gwan-gyeong Mun wrote:
> > >
> > > On 9/10/21 2:07 AM, José Roberto de Souza wrote:
> > > > Wa_16014451276 fixes the starting coordinate for PSR2 selective
> > > > updates. CHICKEN_TRANS definition of the workaround bit has a wrong
> > > > name based on workaround definition and HSD.
> > > >
> > > > Wa_14014971508 allows the screen to continue to be updated when
> > > > coming back from DC5/DC6 and SF_SINGLE_FULL_FRAME bit is not kept
> > > > set in PSR2_MAN_TRK_CTL.
> > > >
> > > > Wa_16012604467 fixes underruns when exiting PSR2 when it is in one
> > > > of its internal states.
> > > >
> > > > Wa_14014971508 is still in pending status in BSpec but by
> > > > the time this is reviewed and ready to be merged it will be finalized.
> > > >
> > > > BSpec: 54369
> > > > BSpec: 50054
> > > > Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> > > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > > ---
> > > > drivers/gpu/drm/i915/display/intel_psr.c | 23 ++++++++++++++++++++++-
> > > > drivers/gpu/drm/i915/i915_reg.h | 4 ++++
> > > > 2 files changed, 26 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> > > > index 36816abb3bcc0..92c0b2159559f 100644
> > > > --- a/drivers/gpu/drm/i915/display/intel_psr.c
> > > > +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> > > > @@ -1086,6 +1086,12 @@ static void intel_psr_enable_source(struct intel_dp *intel_dp)
> > > > intel_de_write(dev_priv, reg, chicken);
> > > > }
> > > >
> > > > +/* Wa_16014451276:adlp */
> > > > +if (IS_ALDERLAKE_P(dev_priv) &&
> > > > + intel_dp->psr.psr2_enabled)
> > > > +intel_de_rmw(dev_priv, CHICKEN_TRANS(cpu_transcoder), 0,
> > > > + D13_1_BASED_X_GRANULARITY);
> > > Depending on the capability of the PSR panel, the following setting may
> > > not be necessary, could you add some comments such as "force enable
> > > 1-based X granularity on PSR2 VSC SDP"?
> >
> > It was made sure that all alderlake-P BOM panels will have 1-based X granularity, I can add something like that.
> >
> >
> > > > +
> > > > /*
> > > > * Per Spec: Avoid continuous PSR exit by masking MEMUP and HPD also
> > > > * mask LPSP to avoid dependency on other drivers that might block
> > > > @@ -1131,6 +1137,11 @@ static void intel_psr_enable_source(struct intel_dp *intel_dp)
> > > > TRANS_SET_CONTEXT_LATENCY(intel_dp->psr.transcoder),
> > > > TRANS_SET_CONTEXT_LATENCY_MASK,
> > > > TRANS_SET_CONTEXT_LATENCY_VALUE(1));
> > > > +
> > > > +/* Wa_16012604467:adlp */
> > > > +if (IS_ALDERLAKE_P(dev_priv) && intel_dp->psr.psr2_enabled)
> > > > +intel_de_rmw(dev_priv, CLKGATE_DIS_MISC, 0,
> > > > + CLKGATE_DIS_MISC_DMASC_GATING_DIS);
> > > > }
> > > >
> > > > static bool psr_interrupt_error_check(struct intel_dp *intel_dp)
> > > > @@ -1320,6 +1331,11 @@ static void intel_psr_disable_locked(struct intel_dp *intel_dp)
> > > > TRANS_SET_CONTEXT_LATENCY(intel_dp->psr.transcoder),
> > > > TRANS_SET_CONTEXT_LATENCY_MASK, 0);
> > > >
> > > > +/* Wa_16012604467:adlp */
> > > > +if (IS_ALDERLAKE_P(dev_priv) && intel_dp->psr.psr2_enabled)
> > > > +intel_de_rmw(dev_priv, CLKGATE_DIS_MISC,
> > > > + CLKGATE_DIS_MISC_DMASC_GATING_DIS, 0);
> > > > +
> > > > intel_snps_phy_update_psr_power_state(dev_priv, phy, false);
> > > >
> > > > /* Disable PSR on Sink */
> > > > @@ -1488,8 +1504,13 @@ static void psr2_man_trk_ctl_calc(struct intel_crtc_state *crtc_state,
> > > > u32 val = PSR2_MAN_TRK_CTL_ENABLE;
> > > >
> > > > if (full_update) {
> > > > +/*
> > > > + * Wa_14014971508:adlp
> > > > + * SINGLE_FULL_FRAME bit is not hold in register so can not be
> > > > + * restored by DMC, so using CONTINUOS_FULL_FRAME to mimic that
> > > > + */
> > > > if (IS_ALDERLAKE_P(dev_priv))
> > > > -val |= ADLP_PSR2_MAN_TRK_CTL_SF_SINGLE_FULL_FRAME;
> > > > +val |= ADLP_PSR2_MAN_TRK_CTL_SF_CONTINUOS_FULL_FRAME;
> > > > else
> > > > val |= PSR2_MAN_TRK_CTL_SF_SINGLE_FULL_FRAME;
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > > > index c2853cc005ee6..0de2f7541da6c 100644
> > > > --- a/drivers/gpu/drm/i915/i915_reg.h
> > > > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > > > @@ -8235,6 +8235,7 @@ enum {
> > > > #define VSC_DATA_SEL_SOFTWARE_CONTROLREG_BIT(25) /* GLK */
> > > > #define FECSTALL_DIS_DPTSTREAM_DPTTGREG_BIT(23)
> > > > #define DDI_TRAINING_OVERRIDE_ENABLEREG_BIT(19)
> > > > +#define D13_1_BASED_X_GRANULARITYREG_BIT(18)
> > > The meaning of this macro is to set "force enable 1-based X granularity
> > > on PSR2 VSC SDP" in Display 13.1 ADL, so the meaning of the macro may be
> > > a little ambiguous.
> >
> > The name of registers are set to match specification name as close as possible not the use or meaning.
> Yes, just looking at the macro, I thought that it could be interpreted
> in two ways: D13 / 1_BASED_X_GRANULARITY or D13_1 / BASED_X_GRANULARITY.
> If our macro naming convention is fine in this case, then I don't think
> the code is the problem either.
Okay yes someone could interpret into those 2 ways but checking bspec makes it clears that it is the first one.
I can rename to ADLP_1_BASED_X_GRANULARITY if you think it would make it better.
> >
> > > > #define DDI_TRAINING_OVERRIDE_VALUEREG_BIT(18)
> > > > #define DDIE_TRAINING_OVERRIDE_ENABLEREG_BIT(17) /* CHICKEN_TRANS_A only */
> > > > #define DDIE_TRAINING_OVERRIDE_VALUEREG_BIT(16) /* CHICKEN_TRANS_A only */
> > > > @@ -12789,4 +12790,7 @@ enum skl_power_gate {
> > > > #define CLKREQ_POLICY_MMIO(0x101038)
> > > > #define CLKREQ_POLICY_MEM_UP_OVRDREG_BIT(1)
> > > >
> > > > +#define CLKGATE_DIS_MISC_MMIO(0x46534)
> > > > +#define CLKGATE_DIS_MISC_DMASC_GATING_DISREG_BIT(21)
> > > > +
> > > > #endif /* _I915_REG_H_ */
> > > >
> >
next prev parent reply other threads:[~2021-09-13 17:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 23:07 [Intel-gfx] [PATCH 1/5] drm/i915/display/adlp: Fix PSR2_MAN_TRK_CTL_SU_REGION_END_ADDR calculation José Roberto de Souza
2021-09-09 23:07 ` [Intel-gfx] [PATCH 2/5] drm/i915/display/adlp: Add new PSR2 workarounds José Roberto de Souza
2021-09-10 13:38 ` Gwan-gyeong Mun
2021-09-10 16:29 ` Souza, Jose
2021-09-13 16:09 ` Gwan-gyeong Mun
2021-09-13 17:00 ` Souza, Jose [this message]
2021-09-14 12:39 ` Gwan-gyeong Mun
2021-09-09 23:07 ` [Intel-gfx] [PATCH 3/5] drm/i915/display: Wait at least 2 frames before selective update José Roberto de Souza
2021-09-10 13:26 ` Gwan-gyeong Mun
2021-09-09 23:07 ` [Intel-gfx] [PATCH 4/5] drm/i915/display/psr: Use drm damage helpers to calculate plane damaged area José Roberto de Souza
2021-09-13 16:03 ` Gwan-gyeong Mun
2021-09-13 16:45 ` Souza, Jose
2021-09-14 12:42 ` Gwan-gyeong Mun
2021-09-09 23:07 ` [Intel-gfx] [PATCH 5/5] drm/i915/display: Workaround cursor left overs with PSR2 selective fetch enabled José Roberto de Souza
2021-09-10 13:29 ` Gwan-gyeong Mun
2021-09-10 0:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/5] drm/i915/display/adlp: Fix PSR2_MAN_TRK_CTL_SU_REGION_END_ADDR calculation Patchwork
2021-09-10 0:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-09-10 2:26 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-09-10 13:39 ` [Intel-gfx] [PATCH 1/5] " Gwan-gyeong Mun
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=b8fea6042bf07bb1dc9a45482ada74fc9f5d0f95.camel@intel.com \
--to=jose.souza@intel.com \
--cc=gwan-gyeong.mun@intel.com \
--cc=intel-gfx@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