From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: arm64: dts: qcom: add support for pixel 3a xl with the tianma panel
Date: Wed, 11 Feb 2026 16:47:58 +1000 [thread overview]
Message-ID: <review-patch6-20260210023300.15785-7-mailingradian@gmail.com> (raw)
In-Reply-To: <20260210023300.15785-7-mailingradian@gmail.com>
Patch Review
**Copyright Year:**
```c
+ * Copyright (c) 2023-2024, Richard Acayan. All rights reserved.
```
Submitted in 2026, should be 2023-2026 or just 2026.
**Misleading Comment:**
```c
+ * Device tree for Google Pixel 3a XL with the panel connected to the Samsung
+ * Display Controller.
```
The panel is **Tianma/Novatek**, not Samsung. The DSI controller is Qualcomm (part of SDM670). Suggested fix:
```c
/*
* Device tree for Google Pixel 3a XL with Tianma NT37700F panel.
*/
```
**Panel Compatible (from Patch 3 issue):**
```c
+&panel {
+ compatible = "novatek,nt37700f";
```
Should be `"tianma,nt37700f"` as discussed in Patch 3.
**Physical Dimensions:**
```c
+&rmi4_f12 {
+ touchscreen-x-mm = <69>;
+ touchscreen-y-mm = <137>;
+};
```
Bonito XL: 69×137mm vs Sargo: 63×127mm (after patch 5). Physically larger screen on XL - correct.
**Display Resolution:**
```c
+ width = <1080>;
+ height = <2160>;
```
Bonito: 1080×2160 vs Sargo: 1080×2220. The XL actually has fewer vertical pixels despite larger screen. Verified against real specs - this is correct (Pixel 3a XL is 6.0" 18:9, Pixel 3a is 5.6" 18.5:9).
**Konrad Dybcio's Question:**
> should we anticipate a non-Tianma-panel one too (i.e. are you sure those are out in the wild)?
The cover letter mentions "two variants with panels from Samsung or from Tianma/Novatek", so `-tianma` suffix is appropriate. However, commit message should clarify this.
**Rating:** NEEDS REVISION - Fix copyright year, fix misleading Samsung comment, fix panel compatible
---
## SUMMARY OF REQUIRED CHANGES
### Must Fix (Critical):
1. **Patch 1:** Correct commit message (bonito-sdc → bonito-tianma), document base bonito compatible
2. **Patch 2:** Create dedicated novatek,nt37700f.yaml binding, remove from panel-simple-dsi.yaml
3. **Patch 3:** Remove TODO, change compatible to "tianma,nt37700f", fix module description
4. **Patch 5:** Justify GPL-2.0-only license change or revert, explain touchscreen dimension change
### Should Fix (Major):
1. **Patch 5:** Use C-style comments in DT files
2. **Patch 6:** Fix copyright year, fix misleading Samsung comment
3. **All:** Update copyright years to match submission date
4. **Series:** Document dependency on IMX355 patches in cover letter
### Nice to Fix (Minor):
1. Add comments explaining vendor-specific register sequences in panel driver
2. Add comment explaining display timing porch values source
3. Consider thread-safety documentation for backlight mode_flags manipulation
**OVERALL RECOMMENDATION:** The series demonstrates good technical understanding and clean code structure, but contains too many critical issues to merge as-is. Please address critical and major issues and submit v2. The core approach of refactoring into common .dtsi is sound.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-11 6:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 2:32 [PATCH 0/6] Support for the Pixel 3a XL with the Tianma panel Richard Acayan
2026-02-10 2:32 ` [PATCH 1/6] dt-bindings: arm: qcom: document google, bonito-tianma board Richard Acayan
2026-02-10 9:12 ` Krzysztof Kozlowski
2026-02-11 6:47 ` Claude review: " Claude Code Review Bot
2026-02-10 2:32 ` [PATCH 2/6] dt-bindings: panel-simple-dsi: add nt37700f compatible Richard Acayan
2026-02-10 9:12 ` Krzysztof Kozlowski
2026-02-11 6:47 ` Claude review: " Claude Code Review Bot
2026-02-10 2:32 ` [PATCH 3/6] drm/panel: Add Novatek/Tianma NT37700F panel Richard Acayan
2026-02-11 6:47 ` Claude review: " Claude Code Review Bot
2026-02-10 2:32 ` [PATCH 4/6] arm64: dts: qcom: sdm670-google-sargo: add touchscreen and display labels Richard Acayan
2026-02-11 6:47 ` Claude review: " Claude Code Review Bot
2026-02-10 2:32 ` [PATCH 5/6] arm64: dts: qcom: sdm670-google: add common device tree include Richard Acayan
2026-02-11 6:47 ` Claude review: " Claude Code Review Bot
2026-02-12 10:30 ` [PATCH 5/6] " Konrad Dybcio
2026-02-10 2:33 ` [PATCH 6/6] arm64: dts: qcom: add support for pixel 3a xl with the tianma panel Richard Acayan
2026-02-10 9:10 ` Konrad Dybcio
2026-02-11 19:33 ` Richard Acayan
2026-02-12 10:29 ` Konrad Dybcio
2026-02-11 6:47 ` Claude Code Review Bot [this message]
2026-02-11 6:47 ` Claude review: Support for the Pixel 3a XL with the Tianma 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-patch6-20260210023300.15785-7-mailingradian@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