Consider the following scenario:
- mixer hardware block is present including video processor
- userspace uses atomic DRM API
- userspace uses all available planes
The following call sequence (simplified) now happens when
userspace issues an atomic commit.
(1) mixer_atomic_begin()
(2) mixer_update_
Hello everyone,
the recent discussion about this patch has made me realise that the purpose of
the patch, and in particular what it does, and what does not, was too unclear.
Hence I'm resending the patch with a (hopefully) improved and expanded commit
description.
With best wishes,
Tobias
Tob
