drm/i915: Move assertion for iomap access to i915_vma_pin_iomap
authorChris Wilson <chris@chris-wilson.co.uk>
Mon, 15 Aug 2016 09:48:56 +0000 (10:48 +0100)
committerChris Wilson <chris@chris-wilson.co.uk>
Mon, 15 Aug 2016 10:01:04 +0000 (11:01 +0100)
commite5cdb22b2799f2729930ef6394378570c66da251
tree94675775cb130c816c9147039dbbf3ec1d476568
parent7abc98fadfdd060e54fdb7172e2753a2f9808366
drm/i915: Move assertion for iomap access to i915_vma_pin_iomap

Access through the GTT requires the device to be awake. Ideally
i915_vma_pin_iomap() is short-lived and the pinning demarcates the
access through the iomap. This is not entirely true, we have a mixture
of long lived pins that exceed the wakelock (such as legacy ringbuffers)
and short lived pin that do live within the wakelock (such as execlist
ringbuffers).

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1471254551-25805-17-git-send-email-chris@chris-wilson.co.uk
drivers/gpu/drm/i915/i915_gem_gtt.c
drivers/gpu/drm/i915/intel_ringbuffer.c