From: Jay Liu <jay.liu@mediatek.com>
To: <igt-dev@lists.freedesktop.org>
Cc: Jason-JH Lin <jason-jh.lin@mediatek.com>,
Paul-PL Chen <paul-pl.chen@mediatek.com>,
Nancy Lin <nancy.lin@mediatek.com>,
Singo Chang <singo.chang@mediatek.com>,
Gil Dekel <gildekel@google.com>, Yacoub <markyacoub@chromium.org>,
Sharma Swati2 <swati2.sharma@intel.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Jay Liu <jay.liu@mediatek.com>
Subject: [PATCH i-g-t v5 0/1] tests/kms_color: Add 10-bit color depth support to gamma test for MediaTek
Date: Sat, 6 Jun 2026 17:05:35 +0800 [thread overview]
Message-ID: <20260606090557.8879-1-jay.liu@mediatek.com> (raw)
Hi,
This patch introduces support for 10-bit color depth in the kms_color test suite to accommodate MediaTek devices that require a 10-bit pipeline to achieve bit-true results during color verification.
Change in v5:
- Fix typo in comment: s/Medaitek/MediaTek
- Fix comment formatting: s/0xFFFD0/0xffd0 and add space before "which"
- Simplify depth_10bit initialization: bool depth_10bit = is_mtk_device(data->drm_fd)
- Remove redundant if statement that set depth_10bit
- Improve commit message to explain "why" MediaTek requires these changes:
* Why 10-bit color depth is needed (bit-accurate validation without precision loss)
* Why LUT maximum is set to 0xffd0 instead of 0xffff (hardware mapping behavior)
Change in v4:
- Refactor lut_value assignment: declare lut_value variable at the beginning of the function and assign it outside the loop to improve code efficiency.
- Rename is_mtk to depth_10bit: use a more descriptive variable name that reflects the actual purpose (10-bit color depth requirement) rather than device vendor.
Change in v3:
- Fix build error in kms_color.c:the previous patch mistakenly changed primary->crtc to primary->pipe, which caused compilation to fail.
Change in v2:
- Replace the depth_10bit variable with is_mtk to simplify the logic.
- Include a code comment to clarify the justification for using 0xFFD0 as the maximum threshold for the Gamma LUT.
Jay Liu (1):
tests/kms_color: Add 10-bit color depth support to gamma test for
MediaTek
tests/kms_color.c | 29 +++++++++++++++++++++++------
1 file changed, 23 insertions(+), 6 deletions(-)
--
2.45.2
next reply other threads:[~2026-06-06 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 9:05 Jay Liu [this message]
2026-06-06 9:05 ` [PATCH v5 1/1] tests/kms_color: Add 10-bit color depth support to gamma test for MediaTek Jay Liu
2026-06-06 9:50 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-06-06 10:25 ` ✓ i915.CI.BAT: " Patchwork
2026-06-06 16:23 ` ✗ i915.CI.Full: failure " Patchwork
2026-06-06 17:09 ` ✓ Xe.CI.FULL: success " 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=20260606090557.8879-1-jay.liu@mediatek.com \
--to=jay.liu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=gildekel@google.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jason-jh.lin@mediatek.com \
--cc=markyacoub@chromium.org \
--cc=nancy.lin@mediatek.com \
--cc=paul-pl.chen@mediatek.com \
--cc=singo.chang@mediatek.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