summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/check-perf-trace.py
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2014-05-30 17:35:26 +0400
committerDaniel Vetter <daniel.vetter@ffwll.ch>2014-06-05 10:52:45 +0400
commit4b0e333ee1100e621c5530d368a3029d41131214 (patch)
tree60dd289e0e97f538f37b57c67f97217d7db6f8a5 /tools/perf/scripts/python/check-perf-trace.py
parentc9cd7b65db50175a5f1ff64bbad6d5affdad6aba (diff)
downloadlinux-4b0e333ee1100e621c5530d368a3029d41131214.tar.xz
drm/i915: Always apply cursor width changes
It is possible for userspace to create a big object large enough for a 256x256, and then switch over to using it as a 64x64 cursor. This requires the cursor update routines to check for a change in width on every update, rather than just when the cursor is originally enabled. This also fixes an issue with 845g/865g which cannot change the base address of the cursor whilst it is active. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> [Antti:rebased, adjusted macro names and moved some lines, no functional changes] Reviewed-by: Antti Koskipaa <antti.koskipaa@linux.intel.com> Tested-by: Antti Koskipaa <antti.koskipaa@linux.intel.com> Cc: stable@vger.kernel.org Testcase: igt/kms_cursor_crc/cursor-size-change Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions