Simon Ser f0bb53c4ab backend/drm: implement KMS state snapshot/restore ... Following ideas from [1], snapshot the entire KMS state when the VT is switched away, and restore it when the VT is switched back. > Well the neat trick is that userspace doesn’t need to be able to > understand properties to save and restore them - the actual property > value transport between kernel and userspace is fully generic. That way, even if another DRM master changes a property we don't understand like CTM or HDR_OUTPUT_METADATA, we can switch it back and avoid getting garbage on screen. [1]: https://blog.ffwll.ch/2016/01/vt-switching-with-atomic-modeset.html		2023-01-04 18:54:23 +01:00
..
atomic.c	backend/drm: implement KMS state snapshot/restore	2023-01-04 18:54:23 +01:00
backend.c	backend/drm: implement KMS state snapshot/restore	2023-01-04 18:54:23 +01:00
cvt.c	backend/drm: add support for custom modes	2019-10-27 10:46:47 -04:00
drm.c	backend/drm: check return value of get_drm_{connector,crtc}_props()	2022-12-16 10:30:14 +01:00
gen_pnpids.sh	backend/drm: use pnp.ids to fetch EDID data	2022-11-09 00:25:18 +03:00
legacy.c	backend/drm: implement KMS state snapshot/restore	2023-01-04 18:54:23 +01:00
meson.build	backend/session: make optional	2022-11-25 16:15:29 +00:00
monitor.c	backend/drm: add wlr_drm_backend_monitor	2021-12-13 14:55:16 +01:00
properties.c	backend/drm: set "max bpc" to the max	2022-06-19 16:55:36 +00:00
renderer.c	backend/drm: store pending FB in state	2022-12-07 17:45:59 +01:00
util.c	backend/drm: implement KMS state snapshot/restore	2023-01-04 18:54:23 +01:00