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 <intel-gfx@lists.freedesktop.org>
Subject: Re: IEGD to xf86-video-intel
Date: Thu, 16 Jan 2014 16:11:49 +0200	[thread overview]
Message-ID: <20140116141149.GM9454@intel.com> (raw)
In-Reply-To: <CAKMK7uFBmt4E4NfOPNQyRp01Z5ZUqFMA4KQz97Sa_dcMcpkWAw@mail.gmail.com>

On Thu, Jan 16, 2014 at 03:00:26PM +0100, Daniel Vetter wrote:
> On Thu, Jan 16, 2014 at 2:28 PM, Ville Syrjälä
> <ville.syrjala@linux.intel.com> wrote:
> > On Thu, Jan 16, 2014 at 01:41:32PM +0100, Dragos Carp wrote:
> >> Hi Jani,
> >>
> >> thank you for your response.
> >> Attached is the dmesg output trimmed of more thousand lines like:
> >> [drm:i915_irq_handler], pipe B underrun
> >
> > That's a bit weird. We're supposed to disable the underrun reporting
> > after the first error. I guess the pipe state gets stuck somehow and
> > it just keeps reporting the same error all the time...
> 
> Only on pch platforms, but not on gmch stuff. Those still lack a bit
> of work to make them fit into the underrun reporting framework. And we
> need to enable those underruns to be much louder ...

Oh right. Somehow I remembered that it was universal. But now that
re-think things PIPESTAT doesn't even have an enable bit for underruns.
So I guess an underrun won't itself generate an interrupt on gmch
platforms, but instead you need some other interrupt to fire to detect
it. That means we should just have some flag/bool to shut up the debug
message and the rest of the code is fine as is.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-01-16 14:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 22:52 IEGD to xf86-video-intel Dragoș Carp
2014-01-16  9:03 ` Jani Nikula
2014-01-16 12:41   ` Dragos Carp
2014-01-16 13:07     ` Jani Nikula
2014-01-16 14:37       ` Dragos Carp
2014-01-16 13:28     ` Ville Syrjälä
2014-01-16 14:00       ` Daniel Vetter
2014-01-16 14:11         ` Ville Syrjälä [this message]
2014-01-16 14:34           ` Daniel Vetter
2014-01-16  9:44 ` [PATCH] drm/i915: Get LVDS preferred mode from SDVO output timings if there's nothing else ville.syrjala
  -- strict thread matches above, loose matches on Subject: below --
2014-01-15  9:31 IEGD to xf86-video-intel Dragoș Carp
2014-01-15 20:49 Dragoș Carp

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=20140116141149.GM9454@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