From: sashiko-bot@kernel.org
To: "Michał Grzelak" <michal.grzelak@linux.intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v4 2/5] drm/i915/3dlut: disable 3D LUT for pre-GLK
Date: Tue, 13 Oct 2026 20:59:16 +0000 [thread overview]
Message-ID: <sashiko-outbox-170497@kernel.org> (raw)
In-Reply-To: <20261013204705.1574475-3-michal.grzelak@linux.intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] drm/i915: 3D LUT remains disabled for GLK/ICL due to unmodified version check
--
commit 31c6b1070ace7be34ebe695316e80a7d65a5d1a7
Author: Michał Grzelak <michal.grzelak@linux.intel.com>
Subject: drm/i915/3dlut: disable 3D LUT for pre-GLK
This commit adds a has_3dlut field to the display runtime info to indicate
whether 3D LUT is enabled. It initializes the field to 1 for GLK and newer
platforms, and adds a HAS_3DLUT macro to check for support.
> diff --git a/drivers/gpu/drm/i915/display/intel_color.c b/drivers/gpu/drm/i915/display/intel_color.c
> index f1df0f9ba7624..95de75e1de984 100644
> --- a/drivers/gpu/drm/i915/display/intel_color.c
> +++ b/drivers/gpu/drm/i915/display/intel_color.c
> @@ -4304,6 +4304,9 @@ intel_color_load_plane_luts(struct intel_dsb *dsb,
> bool
> intel_color_crtc_has_3dlut(struct intel_display *display, enum pipe pipe)
> {
> + if (!HAS_3DLUT(display))
> + return false;
> +
> if (DISPLAY_VER(display) >= 12)
> return pipe == PIPE_A || pipe == PIPE_B;
> else
> return false;
> }
[Severity: Medium]
Will this still return false for GLK and ICL platforms even though they have
the HAS_3DLUT flag set?
The commit message indicates 3D LUT is supported on GLK+ hardware, and the
patch sets has_3dlut = 1 for GLK (DISPLAY_VER = 10) and ICL (DISPLAY_VER = 11).
However, in intel_color_crtc_has_3dlut(), after the new HAS_3DLUT() check
passes for these platforms, the function still evaluates:
if (DISPLAY_VER(display) >= 12)
...
else
return false;
Doesn't this existing version check unconditionally return false for GLK and
ICL, defeating the newly added flag and keeping 3D LUT disabled for these
platforms?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261013204705.1574475-1-michal.grzelak@linux.intel.com?part=2
next prev parent reply other threads:[~2026-10-13 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 20:46 [PATCH v4 0/5] SKL_DSSM / DE_CAP cleanup Michał Grzelak
2026-10-13 20:47 ` [PATCH v4 1/5] drm/i915/display: clean SKL_DSSM register macros Michał Grzelak
2026-10-13 20:47 ` [PATCH v4 2/5] drm/i915/3dlut: disable 3D LUT for pre-GLK Michał Grzelak
2026-10-13 20:59 ` sashiko-bot [this message]
2026-10-13 20:47 ` [PATCH v4 3/5] drm/i915/3dlut: log 3D LUT's status Michał Grzelak
2026-10-13 20:47 ` [PATCH v4 4/5] drm/i915/3dlut: disable 3D LUT if unsupported Michał Grzelak
2026-10-13 20:47 ` [PATCH v4 5/5] drm/i915/display: log eDP TC support and DBuf overlap detection state Michał Grzelak
2026-10-13 20:53 ` sashiko-bot
2026-10-13 21:24 ` ✗ CI.checkpatch: warning for SKL_DSSM / DE_CAP cleanup Patchwork
2026-10-13 21:26 ` ✓ CI.KUnit: success " Patchwork
2026-10-13 22:29 ` ✓ i915.CI.BAT: " Patchwork
2026-10-14 2:57 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-14 5:34 ` ✗ 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=sashiko-outbox-170497@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.grzelak@linux.intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.