diff options
| author | Dongwon Kim <dongwon.kim@intel.com> | 2024-10-21 02:08:03 +0300 |
|---|---|---|
| committer | Dmitry Osipenko <dmitry.osipenko@collabora.com> | 2024-11-18 21:18:15 +0300 |
| commit | d3c55b8ab6fe5fa2e7ab02efd36d09c39ee5022f (patch) | |
| tree | e226d78b0f725788d53f8d9f6790f1933441dfac /tools/lib/python | |
| parent | 30f86b8f86ada845fbd0d853b3a3d238567ac2c2 (diff) | |
drm/virtio: New fence for every plane update
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
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions