From: Pranay Samala <pranay.samala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: karthik.b.s@intel.com, swati2.sharma@intel.com,
sameer.lattannavar@intel.com, pranay.samala@intel.com
Subject: [PATCH i-g-t v2 0/2] Enable multi-format testing for chamelium color tests
Date: Wed, 15 Jul 2026 10:02:24 +0530 [thread overview]
Message-ID: <20260715043226.169521-1-pranay.samala@intel.com> (raw)
This series adds multi-format coverage to kms_chamelium_color
pipe color tests.
To ensure deterministic behavior across YUV formats, the first patch
updates framebuffer creation to explicitly specify YCbCr encoding/range
instead of relying on implicit defaults.
The second patch extends gamma, degamma, and CTM tests to run across
multiple pixel formats at the dynamic subtest level. This adds coverage
for format-dependent color pipeline behavior.
Pranay Samala (2):
tests/chamelium/kms_chamelium_color: Prepare FB creation for explicit
YUV color range handling
tests/chamelium/kms_chamelium_color: Add multi-format coverage for
pipe color tests
tests/chamelium/kms_chamelium_color.c | 240 +++++++++++++++-----------
1 file changed, 139 insertions(+), 101 deletions(-)
--
2.53.0
next reply other threads:[~2026-07-15 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 4:32 Pranay Samala [this message]
2026-07-15 4:32 ` [PATCH i-g-t v2 1/2] tests/chamelium/kms_chamelium_color: Prepare FB creation for explicit YUV color range handling Pranay Samala
2026-07-15 4:32 ` [PATCH i-g-t v2 2/2] tests/chamelium/kms_chamelium_color: Add multi-format coverage for pipe color tests Pranay Samala
2026-07-15 5:58 ` ✓ Xe.CI.BAT: success for Enable multi-format testing for chamelium " Patchwork
2026-07-15 6:23 ` ✓ i915.CI.BAT: " Patchwork
2026-07-15 6:41 ` ✓ i915.CI.Full: " Patchwork
2026-07-15 6:53 ` ✓ Xe.CI.FULL: " 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=20260715043226.169521-1-pranay.samala@intel.com \
--to=pranay.samala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=sameer.lattannavar@intel.com \
--cc=swati2.sharma@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox