Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch, rclark@redhat.com, stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Check for driver readyness before	handling an underrun interrupt
Date: Fri, 27 Feb 2015 09:52:54 +0200	[thread overview]
Message-ID: <87pp8vaizt.fsf@intel.com> (raw)
In-Reply-To: <1424965982-32678-1-git-send-email-chris@chris-wilson.co.uk>

On Thu, 26 Feb 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> When we takeover from the BIOS and install our interrupt handler, the
> BIOS may have left us a few surprises in the form of spontaneous
> interrupts. (This is especially likely on hardware like 965gm where
> display fifo underruns are continuous and the GMCH cannot filter that
> interrupt souce.) As we enable our IRQ early so that we can use it
> during hardware probing, our interrupt handler must be prepared to
> handle a few sources prior to being fully configured. As such, we need
> to add a simple is-ready check prior to dereferencing our KMS state for
> reporting underruns.
>
> Reported-by: Rob Clark <rclark@redhat.com>
> Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1193972

"You are not authorized to access bug #1193972. To see this bug, you
must first log in to an account with the appropriate permissions."

Meh.

> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: stable@vger.kernel.org
> ---
>  drivers/gpu/drm/i915/intel_fifo_underrun.c | 18 +++++++-----------
>  1 file changed, 7 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_fifo_underrun.c b/drivers/gpu/drm/i915/intel_fifo_underrun.c
> index 04e248dd2259..f2fd992e3cd8 100644
> --- a/drivers/gpu/drm/i915/intel_fifo_underrun.c
> +++ b/drivers/gpu/drm/i915/intel_fifo_underrun.c
> @@ -282,16 +282,6 @@ bool intel_set_cpu_fifo_underrun_reporting(struct drm_i915_private *dev_priv,
>  	return ret;
>  }
>  
> -static bool
> -__cpu_fifo_underrun_reporting_enabled(struct drm_i915_private *dev_priv,
> -				      enum pipe pipe)
> -{
> -	struct drm_crtc *crtc = dev_priv->pipe_to_crtc_mapping[pipe];
> -	struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
> -
> -	return !intel_crtc->cpu_fifo_underrun_disabled;
> -}
> -
>  /**
>   * intel_set_pch_fifo_underrun_reporting - set PCH fifo underrun reporting state
>   * @dev_priv: i915 device instance
> @@ -352,9 +342,15 @@ bool intel_set_pch_fifo_underrun_reporting(struct drm_i915_private *dev_priv,
>  void intel_cpu_fifo_underrun_irq_handler(struct drm_i915_private *dev_priv,
>  					 enum pipe pipe)
>  {
> +	struct drm_crtc *crtc = dev_priv->pipe_to_crtc_mapping[pipe];
> +
> +	/* We may be called too early in init, thanks BIOS! */
> +	if (crtc == NULL)
> +		return;
> +
>  	/* GMCH can't disable fifo underruns, filter them. */
>  	if (HAS_GMCH_DISPLAY(dev_priv->dev) &&
> -	    !__cpu_fifo_underrun_reporting_enabled(dev_priv, pipe))
> +	    !to_intel_crtc(crtc)->cpu_fifo_underrun_disabled)
>  		return;
>  
>  	if (intel_set_cpu_fifo_underrun_reporting(dev_priv, pipe, false))
> -- 
> 2.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2015-02-27  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 15:53 [PATCH] drm/i915: Check for driver readyness before handling an underrun interrupt Chris Wilson
2015-02-27  7:52 ` Jani Nikula [this message]
2015-02-27  8:20   ` [Intel-gfx] " Jani Nikula
2015-02-27  9:27     ` Chris Wilson
2015-02-27  9:53       ` Jani Nikula
2015-02-27 14:24       ` Daniel Vetter
2015-02-28 19:16 ` shuang.he

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=87pp8vaizt.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rclark@redhat.com \
    --cc=stable@vger.kernel.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