From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
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 12:23:47 +0200 [thread overview]
Message-ID: <20140827102347.GO15520@phenom.ffwll.local> (raw)
In-Reply-To: <20140827085158.GC13629@nuc-i3427.alporthouse.com>
On Wed, Aug 27, 2014 at 09:51:58AM +0100, Chris Wilson wrote:
> On Wed, Aug 27, 2014 at 10:43:37AM +0200, Daniel Vetter 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.
>
> Is there a reason why setting up the pipestat prior to enabling
> interrupts is verboten, or is it just not done today?
The similar warning on pch platforms was added to catch runtime pm bugs
where someone enabled some interrupt source, but didn't hold a runtime pm
reference. That's just not going to work. So motivation for this patch is
vlv/chv runtime pm really.
But I also think that this check provides value for driver
load/resume/suspend since if we change interrupt settings after the
interrupts have been disabled or before enabling something is at least
fishy. At least insofar as that our irq install hooks nowadays overwrite
all of them with default values.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-08-27 10:23 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 [this message]
2014-08-27 11:28 ` Chris Wilson
2014-08-27 13:29 ` Daniel Vetter
2014-08-27 23:00 ` Jesse Barnes
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=20140827102347.GO15520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--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