public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Swati Sharma <swati2.sharma@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: chaitanya.kumar.borah@intel.com, Swati Sharma <swati2.sharma@intel.com>
Subject: [RFC PATCH i-g-t 0/5] Add CSC Fixed-Function (CSC_FF) colorop tests
Date: Mon, 30 Mar 2026 17:20:52 +0530	[thread overview]
Message-ID: <20260330115057.963395-1-swati2.sharma@intel.com> (raw)

This series adds IGT test support for the DRM_COLOROP_CSC_FF colorop
type, which represents a fixed-function Color Space Conversion block
in Intel display hardware. Unlike programmable CSC matrices, CSC_FF
selects from predefined hardware modes via the CSC_FF_TYPE enum
property.

The series is structured as follows:

Patch 1: Syncs the DRM UAPI header to add the DRM_COLOROP_CSC_FF
          enum definition.
Patch 2: Registers the CSC_FF_TYPE property in the IGT KMS library
          so IGT can discover and set the enum property on CSC_FF
          colorops.
Patch 3: Extends the kms_colorop_helper with CSC_FF type handling,
          including can_use_colorop(), set_colorop(), and
          reset_colorop() support, plus the enum name table for:
            - YUV601 to RGB601
            - YUV709 to RGB709
            - YUV2020 to RGB2020
            - RGB709 to RGB2020
Patch 4: Adds the actual plane color pipeline subtests for CSC_FF
          covering standalone CSC_FF, CSC_FF + 1D LUT, and
          1D LUT + CSC_FF + 1D LUT pipelines. For YUV input
          tests, a YUYV framebuffer is created with the appropriate
          color encoding and range. Also refactors ctm_colorop_only()
          into a generic colorop_type_only() helper.
Patch 5: Removes unused color_depth and drm_format assignments from
          run_tests_for_plane() that were left over from earlier
          refactoring.

This depends on the corresponding kernel series that introduces
CSC_FF colorop support for Intel display hardware:
https://patchwork.freedesktop.org/series/162786/

Note: During local validation, CRC mismatches were observed on a few
tests. This is still under investigation and is the reason for the
RFC tag.

Swati Sharma (5):
  include/drm-uapi: Add DRM_COLOROP_CSC_FF definition
  lib/igt_kms: Add CSC_FF_TYPE colorop property
  tests/kms_colorop_helper: Add CSC_FF colorop support
  tests/kms_color_pipeline: Add CSC_FF colorop tests
  tests/kms_color_pipeline: Remove unused color_depth and drm_format

 include/drm-uapi/drm_mode.h |  12 ++
 lib/igt_kms.c               |   1 +
 lib/igt_kms.h               |   1 +
 tests/kms_color_pipeline.c  | 292 +++++++++++++++++++++++++++++++++++-
 tests/kms_colorop_helper.c  |  19 +++
 tests/kms_colorop_helper.h  |  19 ++-
 6 files changed, 337 insertions(+), 7 deletions(-)

-- 
2.25.1


             reply	other threads:[~2026-03-30 11:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 11:50 Swati Sharma [this message]
2026-03-30 11:50 ` [RFC PATCH i-g-t 1/5] include/drm-uapi: Add DRM_COLOROP_CSC_FF definition Swati Sharma
2026-03-30 11:50 ` [RFC PATCH i-g-t 2/5] lib/igt_kms: Add CSC_FF_TYPE colorop property Swati Sharma
2026-03-30 11:50 ` [RFC PATCH i-g-t 3/5] tests/kms_colorop_helper: Add CSC_FF colorop support Swati Sharma
2026-03-30 11:50 ` [RFC PATCH i-g-t 4/5] tests/kms_color_pipeline: Add CSC_FF colorop tests Swati Sharma
2026-03-30 11:50 ` [RFC PATCH i-g-t 5/5] tests/kms_color_pipeline: Remove unused color_depth and drm_format Swati Sharma
2026-03-31  2:55 ` ✓ i915.CI.BAT: success for Add CSC Fixed-Function (CSC_FF) colorop tests Patchwork
2026-03-31  2:56 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-31  7:45 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-31 11:35 ` ✗ 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=20260330115057.963395-1-swati2.sharma@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=igt-dev@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox