From: Chris Wilson Date: Tue, 17 Apr 2012 14:31:31 +0000 (+0100) Subject: drm/i915: Refactor put_fence() to use the common fence writing routine X-Git-Tag: v3.5-rc1~83^2~81^2~13 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=61050808bb019ebea966b7b5bfd357aaf219fb51;p=pandora-kernel.git 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 Signed-off-by: Daniel Vetter --- Reading git-diff-tree failed