From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: arm64: dts: qcom: sc8280xp: Add dsi nodes on SC8280XP
Date: Tue, 03 Mar 2026 14:16:44 +1000 [thread overview]
Message-ID: <review-patch4-20260228141715.35307-5-mitltlatltl@gmail.com> (raw)
In-Reply-To: <20260228141715.35307-5-mitltlatltl@gmail.com>
Patch Review
**Status: Has bugs that need fixing.**
This is the main DTS patch adding 4 DSI controllers and 4 DSI PHYs across both MDSS instances. Overall structure looks correct, but there are two issues:
#### Bug 1: Missing comma in PHY compatible strings (CRITICAL)
All four PHY nodes are missing a comma between the two compatible strings. This will cause a DTS compilation error.
For `mdss0_dsi0_phy`:
```dts
+ compatible = "qcom,sc8280xp-dsi-phy-5nm"
+ "qcom,sa8775p-dsi-phy-5nm";
```
Should be:
```dts
+ compatible = "qcom,sc8280xp-dsi-phy-5nm",
+ "qcom,sa8775p-dsi-phy-5nm";
```
This same missing comma is present in all four PHY nodes: `mdss0_dsi0_phy`, `mdss0_dsi1_phy`, `mdss1_dsi0_phy`, and `mdss1_dsi1_phy`.
#### Bug 2: Copy-paste error in mdss1_dsi0 assigned-clock-parents
For `mdss1_dsi0`, the byte clock parent references the wrong PHY:
```dts
+ assigned-clock-parents = <&mdss1_dsi1_phy DSI_BYTE_PLL_CLK>,
+ <&mdss1_dsi0_phy DSI_PIXEL_PLL_CLK>;
```
The byte clock parent should reference `&mdss1_dsi0_phy` (not `&mdss1_dsi1_phy`), matching the pattern in `mdss0_dsi0` where both clock parents come from the same PHY:
```dts
assigned-clock-parents = <&mdss0_dsi0_phy DSI_BYTE_PLL_CLK>,
<&mdss0_dsi0_phy DSI_PIXEL_PLL_CLK>;
```
This is likely a copy-paste error from the mdss1_dsi1 block.
#### Minor observations (not blocking)
- The `dsi_opp_table` is defined inside `mdss0_dsi0` and shared by reference from all four DSI controllers. This is correct per v2 review feedback from Konrad.
- The `#include <dt-bindings/clock/qcom,dsi-phy-28nm.h>` header provides the `DSI_BYTE_PLL_CLK` and `DSI_PIXEL_PLL_CLK` defines. Despite the "28nm" in the filename, these constants are generic and used across PHY generations.
- The `refgen-supply` is correctly present on all four DSI controllers, addressing v3 feedback from Dmitry.
- The whitespace-only changes (adding blank lines between `reg` and endpoint labels) in existing port nodes are valid style cleanups.
- The commit message honestly notes that DSI won't fully work yet due to pending dispcc fixes and DSC timing issues. This is good transparency.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-03 4:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 14:17 [PATCH v3 0/4] Add DSI display support for SC8280XP Pengyu Luo
2026-02-28 14:17 ` [PATCH v3 1/4] dt-bindings: display: msm-dsi-phy-7nm: Add SC8280XP Pengyu Luo
2026-03-01 11:42 ` Krzysztof Kozlowski
2026-03-03 4:16 ` Claude review: " Claude Code Review Bot
2026-02-28 14:17 ` [PATCH v3 2/4] dt-bindings: display/msm: dsi-controller-main: " Pengyu Luo
2026-03-01 11:46 ` Krzysztof Kozlowski
2026-03-03 4:16 ` Claude review: " Claude Code Review Bot
2026-02-28 14:17 ` [PATCH v3 3/4] dt-bindings: display: msm: Document DSI controller and DSI PHY on SC8280XP Pengyu Luo
2026-03-01 11:46 ` Krzysztof Kozlowski
2026-03-03 4:16 ` Claude review: " Claude Code Review Bot
2026-02-28 14:17 ` [PATCH v3 4/4] arm64: dts: qcom: sc8280xp: Add dsi nodes " Pengyu Luo
2026-02-28 14:28 ` Dmitry Baryshkov
2026-03-02 11:02 ` Konrad Dybcio
2026-03-03 4:16 ` Claude Code Review Bot [this message]
2026-03-03 4:16 ` Claude review: Add DSI display support for SC8280XP Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-08 6:48 [PATCH v4 0/4] " Pengyu Luo
2026-03-08 6:48 ` [PATCH v4 4/4] arm64: dts: qcom: sc8280xp: Add dsi nodes on SC8280XP Pengyu Luo
2026-03-08 21:56 ` Claude review: " Claude Code Review Bot
2026-02-28 10:19 [PATCH v2 0/4] Add DSI display support for SC8280XP Pengyu Luo
2026-02-28 10:19 ` [PATCH v2 4/4] arm64: dts: qcom: sc8280xp: Add dsi nodes on SC8280XP Pengyu Luo
2026-03-03 4:28 ` 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-patch4-20260228141715.35307-5-mitltlatltl@gmail.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