drm/i915: Track when an object is pinned for use by the display engine
authorChris Wilson <chris@chris-wilson.co.uk>
Fri, 9 Aug 2013 11:25:09 +0000 (12:25 +0100)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Sat, 10 Aug 2013 09:19:51 +0000 (11:19 +0200)
commitcc98b413c197c4c6a62b1e469e9d05e613571af5
treec4e606ee5c8f1801b9a4a45a589224bd014d1770
parentc76ce038e31a2b30bc3dd816f0aefaf685097a0a
drm/i915: Track when an object is pinned for use by the display engine

The display engine has unique coherency rules such that it requires
special handling to ensure that all writes to cursors, scanouts and
sprites are clflushed. This patch introduces the infrastructure to
simply track when an object is being accessed by the display engine.

v2: Explain the is_pin_display() magic as the sources for obj->pin_count
and their individual rules is not obvious. (Ville)

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drivers/gpu/drm/i915/i915_debugfs.c
drivers/gpu/drm/i915/i915_drv.h
drivers/gpu/drm/i915/i915_gem.c
drivers/gpu/drm/i915/intel_display.c