diff options
author | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2016-10-12 14:44:47 +0300 |
---|---|---|
committer | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2016-10-17 14:26:42 +0300 |
commit | 862372bc8fefb7bdc243dd120448b970244c8185 (patch) | |
tree | 52577b9562cc3f502c50aa90f84b80e8c8dfdb15 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 06a75ace46e2fdd1d93b06228df0e2dfe526cc27 (diff) |
drm/i915: GMBUS don't need no forcewake
GMBUS is part of the display engine, and thus has no need for
forcewake. Let's not bother trying to grab it then.
I don't recall if the display engine suffers from system hangs
due to multiple accesses to the same "cacheline" in mmio space.
I hope not since we're no longer protected by the uncore lock
since commit 4e6c2d58ba86 ("drm/i915: Take forcewake once for
the entire GMBUS transaction")
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Weinehall <david.weinehall@linux.intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1476272687-15070-1-git-send-email-ville.syrjala@linux.intel.com
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions