You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Michael Olbrich f5a4fb5abc backend-drm: make sure all buffers are released when an output is removed ... When an output is destroyed then the output state is freed immediately. In this case, the plane state is only partially destroyed because it is the currently active state. This includes the buffer reference. Without the output, the plane will not be updated any more until it is used by a different output (if possible) or the output returns and the plane is used again. As a result, the buffer reference is kept for a long time. This will cause some applications to stall because weston now keeps two buffers (the one here and another one for a different output where the application is now displayed). To avoid this, do a synchronous commit that disables the output. The output needs to be disabled anyways and this way the current state contains no buffers that would remain. `device->state_invalid = true` in drm_output_detach_crtc() is no longer needed, because drm_output_detach_crtc() is called only when initialization failed and the crtc was not yet used or in drm_output_deinit() when the crtc was already disabled with the new synchronous commit. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>		3 years ago
..
drm-gbm.c	…
drm-internal.h	…
drm-virtual.c	…
drm.c	backend-drm: make sure all buffers are released when an output is removed	3 years ago
fb.c	…
kms-color.c	…
kms.c	backend-drm: check that outputs are in fact ours	3 years ago
libbacklight.c	…
libbacklight.h	…
meson.build	…
modes.c	…
state-helpers.c	…
state-propose.c	build: fix possible race/error for some backends	3 years ago
vaapi-recorder.c	…
vaapi-recorder.h	…