drm/i915/display: Be explicit in handling the preallocated vma

Browse source

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

...

This commit is contained in:

Chris Wilson 2020-02-04 09:48:02 +00:00

parent 1586f6200f

commit 9c4ce97d80

5 changed files with 101 additions and 124 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

140

drivers/gpu/drm/i915/display/intel_display.c

View file

1

drivers/gpu/drm/i915/display/intel_display_types.h

View file

82

drivers/gpu/drm/i915/gem/i915_gem_stolen.c

View file

1

drivers/gpu/drm/i915/gem/i915_gem_stolen.h

View file

1

drivers/gpu/drm/i915/gt/intel_rc6.c

View file