From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm: detect panel type from DisplayID 2.x
Date: Mon, 25 May 2026 22:19:21 +1000 [thread overview]
Message-ID: <review-overall-20260520021432.1301326-1-chen-yu.chen@amd.com> (raw)
In-Reply-To: <20260520021432.1301326-1-chen-yu.chen@amd.com>
Overall Series Review
Subject: drm: detect panel type from DisplayID 2.x
Author: Chenyu Chen <chen-yu.chen@amd.com>
Patches: 6
Reviewed: 2026-05-25T22:19:21.187117
---
This 3-patch series adds panel type detection from the DisplayID v2.x Display Parameters Data Block (tag 0x21), resolving a longstanding TODO in amdgpu_dm. The approach is clean: extract a helper, parse a new block type, wire it into the driver. The code is well-structured and correctly handles the detection priority chain (VSDB > DPCD > DisplayID > Samsung heuristic).
However, there is one significant UAPI concern: **`DRM_MODE_PANEL_TYPE_LCD` is added to the UAPI header (`drm_mode.h`) but `drm_panel_type_enum_list` in `drm_connector.c` is not updated**, so the panel type property can never report "LCD" to userspace. Additionally, at the end of `dm_set_panel_type()`, the existing code only exposes `DRM_MODE_PANEL_TYPE_OLED` via the property — anything else becomes `DRM_MODE_PANEL_TYPE_UNKNOWN`. So even after this series, an LCD panel detected via DisplayID will show as "unknown" to userspace. This needs to be either fixed (update the enum list and the property-setting logic) or acknowledged as intentional for internal-only use — in which case `DRM_MODE_PANEL_TYPE_LCD` should not be in a UAPI header.
There are also minor style issues in Patch 1.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-25 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 2:13 [PATCH v2 0/3] drm: detect panel type from DisplayID 2.x Chenyu Chen
2026-05-20 2:13 ` [PATCH v2 1/3] drm/edid: extract section header processing into helper Chenyu Chen
2026-05-20 13:10 ` Jani Nikula
2026-05-25 12:19 ` Claude review: " Claude Code Review Bot
2026-05-20 2:13 ` [PATCH v2 2/3] drm/edid: parse panel type from DisplayID 2.x Display Parameters Chenyu Chen
2026-05-20 13:30 ` Jani Nikula
2026-05-25 12:19 ` Claude review: " Claude Code Review Bot
2026-05-20 2:13 ` [PATCH v2 3/3] drm/amd/display: use DisplayID panel type in dm_set_panel_type Chenyu Chen
2026-05-25 12:19 ` Claude review: " Claude Code Review Bot
2026-05-25 12:19 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-26 2:59 [PATCH v3 0/3] drm: detect panel type from DisplayID 2.x Chenyu Chen
2026-05-27 5:16 ` Claude review: " Claude Code Review Bot
2026-05-14 6:54 [PATCH 0/2] " Chenyu Chen
2026-05-16 1:17 ` Claude review: " Claude Code Review Bot
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=review-overall-20260520021432.1301326-1-chen-yu.chen@amd.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.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