public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Check for underruns after crtc disable
Date: Tue, 24 Nov 2015 16:21:53 +0200	[thread overview]
Message-ID: <20151124142153.GH4437@intel.com> (raw)
In-Reply-To: <20151124141423.GF17050@phenom.ffwll.local>

On Tue, Nov 24, 2015 at 03:14:23PM +0100, Daniel Vetter wrote:
> On Mon, Nov 23, 2015 at 02:42:21PM +0000, Chris Wilson wrote:
> > On Mon, Nov 23, 2015 at 04:10:32PM +0200, Ville Syrjälä wrote:
> > > On Sat, Nov 21, 2015 at 10:49:04AM +0000, Chris Wilson wrote:
> > > > On Fri, Nov 20, 2015 at 10:09:20PM +0200, ville.syrjala@linux.intel.com wrote:
> > > > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > > 
> > > > > To get a better idea if underruns occurred during crtc disabling,
> > > > > let's check for them explicitly. This helps in cases where the
> > > > > error interrupt isn't active, or there is no underrun interrupt
> > > > > support at all.
> > > > > 
> > > > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > 
> > > > Would this be better the vblank after enabling?
> > > 
> > > We do that too.
> > 
> > Oh, crtc disabling. I can't read.
> 
> Hm, should we also double-check before disabling, to catch anything that
> happened right before the modeset and avoid confusing it with underruns
> happening during the modeset?

Hmm. Yeah that might be a decent idea. Although we don't wait for the
planes to be disabled before we disable the pipe so in theory some weird
underrun stemming from the plane disable might still get mixed in there.

> 
> But this is a good idea already.
> 
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-11-24 14:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 20:09 [PATCH 1/3] drm/i915: Suppress spurious CPU FIFO underruns on ILK-IVB ville.syrjala
2015-11-20 20:09 ` [PATCH 2/3] drm/i915: Disable CPU underruns around eDP port and vdd enable " ville.syrjala
2015-11-21 10:52   ` Chris Wilson
2015-11-20 20:09 ` [PATCH 3/3] drm/i915: Check for underruns after crtc disable ville.syrjala
2015-11-21 10:49   ` Chris Wilson
2015-11-23 14:10     ` Ville Syrjälä
2015-11-23 14:42       ` Chris Wilson
2015-11-24 14:14         ` Daniel Vetter
2015-11-24 14:21           ` Ville Syrjälä [this message]
2015-11-21 10:51 ` [PATCH 1/3] drm/i915: Suppress spurious CPU FIFO underruns on ILK-IVB Chris Wilson
2015-11-23 14:22   ` Ville Syrjälä
2015-11-23 14:28     ` Chris Wilson
2015-11-23 14:55       ` Ville Syrjälä
2015-11-24 14:09         ` Daniel Vetter
2015-11-24 14:16 ` Daniel Vetter
2015-11-24 14:52   ` Ville Syrjälä

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=20151124142153.GH4437@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --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