From: Melissa Wen <mwen@igalia.com>
To: Petri Latvala <adrinael@adrinael.net>,
Arkadiusz Hiler <arek@hiler.eu>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
Bhanuprakash Modem <bhanuprakash.modem@gmail.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Karthik B S <karthik.b.s@intel.com>
Cc: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
igt-dev@lists.freedesktop.org, kernel-dev@igalia.com,
Alex Hung <alex.hung@amd.com>,
Swati Sharma <swati2.sharma@intel.com>,
John Harrison <John.Harrison@Igalia.com>,
Rodrigo Siqueira <siqueira@igalia.com>,
Simon Ser <contact@emersion.fr>, Xaver Hugl <xaver.hugl@kde.org>,
Harry Wentland <harry.wentland@amd.com>,
Uma Shankar <uma.shankar@intel.com>
Subject: [PATCH i-g-t v3 0/6] test/kms_colorop_helper: don't request colorop updates indefinitely
Date: Tue, 11 Aug 2026 16:23:00 +0200 [thread overview]
Message-ID: <20260811143558.141813-1-mwen@igalia.com> (raw)
After committing colorop settings, colorops are still flagged as
changed, even if there is no new request for updates. This v3 addresses
Chaitanya's comments [v2] to fix an extra space and split one commit
into three, as follows:
- Patch 1 clears colorop flag after commit so that the next patch
doesn't try to re-submit changes on inactive color pipeline.
- Patch 2 prevents colorop to be marked as changed just because it was
checking if a property enum value is supported. These changes are
consistent with the current expetation of allowing property changes in
colorop that are part of a current active color pipeline or a color
pipeline that will be activated or deactived in the same atomic commit;
but rejecting attempts to change inactive colorops.
- Patch 3 (new): was detached from previous-version patch 3 to only
verify colorop properties in planes that support plane COLOR_PIPELINE
property, i.e. planes that has a colorop pipeline, since not all planes
have to support it.
- Patch 4 (new): was also detached from previous-version patch 3 and now
it basically keeps a primary plane always active for a given CRTC,
even though colorop properties of an overlay plane is under testing.
- Patch 5: is the main change of previous-version patch 3 that fixes
kms_properties to match colorop update requirements of an active plane
color pipeline.
- Patch 6 just ensure that kms_color_pipeline expects an intel device
and will not run otherwise. As color validation works better with
writeback then CRC, other devices should prefer kms_colorop if they have
writeback support. If not, they should work on adapting
kms_color_pipeline according to their specs.
[v1] https://lore.kernel.org/igt-dev/20260602211259.898147-1-mwen@igalia.com/
Lemme know your thought!
Melissa
Melissa Wen (6):
lib/igt_kms: clear colorop-changed flag after commit
test/kms_colorop_helper: only check if a given enum value exist
tests/kms_properties: don't check colorop if no plane color pipeline prop
tests/kms_properties: keep primary plane enabled for each CRTC
tests/kms_properties: check colorop properties on active color pipelines
tests/kms_color_pipeline: skip if not an intel device
lib/igt_kms.c | 41 ++++++++++++++++++++++++++++++++++++++
lib/igt_kms.h | 4 ++++
tests/kms_color_pipeline.c | 1 +
tests/kms_colorop_helper.c | 4 +++-
tests/kms_properties.c | 26 ++++++++++++++++++++++--
5 files changed, 73 insertions(+), 3 deletions(-)
--
2.53.0
next reply other threads:[~2026-08-11 14:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 14:23 Melissa Wen [this message]
2026-08-11 14:23 ` [PATCH i-g-t v3 1/6] lib/igt_kms: clear colorop-changed flag after commit Melissa Wen
2026-08-11 16:37 ` Jani Nikula
2026-08-14 3:39 ` Alex Hung
2026-08-11 14:23 ` [PATCH i-g-t v3 2/6] test/kms_colorop_helper: only check if a given enum value exist Melissa Wen
2026-08-14 3:41 ` Alex Hung
2026-08-11 14:23 ` [PATCH i-g-t v3 3/6] tests/kms_properties: don't check colorop if no plane color pipeline prop Melissa Wen
2026-08-14 3:44 ` Alex Hung
2026-08-11 14:23 ` [PATCH i-g-t v3 4/6] tests/kms_properties: keep primary plane enabled for each CRTC Melissa Wen
2026-08-14 4:05 ` Alex Hung
2026-08-14 6:20 ` Borah, Chaitanya Kumar
2026-08-17 15:16 ` Melissa Wen
2026-08-11 14:23 ` [PATCH i-g-t v3 6/6] tests/kms_color_pipeline: skip if not an intel device Melissa Wen
2026-08-14 3:55 ` Alex Hung
2026-08-17 15:19 ` Melissa Wen
2026-08-17 15:39 ` Harry Wentland
2026-08-17 16:08 ` Harry Wentland
2026-08-18 13:54 ` Melissa Wen
2026-08-18 14:30 ` Harry Wentland
2026-08-18 14:50 ` Melissa Wen
2026-08-19 5:24 ` Borah, Chaitanya Kumar
2026-08-21 11:53 ` Sharma, Swati2
2026-08-11 16:43 ` ✓ Xe.CI.BAT: success for test/kms_colorop_helper: don't request colorop updates indefinitely (rev2) Patchwork
2026-08-11 16:59 ` ✓ i915.CI.BAT: " Patchwork
2026-08-11 18:43 ` ✓ Xe.CI.FULL: " Patchwork
2026-08-11 19:21 ` ✗ i915.CI.Full: failure " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260811143558.141813-1-mwen@igalia.com \
--to=mwen@igalia.com \
--cc=John.Harrison@Igalia.com \
--cc=adrinael@adrinael.net \
--cc=alex.hung@amd.com \
--cc=arek@hiler.eu \
--cc=ashutosh.dixit@intel.com \
--cc=bhanuprakash.modem@gmail.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=contact@emersion.fr \
--cc=harry.wentland@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=karthik.b.s@intel.com \
--cc=kernel-dev@igalia.com \
--cc=siqueira@igalia.com \
--cc=swati2.sharma@intel.com \
--cc=uma.shankar@intel.com \
--cc=xaver.hugl@kde.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.