From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: Tarun Vyas <tarun.vyas@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, rodrigo.vivi@intel.com
Subject: Re: [PATCH v8 2/2] drm/i915: Wait for PSR exit before checking for vblank evasion
Date: Mon, 02 Jul 2018 11:40:51 -0700 [thread overview]
Message-ID: <1530556851.2736.4.camel@intel.com> (raw)
In-Reply-To: <1530314774.25977.5.camel@intel.com>
On Fri, 2018-06-29 at 16:26 -0700, Dhinakaran Pandiyan wrote:
> On Wed, 2018-06-27 at 13:02 -0700, Tarun Vyas wrote:
> >
> > The PIPEDSL freezes on PSR entry and if PSR hasn't fully exited,
> > then
> > the pipe_update_start call schedules itself out to check back
> > later.
> >
> > On ChromeOS-4.4 kernel, which is fairly up-to-date w.r.t drm/i915
> > but
> > lags w.r.t core kernel code, hot plugging an external display
> > triggers
> > tons of "potential atomic update errors" in the dmesg, on *pipe A*.
> > A
> > closer analysis reveals that we try to read the scanline 3 times
> > and
> > eventually timeout, b/c PSR hasn't exited fully leading to a
> > PIPEDSL
> > stuck @ 1599. This issue is not seen on upstream kernels, b/c for
> > *some*
> > reason we loop inside intel_pipe_update start for ~2+ msec which in
> > this
> > case is more than enough to exit PSR fully, hence an *unstuck*
> > PIPEDSL
> > counter, hence no error. On the other hand, the ChromeOS kernel
> > spends
> > ~1.1 msec looping inside intel_pipe_update_start and hence errors
> > out
> > b/c the source is still in PSR.
> >
> > Regardless, we should wait for PSR exit (if PSR is disabled, we
> > incur
> > a ~1-2 usec penalty) before reading the PIPEDSL, b/c if we haven't
> > fully exited PSR, then checking for vblank evasion isn't actually
> > applicable.
> >
> > v4: Comment explaining psr_wait after enabling VBL interrupts (DK)
> >
> > v5: CAN_PSR() to handle platforms that don't support PSR.
> >
> > v6: Handle local_irq_disable on early return (Chris)
>
> Series Reviewed-by: Dhinakaran Pandiyan
> <dhinakaran.pandiyan@intel.com>
>
> Daniel's questions were addressed over IRC, I'll push this version if
> they aren't any other concerns.
and pushed to -dinq with Daniel's irc ack.
"<dhnkrn> ickle: danvet ack on the PSR wait_for_idle series?
<danvet> sure"
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-02 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 20:02 [PATCH v8 1/2] drm/i915/psr: Lockless version of psr_wait_for_idle Tarun Vyas
2018-06-27 20:02 ` [PATCH v8 2/2] drm/i915: Wait for PSR exit before checking for vblank evasion Tarun Vyas
2018-06-29 23:26 ` Dhinakaran Pandiyan
2018-07-02 18:40 ` Dhinakaran Pandiyan [this message]
2018-06-27 20:53 ` ✓ Fi.CI.BAT: success for series starting with [v8,1/2] drm/i915/psr: Lockless version of psr_wait_for_idle Patchwork
2018-06-28 1:41 ` ✓ 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=1530556851.2736.4.camel@intel.com \
--to=dhinakaran.pandiyan@intel.com \
--cc=daniel.vetter@ffwll.ch \
--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.