Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v5 0/2] Enable multi-format testing for pipe color tests
Date: Fri,  5 Jun 2026 12:11:01 +0530	[thread overview]
Message-ID: <20260605064103.855630-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)

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 | 221 ++++++++++++++++++++++++----------------------
 1 file changed, 117 insertions(+), 104 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-06-05  6:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05  6:41 Pranay Samala [this message]
2026-06-05  6:41 ` [PATCH i-g-t v5 1/2] tests/kms_color: Prepare FB creation for explicit YUV color range handling Pranay Samala
2026-06-10  7:46   ` Sharma, Swati2
2026-06-10 12:54     ` Samala, Pranay
2026-06-05  6:41 ` [PATCH i-g-t v5 2/2] tests/kms_color: Add multi-format coverage for pipe color tests Pranay Samala
2026-06-11  5:46   ` Sharma, Swati2
2026-06-11 11:09     ` Jason-JH Lin (林睿祥)
2026-06-05  7:22 ` ✓ Xe.CI.BAT: success for Enable multi-format testing for pipe color tests (rev2) Patchwork
2026-06-05  7:47 ` ✓ i915.CI.BAT: " Patchwork
2026-06-05 17:45 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-05 22:47 ` ✗ i915.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=20260605064103.855630-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