drm/i915: Track pinned vma in intel_plane_state
With atomic plane states we are able to track an allocation right from preparation, during use and through to the final free after being swapped out for a new plane. We can couple the VMA we pin for the framebuffer (and its rotation) to this lifetime and avoid all the clumsy lookups in between. v2: Remove residual vma on plane cleanup (Chris) v3: Add a description for the vma destruction in intel_plane_destroy_state (Maarten) References: https://bugs.freedesktop.org/show_bug.cgi?id=98829 Signed-off-by:Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by:
Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/20170116152131.18089-1-chris@chris-wilson.co.uk Acked-by:
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Showing
- drivers/gpu/drm/i915/i915_drv.h 4 additions, 12 deletionsdrivers/gpu/drm/i915/i915_drv.h
- drivers/gpu/drm/i915/intel_atomic_plane.c 20 additions, 0 deletionsdrivers/gpu/drm/i915/intel_atomic_plane.c
- drivers/gpu/drm/i915/intel_display.c 47 additions, 83 deletionsdrivers/gpu/drm/i915/intel_display.c
- drivers/gpu/drm/i915/intel_drv.h 7 additions, 2 deletionsdrivers/gpu/drm/i915/intel_drv.h
- drivers/gpu/drm/i915/intel_fbc.c 20 additions, 32 deletionsdrivers/gpu/drm/i915/intel_fbc.c
- drivers/gpu/drm/i915/intel_fbdev.c 2 additions, 2 deletionsdrivers/gpu/drm/i915/intel_fbdev.c
- drivers/gpu/drm/i915/intel_sprite.c 4 additions, 4 deletionsdrivers/gpu/drm/i915/intel_sprite.c
Loading
Please register or sign in to comment