diff options
| author | Paulo Zanoni | 2014-04-01 20:37:16 +0200 |
|---|---|---|
| committer | Daniel Vetter | 2014-04-01 23:09:29 +0200 |
| commit | 337ba0175f49b2d3a0bcc893f97f539bda831007 (patch) | |
| tree | d8e22e527832271cee020e2270315842b846f836 /drivers/memstick | |
| parent | drm/i915: add GEN5_IRQ_INIT (diff) | |
| download | kernel-qcow2-linux-337ba0175f49b2d3a0bcc893f97f539bda831007.tar.gz kernel-qcow2-linux-337ba0175f49b2d3a0bcc893f97f539bda831007.tar.xz kernel-qcow2-linux-337ba0175f49b2d3a0bcc893f97f539bda831007.zip | |
drm/i915: check if IIR is still zero at postinstall on Gen5+
It should already be masked and disabled and zeroed at the preinstall
and uninstall stages. Also, the current code just writes to IIR once,
and this is not a guarantee that it will be cleared, so it's wrong
anyway.
The whole reason for the paranoia is that we're going to start calling
the IRQ preinstall/postinstall/uninstall from the runtime PM
callbacks, so we need to make sure everything is behaving as expected.
v2: - Change the original DRM_ERROR to WARN and clear IIR in case it's
not zero (Ben).
- Improve commit message (Daniel).
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/memstick')
0 files changed, 0 insertions, 0 deletions