public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: WARN if interrupts aren't on in en/disable_pipestat
Date: Wed, 27 Aug 2014 16:00:22 -0700	[thread overview]
Message-ID: <20140827160022.2a8fe834@jbarnes-desktop> (raw)
In-Reply-To: <1409129017-16857-1-git-send-email-daniel.vetter@ffwll.ch>

On Wed, 27 Aug 2014 10:43:37 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:

> Now that vlv has runtime pm we kinda should check for that like on the
> pch split platforms. Looks like this was simply lost in the vlv rpm
> enabling.
> 
> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Cc: Imre Deak <imre.deak@intel.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
>  drivers/gpu/drm/i915/i915_irq.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 9eb303c1b621..76bc4d0de5a4 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -589,6 +589,7 @@ __i915_enable_pipestat(struct drm_i915_private *dev_priv, enum pipe pipe,
>  	u32 pipestat = I915_READ(reg) & PIPESTAT_INT_ENABLE_MASK;
>  
>  	assert_spin_locked(&dev_priv->irq_lock);
> +	WARN_ON(!intel_irqs_enabled(dev_priv));
>  
>  	if (WARN_ONCE(enable_mask & ~PIPESTAT_INT_ENABLE_MASK ||
>  		      status_mask & ~PIPESTAT_INT_STATUS_MASK,
> @@ -615,6 +616,7 @@ __i915_disable_pipestat(struct drm_i915_private *dev_priv, enum pipe pipe,
>  	u32 pipestat = I915_READ(reg) & PIPESTAT_INT_ENABLE_MASK;
>  
>  	assert_spin_locked(&dev_priv->irq_lock);
> +	WARN_ON(!intel_irqs_enabled(dev_priv));
>  
>  	if (WARN_ONCE(enable_mask & ~PIPESTAT_INT_ENABLE_MASK ||
>  		      status_mask & ~PIPESTAT_INT_STATUS_MASK,

Yeah looks good, wonder if it'll trigger any new warnings.

Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>

-- 
Jesse Barnes, Intel Open Source Technology Center

  parent reply	other threads:[~2014-08-27 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  8:43 [PATCH] drm/i915: WARN if interrupts aren't on in en/disable_pipestat Daniel Vetter
2014-08-27  8:51 ` Chris Wilson
2014-08-27 10:23   ` Daniel Vetter
2014-08-27 11:28     ` Chris Wilson
2014-08-27 13:29       ` Daniel Vetter
2014-08-27 23:00 ` Jesse Barnes [this message]
2014-09-04 15:59   ` Daniel Vetter
2014-09-04 16:24     ` Jesse Barnes
2014-09-04 16:59       ` Daniel Vetter
2014-09-04 17:36         ` Jesse Barnes
2014-09-08  8:18   ` Daniel Vetter

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=20140827160022.2a8fe834@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@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