OSDN Git Service

drm/i915/display: Be explicit in handling the preallocated vma
authorChris Wilson <chris@chris-wilson.co.uk>
Tue, 4 Feb 2020 09:48:02 +0000 (09:48 +0000)
committerChris Wilson <chris@chris-wilson.co.uk>
Wed, 5 Feb 2020 09:20:39 +0000 (09:20 +0000)
commit9c4ce97d80257ff48f850a6f13fd9a8f7b37a6e4
treefac852b85cbb8ac1b1c2cab9b148c8da0a381414
parent1586f6200f69d65a49158c5d0823460568d850f7
drm/i915/display: Be explicit in handling the preallocated vma

As only the display codes tries to pin its preallocated framebuffer into
an exact location in the GGTT, remove the convenience function and make
the pin management explicit in the display code. Then throughout the
display management, we track the framebuffer and its plane->vma; with
less single purpose code and ready for first class i915_vma.

In doing so, this should fix the BUG_ON(vma->pages) on fi-kbl-soraka.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200204094801.877288-2-chris@chris-wilson.co.uk
drivers/gpu/drm/i915/display/intel_display.c
drivers/gpu/drm/i915/display/intel_display_types.h
drivers/gpu/drm/i915/gem/i915_gem_stolen.c
drivers/gpu/drm/i915/gem/i915_gem_stolen.h
drivers/gpu/drm/i915/gt/intel_rc6.c