drm/i915: Track when an object is pinned for use by the display engine

Browse source

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>

...

This commit is contained in:

Chris Wilson 2013-08-09 12:25:09 +01:00 • committed by Daniel Vetter

parent c76ce038e3

commit cc98b413c1

4 changed files with 42 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

drivers/gpu/drm/i915/i915_debugfs.c

View file

2

drivers/gpu/drm/i915/i915_drv.h

View file

36

drivers/gpu/drm/i915/i915_gem.c

View file

8

drivers/gpu/drm/i915/intel_display.c

View file