From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: ARM: dts: ti: omap: espresso-common: Add common device tree for Samsung Galaxy Tab 2 series
Date: Wed, 04 Mar 2026 06:45:50 +1000 [thread overview]
Message-ID: <review-patch5-20260303203017.511-6-bavishimithil@gmail.com> (raw)
In-Reply-To: <20260303203017.511-6-bavishimithil@gmail.com>
Patch Review
This is the largest patch (744 lines) and has several issues:
**Bug - magnetometer interrupts property:**
```
magnetometer@2e {
compatible = "yamaha,yas530";
...
interrupts = <&gpio6 10 IRQ_TYPE_EDGE_RISING>;
};
```
The `interrupts` property takes plain interrupt specifiers, not phandle references. This should be either:
```
interrupt-parent = <&gpio6>;
interrupts = <10 IRQ_TYPE_EDGE_RISING>;
```
or:
```
interrupts-extended = <&gpio6 10 IRQ_TYPE_EDGE_RISING>;
```
**Issue - reserved-memory size hardcoded for 7" variant only:**
```
continuous_splash: framebuffer@bef00000{
reg = <0xbef00000 (1024 * 600 * 4)>;
no-map;
};
```
The size `1024 * 600 * 4` corresponds to the 7" panel (1024x600). The 10" panel is 1280x800, which requires `1280 * 800 * 4` bytes. This is in the **common** dtsi but the size is variant-specific. Either this should be moved to the per-variant dts files, or the size should be large enough for the largest panel, or the 10" variant should override it.
**Style - missing space before brace:**
```
continuous_splash: framebuffer@bef00000{
```
Should be `framebuffer@bef00000 {` (space before `{`).
**Typo in node name:**
```
ledir_pins: pimux-ledir-pins {
```
Should be `pinmux-ledir-pins` (missing `n` in `pinmux`).
**Inconsistent include syntax:**
```
#include "dt-bindings/gpio/gpio.h"
#include <dt-bindings/interrupt-controller/irq.h>
#include <dt-bindings/input/input.h>
```
The first include uses double quotes while the others use angle brackets. Should be consistent — prefer angle brackets (`<...>`) as used elsewhere in the kernel DTS files.
**Inconsistent hex prefix case in OMAP4_IOPAD:**
```
OMAP4_IOPAD(0X0D8, PIN_OUTPUT | PIN_OFF_OUTPUT_LOW | MUX_MODE3)
OMAP4_IOPAD(0X0D6, PIN_OUTPUT | PIN_OFF_OUTPUT_LOW | MUX_MODE1)
OMAP4_IOPAD(0X136, PIN_OUTPUT | MUX_MODE3)
```
These use uppercase `0X` prefix while all other entries use lowercase `0x`. Should be consistent (lowercase).
**Questionable interrupt flags on accelerometer:**
```
accelerometer@18 {
...
interrupts = <25 (IRQ_TYPE_LEVEL_HIGH | IRQ_TYPE_EDGE_RISING)>,
<26 (IRQ_TYPE_LEVEL_HIGH | IRQ_TYPE_EDGE_RISING)>;
};
```
Combining `IRQ_TYPE_LEVEL_HIGH | IRQ_TYPE_EDGE_RISING` (value 5) is unusual. Typically an interrupt is either level-triggered or edge-triggered, not both. Please verify this is correct for the BMA254 accelerometer.
**Unnecessary `#address-cells` in chosen:**
```
chosen {
stdout-path = &uart3;
#address-cells = <1>;
};
```
The `#address-cells` in the `chosen` node is unnecessary if there are no child nodes. Can be dropped.
**Minor - `ti,non-removable` in mmc2:**
```
&mmc2 {
...
ti,non-removable;
bus-width = <8>;
};
```
This is consistent with other OMAP DTS files that use the same property, so it's fine. (Though some newer DTS files use standard `non-removable`.)
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-03 20:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 20:30 [PATCH v9 0/8] Initial support for Samsung Galaxy Tab 2 series Mithil Bavishi
2026-03-03 20:30 ` [PATCH v9 1/8] ARM: dts: twl6032: Add DTS file for TWL6032 PMIC Mithil Bavishi
2026-03-03 20:45 ` Claude review: " Claude Code Review Bot
2026-03-03 20:30 ` [PATCH v9 2/8] dt-bindings: vendor-prefixes: Add Doestek Mithil Bavishi
2026-03-03 20:45 ` Claude review: " Claude Code Review Bot
2026-03-03 20:30 ` [PATCH v9 3/8] dt-bindings: display: bridge: lvds-codec: add doestek, dtc34lm85am Mithil Bavishi
2026-03-03 20:45 ` Claude review: " Claude Code Review Bot
2026-03-03 20:30 ` [PATCH v9 4/8] dt-bindings: display: panel-lvds: Add compatibles for Samsung LTN070NL01 and LTN101AL03 panels Mithil Bavishi
2026-03-03 20:45 ` Claude review: " Claude Code Review Bot
2026-03-03 20:30 ` [PATCH v9 5/8] ARM: dts: ti: omap: espresso-common: Add common device tree for Samsung Galaxy Tab 2 series Mithil Bavishi
2026-03-03 20:45 ` Claude Code Review Bot [this message]
2026-03-03 20:30 ` [PATCH v9 6/8] dt-bindings: omap: Add Samsung Galaxy Tab 2 7.0 and 10.1 Mithil Bavishi
2026-03-03 20:45 ` Claude review: " Claude Code Review Bot
2026-03-03 20:30 ` [PATCH v9 7/8] ARM: dts: ti: omap: samsung-espresso7: Add initial support for Galaxy Tab 2 7.0 Mithil Bavishi
2026-03-03 20:45 ` Claude review: " Claude Code Review Bot
2026-03-03 20:30 ` [PATCH v9 8/8] ARM: dts: ti: omap: samsung-espresso10: Add initial support for Galaxy Tab 2 10.1 Mithil Bavishi
2026-03-03 20:45 ` Claude review: " Claude Code Review Bot
2026-03-03 20:45 ` Claude review: Initial support for Samsung Galaxy Tab 2 series Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-02-23 5:51 [PATCH v7 0/8] " Mithil Bavishi
2026-02-23 5:51 ` [PATCH v7 5/8] ARM: dts: ti: omap: espresso-common: Add common device tree " Mithil Bavishi
2026-02-24 0:31 ` Claude review: " Claude Code Review Bot
2026-02-19 21:03 [PATCH v6 0/8] Initial support " Mithil Bavishi
2026-02-19 21:04 ` [PATCH v6 5/8] ARM: dts: ti: omap: espresso-common: Add common device tree " Mithil Bavishi
2026-02-22 20: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-patch5-20260303203017.511-6-bavishimithil@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