Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Try to suppress more spurious PCH underruns on ILK-IVB
Date: Fri, 25 May 2018 18:19:17 +0300	[thread overview]
Message-ID: <87d0xj3gqy.fsf@intel.com> (raw)
In-Reply-To: <20180525150250.GC23723@intel.com>

On Fri, 25 May 2018, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Thu, May 24, 2018 at 10:19:02PM +0100, Chris Wilson wrote:
>> Quoting Ville Syrjala (2018-05-24 20:04:05)
>> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> > 
>> > My ILK seems to generate a spurious PCH underrun with most interlaced
>> > HDMI modes. Add a second vblank wait to avoid it.
>> 
>> Fwiw, a second vblank because of interlacing is very believable.

/me .oO( could we wait for the 2nd vblank based on interlace? )

>>  
>> > We have seen some spurious PCH underruns still in CI as well, some
>> > of which seem to be progressive DP. The logs also point towards some
>> > spurious underrins with progressive HDMI on SNB. While I don't have
>> > a solid explanation for those let's try to kill all the birds with one
>> > stone and always do the double wait.
>> > 
>> > Buzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106387
>> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>a
>
> Thanks. Pushed to dinq.
>
>> 
>> No point waiting for a vblank worker? ;)
>
> That might take a while. Also I'm not sure we'd want to use it here
> because we'd probably want underrun reporting to be active by the
> time we enable the planes. So we'd either have to enable planes from
> the worker as well, or we'd just sample the vblank counter at the
> end of crtc_enable and wait for n+2 just before we start to enable the
> planes. Not sure if that latter approach would gain us any practical
> parallelism though.

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-05-25 15:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 19:04 [PATCH 1/2] drm/i915: Try to suppress more spurious PCH underruns on ILK-IVB Ville Syrjala
2018-05-24 19:04 ` [PATCH 2/2] drm/i915: Simplify ilk-ivb underrun suppression Ville Syrjala
2018-05-25 15:20   ` Chris Wilson
2018-05-25 15:43     ` Ville Syrjälä
2018-05-25 15:55       ` Chris Wilson
2018-05-25 19:23         ` Ville Syrjälä
2018-05-24 19:50 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Try to suppress more spurious PCH underruns on ILK-IVB Patchwork
2018-05-24 20:14 ` [PATCH 1/2] " Chris Wilson
2018-05-24 20:15   ` Chris Wilson
2018-05-24 20:31     ` Ville Syrjälä
2018-05-24 21:19 ` Chris Wilson
2018-05-25 15:02   ` Ville Syrjälä
2018-05-25 15:19     ` Jani Nikula [this message]
2018-05-25 15:49       ` Ville Syrjälä
2018-05-25  2:00 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " 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=87d0xj3gqy.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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