[PATCH i-g-t v6 0/8] test/kms_colorop_helper: don't request colorop updates indefinitely

[Melissa Wen <mwen@igalia.com>]

IGT currently lets colorop property changes be staged on color pipelines that
aren't active, which the uAPI will reject after some kernel fixes [1]:
colorop properties may only change on a currently active pipeline, or on one
activated or deactivated in the same atomic commit. This series fixes the
lib/igt_kms and colorop property tests to respect it.

- Patch 1 clears the colorop changed flag after a commit, so that later
  commits don't re-submit changes on an inactive color pipeline.

- Patch 2 prevents a colorop from being marked as changed just for checking
  whether a property enum value is supported. Together with patch 1, this
  matches the current expectation of allowing property changes on colorops
  that are part of a currently active color pipeline, or of a color pipeline
  that will be activated or deactivated in the same atomic commit, while
  rejecting attempts to change inactive colorops.

- Patch 3 restricts colorop property testing to planes that support the plane
  COLOR_PIPELINE property, i.e. planes that have a colorop pipeline, since not
  all planes have to support it.

- Patch 4 attaches a different framebuffer to non-primary planes so that the
  primary plane stays enabled and, with it, the CRTC under test: AMD requires
  an active primary plane to keep the CRTC active.

- Patch 5 extends igt_plane_set_color_pipeline() to accept NULL as the
  "Bypass" color pipeline and removes set_color_pipeline_bypass(), converting
  all its callers.

- Patch 6 fixes the kms_properties tests to match the colorop update
  requirement of only allowing changes to colorops that are part of an active
  plane color pipeline.

- Patch 7 move kms_color_pipeline to Intel's folder and make sure it only runs
  on Intel devices. As color validation works better with writeback than with
  CRC, other devices should run kms_colorop if they have writeback support.
  Currently, AMD and VKMS support colorop and writeback, and intel is the only
  one that still needs CRC-based test. If a new driver is in the same
  situation as intel, they can move kms_color_pipeline back to generic folder
  and work on adapting it to their specs. 

- Patch 8 adds macros for walking the colorops in a color pipeline, as
  well as all the color pipelines supported by a given plane.

[1] https://lore.kernel.org/dri-devel/20260811171011.184964-1-mwen@igalia.com/

I hope I didn't forget to address all comments in the last version.
Basically I clarified commit message of patch 4 (Harry) and commit plane fb
changes (Chaitanya). I slighty changed commit 6 to balance the changes
in commit 4. Added r-b and a-b. The whole series is now accepted, but
I'll wait a week for any further review before applying it.

Melissa

Melissa Wen (8):
  lib/igt_kms: clear colorop-changed flag after commit
  tests/kms_colorop_helper: only check if a given enum value exists
  tests/kms_properties: don't check colorop if no plane color pipeline prop
  tests/kms_properties: give non-primary planes their own fb
  lib/igt_kms: extend igt_plane_set_color_pipeline to accept Bypass
  tests/kms_properties: check colorop properties on active color pipelines
  tests/intel/kms_color_pipeline: move driver-specific test to intel's folder
  lib/igt_kms: add macros to iterate color pipelines and colorops

 lib/igt_kms.c                                 | 122 +++++++++++-------
 lib/igt_kms.h                                 |  36 +++++-
 .../chamelium/kms_chamelium_color_pipeline.c  |   2 +-
 tests/{ => intel}/kms_color_pipeline.c        |   4 +-
 tests/kms_colorop.c                           |  23 ++--
 tests/kms_colorop_helper.c                    |  49 +++----
 tests/kms_colorop_helper.h                    |   1 -
 tests/kms_properties.c                        |  44 +++++--
 tests/meson.build                             |   2 +-
 9 files changed, 167 insertions(+), 116 deletions(-)
 rename tests/{ => intel}/kms_color_pipeline.c (99%)

-- 
2.53.0