drm/i915: Refactor put_fence() to use the common fence writing routine
authorChris Wilson <chris@chris-wilson.co.uk>
Tue, 17 Apr 2012 14:31:31 +0000 (15:31 +0100)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Wed, 18 Apr 2012 11:34:30 +0000 (13:34 +0200)
commit61050808bb019ebea966b7b5bfd357aaf219fb51
tree72cc9ecdf833fc3bee5e66355acf985f1e3e964e
parent9ce079e4812c41c5f4ee9ea116c768b8939197d6
drm/i915: Refactor put_fence() to use the common fence writing routine

One clarification that we make is to the existing semantics of
obj->tiling_changed to only mean that we need to update an associated
fence register (including the NO_FENCE when executing an untiled but
fenced GPU command). If we do not have a fence register or pending
fenced GPU access for the object (after put_fence() for example), then
we can clear the tiling_changed flag as any fence will necessarily be
rewritten upon acquisition.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drivers/gpu/drm/i915/i915_gem.c