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 v7 0/2] Enable multi-format testing for pipe color tests
Date: Thu, 2 Jul 2026 13:53:21 +0530 [thread overview]
Message-ID: <20260702082323.3398022-1-pranay.samala@intel.com> (raw)
This series adds multi-format coverage to kms_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 while avoiding redundant
testing on platforms where only a single format is applicable.
v2:
- Add DRM_FORMAT_P010 format
v3:
- Update commit message (Swati)
v4:
- Split the patches (Swati)
v5:
- Consolidate format structure with bpc info (Swati)
- Move format support check out of dynamic subtest scope (Swati)
- Add a common FB helper to centralize framebuffer creation (Swati)
- Keep RGB formats on the existing igt_create_fb() path (Swati)
- Use explicit range/encoding only for YUV formats (Swati)
v6:
- Add FP16 format to the format list
- Combine declaration and assignment for mtk_10bpc_only (Swati)
- Use per-format depth in gamma/degamma tests for 10-bit accuracy (Swati)
- Rename fb creation helper name (Swati)
- Make YCbCr encoding and range explicit helper parameters (Swati)
v7:
- Rebase
Pranay Samala (2):
tests/kms_color: Prepare FB creation for explicit YUV color range
handling
tests/kms_color: Add multi-format coverage for pipe color tests
tests/kms_color.c | 274 +++++++++++++++++++++++++++-------------------
1 file changed, 161 insertions(+), 113 deletions(-)
--
2.34.1
next reply other threads:[~2026-07-02 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 8:23 Pranay Samala [this message]
2026-07-02 8:23 ` [PATCH i-g-t v7 1/2] tests/kms_color: Prepare FB creation for explicit YUV color range handling Pranay Samala
2026-07-02 8:23 ` [PATCH i-g-t v7 2/2] tests/kms_color: Add multi-format coverage for pipe color tests Pranay Samala
2026-07-02 17:39 ` ✓ i915.CI.BAT: success for Enable multi-format testing for pipe color tests (rev4) Patchwork
2026-07-02 17:42 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-03 10:19 ` ✗ Xe.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=20260702082323.3398022-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 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.