mirror of
git://git.yoctoproject.org/linux-yocto.git
synced 2025-07-06 13:55:22 +02:00
![]() [ 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> |
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
virtgpu_debugfs.c | ||
virtgpu_display.c | ||
virtgpu_drv.c | ||
virtgpu_drv.h | ||
virtgpu_fence.c | ||
virtgpu_gem.c | ||
virtgpu_ioctl.c | ||
virtgpu_kms.c | ||
virtgpu_object.c | ||
virtgpu_plane.c | ||
virtgpu_prime.c | ||
virtgpu_trace_points.c | ||
virtgpu_trace.h | ||
virtgpu_vq.c | ||
virtgpu_vram.c |