diff options
| author | Dongwon Kim <dongwon.kim@intel.com> | 2024-10-21 02:08:03 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-02-17 10:04:44 +0100 |
| commit | 18daf9e83c4fbe0ce245ebd91342f8c5a9cff541 (patch) | |
| tree | 3d23569fc6ce5d24397696cb5700b9009aa5a739 /include | |
| parent | 8b60f25c3e672eabd140064bb226795acddee19d (diff) | |
| download | linux-18daf9e83c4fbe0ce245ebd91342f8c5a9cff541.tar.gz linux-18daf9e83c4fbe0ce245ebd91342f8c5a9cff541.tar.bz2 linux-18daf9e83c4fbe0ce245ebd91342f8c5a9cff541.zip | |
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>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions