From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "Hogander, Jouni" <jouni.hogander@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915: Do not enable PSR2/selective fetch if there are no planes
Date: Wed, 15 Jun 2022 10:43:41 +0300 [thread overview]
Message-ID: <20220615074341.GA19772@intel.com> (raw)
In-Reply-To: <bfcd24764e38db1fd13a1315106cb71dac0d7d01.camel@intel.com>
On Tue, Jun 14, 2022 at 03:55:04PM +0300, Hogander, Jouni wrote:
> On Tue, 2022-06-14 at 15:22 +0300, Stanislav Lisovskiy wrote:
> > We seem to enable PSR2 and selective fetch even if there are no
> > active
> > planes. That seems to causes FIFO underruns at least for ADLP.
> > Those are gone if we don't do that. Just adding simple check
> > in intel_psr2_sel_fetch_config_valid seems to do the trick.
>
> We are already disabling PSR intel_psr_pre_plane_update if
> active_planes is 0.
>
> We are also checking active_planes in _intel_psr_post_plane_update and
> not enabling PSR if it's 0.
>
> So I'm now wondering what sequence this patch is actually changing?
> I.e. where PSR is currently enabled/not disabled if active_planes == 0?
Good question! Apparently we still do it, because without this change
we get FIFO underruns, while with that one we don't.
I have suspicion that this happens during modeset, however you are right
we need to know for sure.
I will get back here and post the exact call trace.
One thing I can say for sure that we do it somewhere, otherwise adding
this wouldn't have any effect.
Stan
>
> > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_psr.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> > b/drivers/gpu/drm/i915/display/intel_psr.c
> > index 7d61c55184e5..03add69cfdca 100644
> > --- a/drivers/gpu/drm/i915/display/intel_psr.c
> > +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> > @@ -747,6 +747,12 @@ static bool
> > intel_psr2_sel_fetch_config_valid(struct intel_dp *intel_dp,
> > return false;
> > }
> >
> > + if (hweight32(crtc_state->active_planes) == 0) {
> > + drm_dbg_kms(&dev_priv->drm,
> > + "PSR2 sel fetch not enabled, no
> > active_planes\n");
> > + return false;
> > + }
> > +
> > /* Wa_14010254185 Wa_14010103792 */
> > if (IS_TGL_DISPLAY_STEP(dev_priv, STEP_A0, STEP_C0)) {
> > drm_dbg_kms(&dev_priv->drm,
>
next prev parent reply other threads:[~2022-06-15 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 12:22 [Intel-gfx] [PATCH 0/1] Do not enable PSR2 if no active planes Stanislav Lisovskiy
2022-06-14 12:22 ` [Intel-gfx] [PATCH 1/1] drm/i915: Do not enable PSR2/selective fetch if there are no planes Stanislav Lisovskiy
2022-06-14 12:55 ` Hogander, Jouni
2022-06-15 7:43 ` Lisovskiy, Stanislav [this message]
2022-06-15 9:01 ` Lisovskiy, Stanislav
2022-06-14 16:46 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Do not enable PSR2 if no active planes Patchwork
2022-06-15 12:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Do not enable PSR2 if no active planes (rev2) Patchwork
2022-06-15 18:12 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-06-16 12:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Do not enable PSR2 if no active planes (rev3) Patchwork
2022-06-16 17:59 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20220615074341.GA19772@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jouni.hogander@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