linux-yocto/drivers/gpu/drm/virtio
Dongwon Kim b04b69819b drm/virtio: New fence for every plane update
[ Upstream commit d3c55b8ab6fe5fa2e7ab02efd36d09c39ee5022f ]

Having a fence linked to a virtio_gpu_framebuffer in the plane update
sequence would cause conflict when several planes referencing the same
framebuffer (e.g. Xorg screen covering multi-displays configured for an
extended mode) and those planes are updated concurrently. So it is needed
to allocate a fence for every plane state instead of the framebuffer.

Signed-off-by: Dongwon Kim <dongwon.kim@intel.com>
[dmitry.osipenko@collabora.com: rebase, fix up, edit commit message]
Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Acked-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
Reviewed-by: Rob Clark <robdclark@gmail.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20241020230803.247419-2-dmitry.osipenko@collabora.com
Signed-off-by: Sasha Levin <sashal@kernel.org>
2025-02-21 13:49:30 +01:00
..
Kconfig
Makefile
virtgpu_debugfs.c
virtgpu_display.c
virtgpu_drv.c drm/virtio: Set segment size for virtio_gpu device 2024-02-23 09:12:37 +01:00
virtgpu_drv.h drm/virtio: New fence for every plane update 2025-02-21 13:49:30 +01:00
virtgpu_fence.c
virtgpu_gem.c
virtgpu_ioctl.c drm/virtio: Conditionally allocate virtio_gpu_fence 2023-09-19 12:27:55 +02:00
virtgpu_kms.c
virtgpu_object.c
virtgpu_plane.c drm/virtio: New fence for every plane update 2025-02-21 13:49:30 +01:00
virtgpu_prime.c
virtgpu_trace_points.c
virtgpu_trace.h
virtgpu_vq.c drm/virtio: Pass correct device to dma_sync_sgtable_for_device() 2023-03-22 13:33:39 +01:00
virtgpu_vram.c