diff options
author | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2015-10-22 12:34:57 (GMT) |
---|---|---|
committer | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2015-10-26 14:28:21 (GMT) |
commit | 4018169704e01af8c9a46105bcaf9e4f583bdfdc (patch) | |
tree | aa771c07b0b7e8a1110e2ce8cc2c70c8a3cec443 /.mailmap | |
parent | 75aa3f6307f01b46ea78b81ac257e24c3753e51d (diff) | |
download | linux-4018169704e01af8c9a46105bcaf9e4f583bdfdc.tar.xz |
drm/i915: Read FORCEWAKE registers with I915_READ_FW()
Change FORCEWAKE & co. reads for the error state to use I915_READ_FW().
Reading a FORCEWAKE register using a function that can frob forcewake
just seems wrong.
There is a check to skip grabbing the forcewake for accessing FORCEWAKE
in intel_uncore.c, but there's no such check for FORCEWAKE_MT. So no
idea what is currently happening with FORCEWAKE_MT reads. FORCEWAKE_VLV
is fortunately outside the forcewake range anyway, so no actual issue
with that one.
So let's just make the rule that you can't access FORCEWAKE registers with
the normal I915_READ() stuff, and we can drop the extra FORCEWAKE check
from NEEDS_FORCEWAKE(). While at it use NEEDS_FORCEWAKE() on BDW, where
it was skipped for whatever bikeshed reason that I've already forgotten.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1445517300-28173-3-git-send-email-ville.syrjala@linux.intel.com
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions