From: Daniel Vetter Date: Fri, 14 Feb 2014 13:01:14 +0000 (+0100) Subject: drm/i915: Don't set PIN_MAPPABLE for legacy ringbuffers X-Git-Tag: accepted/tizen/common/20141203.182822~254^2~59^2~8 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=be1fa129f5a31e78ce0a692f0e30c2ff0fad9ebe;p=platform%2Fkernel%2Flinux-arm64.git drm/i915: Don't set PIN_MAPPABLE for legacy ringbuffers Tighter code since legacy gem has only mappable anyway. Split out from Chris vma-bind rework. Note that this is only possible due to the split-up of the mappable pin flag into PIN_GLOBAL and PIN_MAPPABLE. Cc: Chris Wilson Cc: Ben Widawsky Reviewed-by: Chris Wilson Signed-off-by: Daniel Vetter --- diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c index 0fd6ba0..bcaa149 100644 --- a/drivers/gpu/drm/i915/intel_ringbuffer.c +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c @@ -1920,7 +1920,7 @@ int intel_init_render_ring_buffer(struct drm_device *dev) return -ENOMEM; } - ret = i915_gem_obj_ggtt_pin(obj, 0, PIN_MAPPABLE); + ret = i915_gem_obj_ggtt_pin(obj, 0, 0); if (ret != 0) { drm_gem_object_unreference(&obj->base); DRM_ERROR("Failed to ping batch bo\n");