From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update
Date: Mon, 9 Jul 2018 12:38:47 -0700 [thread overview]
Message-ID: <20180709193847.GH28253@intel.com> (raw)
In-Reply-To: <1531166308.26763.23.camel@intel.com>
On Mon, Jul 09, 2018 at 12:58:28PM -0700, Dhinakaran Pandiyan wrote:
> On Mon, 2018-07-09 at 12:24 -0700, Rodrigo Vivi wrote:
> > On Mon, Jul 09, 2018 at 11:30:00AM -0700, Dhinakaran Pandiyan wrote:
> > >
> > > On Sun, 2018-07-08 at 18:46 -0700, Tarun Vyas wrote:
> > > >
> > > > In commit "drm/i915: Wait for PSR exit before checking for vblank
> > > > evasion", the idea was to limit the PSR IDLE checks when PSR is
> > > > actually supported. While CAN_PSR does do that check, it doesn't
> > > > applies on a per-crtc basis. crtc_state->has_psr is a more
> > > > granular
> > > > check that avoids everything but pipe A, for the PSR IDLE check.
> > > >
> > > > With this, the PSR IDLE check should be a *no-op* for all but
> > > > pipe A
> > > > which is what was intended originally.
> > > >
> > > So, the problem is when we update a non-PSR pipe (B or C) and PSR
> > > is
> > > active on another pipe(A, specifically), we end up waiting for the
> > > pipe
> > > A MMIO to become idle.
> > >
> > > Can you please update the commit message as the commit message
> > > makes
> > > the per-pipe check sound like an optimization?
> > I truly doubt that multiple PSR pipes case doesn't work in our
> > driver.
> > if that works I'd assume it is by coincidence :P
> >
> > >
> > > This also points to a gap in our testing, I don't see a two pipe
> > > PSR
> > > related IGT.
> > The almost impossible mission here is to find any design with 2 eDP
> > connectors and both panels with PSR.
> >
> I meant, two pipes with PSR on one of them. I looked at the frontbuffer
> _tracking@psr subtests in https://intel-gfx-ci.01.org/tree/drm-tip/drmt
> ip.html, none of them were "2p". Ideally, a pipe update on a non-PSR
> pipe would have triggered this failure in CI.
oh I see... you are right...
>
>
> > >
> > >
> > > >
> > > > Fixes: a608987970b9 ("drm/i915: Wait for PSR exit before checking
> > > > for
> > > > vblank evasion")
> > > >
> > > > v2: Remove unnecessary parantheses, make checkpatch happy.
> > > >
> > > > Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
I take it back, sorry ;)
> > > > Signed-off-by: Tarun Vyas <tarun.vyas@intel.com>
> > > > ---
> > > > drivers/gpu/drm/i915/intel_sprite.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/intel_sprite.c
> > > > b/drivers/gpu/drm/i915/intel_sprite.c
> > > > index 4990d6e84ddf..83880e3a5f3d 100644
> > > > --- a/drivers/gpu/drm/i915/intel_sprite.c
> > > > +++ b/drivers/gpu/drm/i915/intel_sprite.c
> > > > @@ -118,7 +118,7 @@ void intel_pipe_update_start(const struct
> > > > intel_crtc_state *new_crtc_state)
> > > > * VBL interrupts will start the PSR exit and prevent a
> > > > PSR
> > > > * re-entry as well.
> > > > */
> > > > - if (CAN_PSR(dev_priv) &&
> > > > intel_psr_wait_for_idle(dev_priv))
> > > > + if (new_crtc_state->has_psr &&
> > > > intel_psr_wait_for_idle(dev_priv))
> > > > DRM_ERROR("PSR idle timed out, atomic update may
> > > > fail\n");
> > > >
> > > > local_irq_disable();
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-07-09 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 1:46 [PATCH v2] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update Tarun Vyas
2018-07-09 2:11 ` ✓ Fi.CI.BAT: success for drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update (rev2) Patchwork
2018-07-09 3:09 ` ✓ Fi.CI.IGT: " Patchwork
2018-07-09 18:30 ` [PATCH v2] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update Dhinakaran Pandiyan
2018-07-09 18:16 ` Tarun Vyas
2018-07-09 18:58 ` Dhinakaran Pandiyan
2018-07-09 19:52 ` Tarun Vyas
2018-07-09 20:31 ` Dhinakaran Pandiyan
2018-07-09 20:24 ` Tarun Vyas
2018-07-09 19:24 ` Rodrigo Vivi
2018-07-09 19:58 ` Dhinakaran Pandiyan
2018-07-09 19:38 ` Rodrigo Vivi [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=20180709193847.GH28253@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dhinakaran.pandiyan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.