All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: Tarun Vyas <tarun.vyas@intel.com>
Cc: intel-gfx@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [PATCH v2] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update
Date: Mon, 09 Jul 2018 13:31:52 -0700	[thread overview]
Message-ID: <1531168312.4283.5.camel@intel.com> (raw)
In-Reply-To: <20180709195251.GA82530@otc-chromeosbuild-5>

On Mon, 2018-07-09 at 12:52 -0700, Tarun Vyas wrote:
> On Mon, Jul 09, 2018 at 11:58:52AM -0700, Dhinakaran Pandiyan wrote:
> > 
> > On Mon, 2018-07-09 at 11:16 -0700, Tarun Vyas 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.

I looked at the code and spec again, PSR isn't tied to "pipe A" The
driver allows PSR only on "port A" + "transcoder eDP", but the pipe
itself can be any one of the possible options.

> > > > > 
> > > > > 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? 
> > > > 
> > > > This also points to a gap in our testing, I don't see a two
> > > > pipe
> > > > PSR
> > > > related IGT.
> > > > 
> > > That's right. On my KBL chromebook that's running the drm-tip,
> > > when I
> > > plug-in an external display, so pipe B,
> > > I see "[drm:intel_pipe_update_start] *ERROR* PSR idle timed out,
> > > atomic update may fail on pipe B", Iadded the pipe
> > > name in the DRM_ERROR, may be I should make that change in the v3
> > > of
> > > this patch along with updating the commit message.
> > > 
> > > But, yea, this proves that with the CAN_PSR check, the non-PSR
> > > pipes
> > > (B/C) wait on pipe-A to exit PSR which doesn't have
> > > any reason to do so at that moment, hence the error.
> > > 
> > > I'll make the commit message changes and add the pipe name in the
> > > DRM_ERROR as well ?
> > I am thinking you could pass crtc_state
> > to intel_psr_wait_for_idle()
> > and then check inside the implementation if the argument is the
> > same as
> > the pipe PSR was enabled on and then wait.
> > 
> > intel_psr_wait_for_idle(crtc_state) {
> > 	if (!CAN_PSR() || !crtc_state->has_psr)
> > 		return;
> > 	...
> > }
> Hmm, but the CAN_PSR check is already taken care of by
> intel_psr_compute_config() which then sets has_psr, so just
> 	if (!crtc_state->has_psr)
> 		return;
> should suffice, right ?
> 
Yeah, we can assume at this point state->has_psr is set correctly.

> But then, we incur a function call for non-PSR pipes, which will
> return right away.

That should be okay, having the PSR related check inside the function
looks cleaner IMO. 

> > 
> > 
> > I don't like how intel_psr_wait_for_idle() doesn't care which pipe
> > (transcoder actually) MMIO it should wait on.
> > 		
> > 
> > > 
> > > > 
> > > > 
> > > > > 
> > > > > 
> > > > > 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>
> > > > > 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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-07-09 20:05 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 [this message]
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

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=1531168312.4283.5.camel@intel.com \
    --to=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=tarun.vyas@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 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.