public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/edid: parse panel type from DisplayID 2.x Display Parameters
Date: Mon, 25 May 2026 22:19:21 +1000	[thread overview]
Message-ID: <review-patch2-20260520021432.1301326-3-chen-yu.chen@amd.com> (raw)
In-Reply-To: <20260520021432.1301326-3-chen-yu.chen@amd.com>

Patch Review

**Purpose:** Adds parsing of the Display Device Technology field from the Display Parameters Data Block (tag 0x21).

**Struct layout:** `displayid_block` base is 3 bytes (tag + rev + num_bytes). The struct `displayid_display_params_block` places `payload[27]` then `device_tech_byte` at offset 30 from the block start (3 + 27 = 30 = 0x1E), which matches the spec reference. The `DISPLAYID_DISPLAY_PARAMS_MIN_LEN` calculation (29 bytes of payload) and the `num_bytes` check are correct.

**Parsing logic:** Using `FIELD_GET(DISPLAYID_DISPLAY_PARAMS_DEVICE_TECH, ...)` to extract bits [6:4] is correct and clean.

**UAPI concern (significant):**

```c
+#define DRM_MODE_PANEL_TYPE_LCD		2
```

This adds a new UAPI constant, but `drm_panel_type_enum_list` in `drivers/gpu/drm/drm_connector.c` currently only contains:

```c
static const struct drm_prop_enum_list drm_panel_type_enum_list[] = {
	{ DRM_MODE_PANEL_TYPE_UNKNOWN, "unknown" },
	{ DRM_MODE_PANEL_TYPE_OLED, "OLED" },
};
```

Without adding `{ DRM_MODE_PANEL_TYPE_LCD, "LCD" }` to this list, the panel type property will never report LCD to userspace. If LCD is meant to be internal-only, it shouldn't be in `include/uapi/drm/drm_mode.h`. If it's meant to be exposed, the enum list needs updating.

**`did_panel_type` field:** Adding a `u8` to `drm_display_info` is fine. The reset in `drm_reset_display_info()` is correct.

**Version gate:** The check `displayid_version(&iter) == DISPLAY_ID_STRUCTURE_VER_20` before parsing the block is correct — tag 0x21 is only valid in DisplayID v2.x.

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-05-25 12:19 UTC|newest]

Thread overview: 11+ 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 Code Review Bot [this message]
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 review: drm: detect panel type from DisplayID 2.x Claude Code Review Bot
  -- strict thread matches above, loose matches on Subject: below --
2026-05-26  2:59 [PATCH v3 0/3] " Chenyu Chen
2026-05-26  2:59 ` [PATCH v3 2/3] drm/edid: parse panel type from DisplayID 2.x Display Parameters Chenyu Chen
2026-05-27  5:16   ` 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-patch2-20260520021432.1301326-3-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