]> git.baikalelectronics.ru Git - kernel.git/commit
drm/i915: Use safer intel_uncore_wait_for_register in ring-init
authorChris Wilson <chris@chris-wilson.co.uk>
Tue, 11 Apr 2017 10:13:40 +0000 (11:13 +0100)
committerChris Wilson <chris@chris-wilson.co.uk>
Tue, 11 Apr 2017 11:50:44 +0000 (12:50 +0100)
commitde9627d83d5541db947b1aa2483814952a658411
treefca3ff1680b1ec50acdabc79f49fee305f8d30a1
parent5bd01406e6b0372808f6b639e305aff7a8266113
drm/i915: Use safer intel_uncore_wait_for_register in ring-init

While we do hold the forcewake for legacy ringbuffer initialisation, we
don't guard our access with the uncore.lock spinlock. In theory, we only
initialise when no others should be accessing the same mmio cachelines,
but in practice be safe as this is an infrequently used path and not
worth risky micro-optimisations.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170411101340.31994-5-chris@chris-wilson.co.uk
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
drivers/gpu/drm/i915/intel_ringbuffer.c