mirror of
https://gitlab.freedesktop.org/emersion/libliftoff.git
synced 2024-12-25 21:59:11 +01:00
Disable plane reset logging
Logigng the list of planes being disabled at the beginning of an apply does not really give useful information. Planes are disabled (and by that become in theory ready for layer-assignment) if they do not have a layer associated at the moment or if they are compatible with the output. That is uninteresting since in this list the subset of planes that are compatible with the output stay constant. And while the subset of planes being reset not compatible with the output might vary from apply to apply it is also of less interest since by definition they are not compatible with what the apply is about.
This commit is contained in:
parent
3cb6cd04b5
commit
780c5b457c
1 changed files with 0 additions and 2 deletions
2
alloc.c
2
alloc.c
|
@ -616,8 +616,6 @@ bool liftoff_output_apply(struct liftoff_output *output, drmModeAtomicReq *req)
|
|||
to hit bandwidth limits because too many planes are enabled. */
|
||||
liftoff_list_for_each(plane, &device->planes, link) {
|
||||
if (plane->layer == NULL) {
|
||||
liftoff_log(LIFTOFF_DEBUG,
|
||||
"Disabling plane %"PRIu32, plane->id);
|
||||
if (!plane_apply(plane, NULL, req, &compatible)) {
|
||||
return false;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue