From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH v3 3/3] arm64: dts: qcom: sm6125-xiaomi-laurel-sprout: Enable MDSS and add panel
Date: Fri, 13 Mar 2026 14:15:08 +1000 [thread overview]
Message-ID: <review-patch3-vjpnt6xefyssqlaivlvhtizlnlw7gfsmwtexcc7ukccwhgfeet@egtg6oe6za4c> (raw)
In-Reply-To: <vjpnt6xefyssqlaivlvhtizlnlw7gfsmwtexcc7ukccwhgfeet@egtg6oe6za4c>
Patch Review
**Potential bug: VCI regulator voltage mismatch (lines 809-820 of mbox):**
```dts
panel_vci_3p0: regulator-panel-vci {
compatible = "regulator-fixed";
regulator-name = "panel_vci_3p0";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
```
The node and regulator are named `panel_vci_3p0` implying 3.0V, but the voltage is set to 1800000 (1.8V). Either the name is misleading or the voltage is wrong. This should be clarified — if the panel VCI truly runs at 1.8V, the label should be renamed to `panel_vci_1p8` to avoid confusion. If it should actually be 3.0V (3000000 µV), the voltage values need fixing. VCI for AMOLED panels is typically 3.0V–3.3V, so this looks like it might be a real bug.
**Minor: Extra blank line (line 863 of mbox):**
```dts
&mdss_dsi0_out {
data-lanes = <0 1 2 3>;
remote-endpoint = <&panel_in>;
};
&mdss_dsi0_phy {
```
There's an extra blank line between `&mdss_dsi0_out` and `&mdss_dsi0_phy`. Minor style nit.
**Observation: `regulator-boot-on` present on both regulators.** This is fine for panels that need to be powered at boot for a smooth transition from the bootloader's display.
**Observation: No `vin-supply` on `panel_vci_3p0`.** The VDDI regulator has `vin-supply = <&vreg_l9a>` but the VCI regulator has no `vin-supply`. This may be fine if VCI is powered directly from battery or another always-on rail, but it's worth confirming.
**Summary of required fixes:**
1. Fix "Samsubng" typo in MODULE_DESCRIPTION (patch 2)
2. Clean up `samsungp` in the display mode variable name (patch 2)
3. Verify/fix the `panel_vci_3p0` voltage — 1.8V vs 3.0V mismatch (patch 3)
4. Clarify the `MIPI_DSI_MODE_LPM` behavior — it's never set initially but gets added after the first backlight update (patch 2)
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-13 4:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 11:55 [PATCH v3 0/3] Add support for the Samsung S6E8FCO DSI and M1906F9 display panel Yedaya Katsman
2026-03-12 11:55 ` [PATCH v3 1/3] dt-bindings: display: panel: Add Samsung S6E8FCO-M1906F9 Yedaya Katsman
2026-03-13 4:15 ` Claude review: " Claude Code Review Bot
2026-03-12 11:55 ` [PATCH v3 2/3] drm: panel: Add Samsung S6E8FCO DSI controller for M1906F9 panel Yedaya Katsman
2026-03-12 12:09 ` David Heidelberg
2026-03-13 4:15 ` Claude review: " Claude Code Review Bot
2026-03-12 12:10 ` David Heidelberg
2026-03-12 11:55 ` [PATCH v3 3/3] arm64: dts: qcom: sm6125-xiaomi-laurel-sprout: Enable MDSS and add panel Yedaya Katsman
2026-03-12 13:31 ` Dmitry Baryshkov
2026-03-13 4:15 ` Claude Code Review Bot [this message]
2026-03-13 4:15 ` Claude review: Add support for the Samsung S6E8FCO DSI and M1906F9 display panel 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-patch3-vjpnt6xefyssqlaivlvhtizlnlw7gfsmwtexcc7ukccwhgfeet@egtg6oe6za4c \
--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