From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: dt-bindings: display: panel: add YAML schema for LXD M9189A
Date: Wed, 11 Feb 2026 16:26:35 +1000 [thread overview]
Message-ID: <review-patch2-20260210-drm-panel-ek79007ad3-v3-2-cd2974d56937@pengutronix.de> (raw)
In-Reply-To: <20260210-drm-panel-ek79007ad3-v3-2-cd2974d56937@pengutronix.de>
Patch Review
**Subject:** `[PATCH v3 2/3] dt-bindings: display: panel: add YAML schema for LXD M9189A`
**Review of binding file (lxd,m9189a.yaml):**
```yaml
+allOf:
+ - $ref: panel-common.yaml
```
**Positive:**
- Correctly references panel-common.yaml as base, which is the modern approach (changed in v3)
- Properties are properly documented
- Example is complete and compiles
**Issues identified:**
1. **Missing backlight requirement** (line 511-513):
```yaml
+ reset-gpios: true
+ power-supply: true
+ backlight: true
```
The binding declares `backlight: true` but doesn't include it in the `required:` section. However, the driver code at line 343-345 does this:
```c
+ ret = drm_panel_of_backlight(&m9189->panel);
+ if (ret)
+ return dev_err_probe(dev, ret, "Failed to get backlight\n");
```
**Question:** Is backlight optional or required? If `drm_panel_of_backlight()` returns an error when backlight is missing, then it should be in the required list. If it's optional, the binding is correct but the error message might be misleading.
2. **Standby GPIO polarity** (line 538):
```yaml
+ standby-gpios = <&gpio5 22 GPIO_ACTIVE_LOW>;
```
The example shows `GPIO_ACTIVE_LOW`, but there's no documentation explaining what "standby" means for this panel. A description would help:
```yaml
standby-gpios:
description: GPIO used for the standby pin
maxItems: 1
```
Consider adding more detail: "GPIO used to control panel standby mode. Assert to enter standby, de-assert for normal operation."
**Minor:** The example could use more descriptive node names, but this is very minor and matches common practice.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-11 6:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 11:22 [PATCH v3 0/3] drm/panel: add LXD M9189A Michael Tretter
2026-02-10 11:22 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add lxd Michael Tretter
2026-02-11 6:26 ` Claude review: " Claude Code Review Bot
2026-02-10 11:22 ` [PATCH v3 2/3] dt-bindings: display: panel: add YAML schema for LXD M9189A Michael Tretter
2026-02-11 6:26 ` Claude Code Review Bot [this message]
2026-02-11 6:28 ` Krzysztof Kozlowski
2026-02-11 10:06 ` Michael Tretter
2026-02-11 10:12 ` Krzysztof Kozlowski
2026-02-10 11:22 ` [PATCH v3 3/3] drm/panel: add LXD M9189A panel driver Michael Tretter
2026-02-11 6:26 ` Claude review: " Claude Code Review Bot
2026-02-11 6:26 ` Claude review: drm/panel: add LXD M9189A 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-20260210-drm-panel-ek79007ad3-v3-2-cd2974d56937@pengutronix.de \
--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