This series is a follow-up of what was discussed in [1] and on #wayland IRC channel regarding policy and userspace expectations on changes in colorop properties and the current status of the color pipeline in which the colorop is part of. In short, we agreed that userspace can change properties of colorops that are currently part of an active color pipeline or when the pipeline is switching status in the same commit. However, userspace cannot change colorop properties of inactive color pipeline in the expactation that it will be activated at some point in the future.
Userspace also expects persistence of color pipeline already set, even if it becomes inactive for a while, when activated, colorop settings previouly set should be preserved. In addition, I found some bugs on IGT tests when this policy is applied. So I sent some bug fixes [2]. The rest of the series in [1] was detached in [3] since there is no dependecy between them. [1] https://lore.kernel.org/dri-devel/[email protected]/ [2] https://lore.kernel.org/dri-devel/[email protected]/ [3] https://lore.kernel.org/igt-dev/[email protected]/ Melissa Wen (3): drm/atomic: only add states of active or transient active colorops drm/atomic: duplicate state of all colorops drm/atomic: reject colorop update from inactive color pipeline drivers/gpu/drm/drm_atomic.c | 126 ++++++++++++++++++++++++++-- drivers/gpu/drm/drm_atomic_helper.c | 9 +- 2 files changed, 120 insertions(+), 15 deletions(-) -- 2.53.0
