From: Harry Wentland <harry.wentland@amd.com>
To: Alex Hung <alex.hung@amd.com>, igt-dev@lists.freedesktop.org
Subject: Re: [PATCH v3 02/12] lib/igt_kms: Add IGT_COLOROP_FIXED_MATRIX property
Date: Thu, 30 Jul 2026 11:34:01 -0400 [thread overview]
Message-ID: <cd537d9a-4abe-490d-92ab-089b23753cd1@amd.com> (raw)
In-Reply-To: <e4dcc6bd-95ff-468c-9431-cbbcf0436ccc@amd.com>
On 2026-07-25 02:56, Alex Hung wrote:
>
>
> On 6/23/26 11:57, Harry Wentland wrote:
>> Add support for the Fixed Matrix colorop property:
>> - Add IGT_COLOROP_FIXED_MATRIX property to the colorop property enum
>> and names array in igt_kms
>>
>> Assisted-by: Claude:claude-opus-4-6
>> Signed-off-by: Harry Wentland <harry.wentland@amd.com>
>> ---
>> lib/igt_kms.c | 1 +
>> lib/igt_kms.h | 1 +
>> 2 files changed, 2 insertions(+)
>>
>> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
>> index e82d32130666..9003b2b9e670 100644
>> --- a/lib/igt_kms.c
>> +++ b/lib/igt_kms.c
>> @@ -725,6 +725,7 @@ const char * const igt_colorop_prop_names[IGT_NUM_COLOROP_PROPS] = {
>> [IGT_COLOROP_MULTIPLIER] = "MULTIPLIER",
>> [IGT_COLOROP_LUT3D_INTERPOLATION] = "LUT3D_INTERPOLATION",
>> [IGT_COLOROP_NEXT] = "NEXT",
>> + [IGT_COLOROP_FIXED_MATRIX] = "FIXED_MATRIX_TYPE",
> Should we move IGT_COLOROP_FIXED_MATRIX before NEXT?
>> };
>> const char * const igt_crtc_prop_names[IGT_NUM_CRTC_PROPS] = {
>> diff --git a/lib/igt_kms.h b/lib/igt_kms.h
>> index 3df3ba86630e..1be58288e119 100644
>> --- a/lib/igt_kms.h
>> +++ b/lib/igt_kms.h
>> @@ -363,6 +363,7 @@ enum igt_atomic_colorop_properties {
>> IGT_COLOROP_MULTIPLIER,
>> IGT_COLOROP_LUT3D_INTERPOLATION,
>> IGT_COLOROP_NEXT,
>> + IGT_COLOROP_FIXED_MATRIX,
> Should we move IGT_COLOROP_FIXED_MATRIX before NEXT?
I would prefer not to re-order existing enum values and
simply append new ones. I see no good reason why _NEXT
should be the last entry of the enum.
Harry
>> IGT_NUM_COLOROP_PROPS
>> };
>>
>
next prev parent reply other threads:[~2026-07-30 15:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 17:57 [PATCH v3 00/12] YUV Conversion Colorop tests Harry Wentland
2026-06-23 17:57 ` [PATCH v3 01/12] include/drm-uapi: Add DRM_COLOROP_FIXED_MATRIX Harry Wentland
2026-07-25 6:52 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 02/12] lib/igt_kms: Add IGT_COLOROP_FIXED_MATRIX property Harry Wentland
2026-07-25 6:56 ` Alex Hung
2026-07-30 15:34 ` Harry Wentland [this message]
2026-07-30 16:16 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 03/12] tests/kms_colorop_helper: Add Fixed Matrix colorop infrastructure Harry Wentland
2026-07-25 6:56 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 04/12] tests/kms_colorop_helper: Add helpers to get encoding/range from FIXED_MATRIX name Harry Wentland
2026-07-25 7:04 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 05/12] lib/igt_fb: Add YUV color pattern framebuffer support Harry Wentland
2026-07-25 7:05 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 06/12] lib/igt_color_encoding: Add XRGB2101010 format support Harry Wentland
2026-07-25 7:05 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 07/12] lib/igt_color: Add YUV pixel reading support Harry Wentland
2026-07-25 7:10 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 08/12] lib/igt_color: Refactor transform_pixels for input/output FBs and CSC Harry Wentland
2026-07-30 17:09 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 09/12] tests/kms_colorop: Add FIXED_MATRIX colorop tests Harry Wentland
2026-07-25 7:15 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 10/12] tests/kms_colorop: Keep CRTC active between YUV tests with temp FB Harry Wentland
2026-07-25 7:19 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 11/12] tests/kms_colorop: Add bypass transition tests Harry Wentland
2026-07-25 7:25 ` Alex Hung
2026-06-23 17:57 ` [PATCH v3 12/12] tests/kms_colorop: Increase VKMS bracket to 3 up Harry Wentland
2026-07-25 7:24 ` Alex Hung
2026-06-23 18:55 ` ✓ Xe.CI.BAT: success for YUV Conversion Colorop tests (rev2) Patchwork
2026-06-23 19:19 ` ✓ i915.CI.BAT: " Patchwork
2026-06-24 1:27 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-24 5:44 ` ✗ 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=cd537d9a-4abe-490d-92ab-089b23753cd1@amd.com \
--to=harry.wentland@amd.com \
--cc=alex.hung@amd.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