DRM already have writeback connectors support, which is a way to expose in DRM the hardware functionality from display engines that allows writing back into memory the result of the DE's composition of supported planes. These days, I'm working to add the writeback support into the vkms[1], and I used the kms_writeback to validate my implementation. As a result, I had to rebase the v5 version of Liviu's series, and I also fixed a small issue in the first path (lib/igt_kms: Add writeback support). Patches have been originally implemented by Brian, Liviu has done the v3 and v4 updates to them. I’m just sending a v6. 1. https://patchwork.freedesktop.org/series/61738/ Brian Starkey (6): lib/igt_kms: Add writeback support kms_writeback: Add initial writeback tests lib: Add function to hash a framebuffer kms_writeback: Add writeback-check-output lib/igt_kms: Add igt_output_clone_pipe for cloning kms_writeback: Add tests using a cloned output lib/igt_fb.c | 66 ++++++ lib/igt_fb.h | 3 + lib/igt_kms.c | 157 +++++++++---- lib/igt_kms.h | 10 + tests/Makefile.sources | 1 + tests/kms_writeback.c | 492 +++++++++++++++++++++++++++++++++++++++++ tests/meson.build | 1 + 7 files changed, 692 insertions(+), 38 deletions(-) create mode 100644 tests/kms_writeback.c -- 2.21.0 -- Rodrigo Siqueira https://siqueira.tech
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
