From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH v2 2/4] dt-bindings: npu: rockchip,rk3588-rknn-core: Add RK3568 support
Date: Thu, 04 Jun 2026 16:18:12 +1000 [thread overview]
Message-ID: <review-patch2-53c4249e-8d6c-4bf7-86ff-b8d02117338a@kernel.org> (raw)
In-Reply-To: <53c4249e-8d6c-4bf7-86ff-b8d02117338a@kernel.org>
Patch Review
**1. Missing `$ref` key — YAML syntax error (critical)**
```yaml
rockchip,pmu:
: /schemas/types.yaml#/definitions/phandle
```
The second line is `: /schemas/types.yaml#/definitions/phandle` with no key. This should be:
```yaml
rockchip,pmu:
$ref: /schemas/types.yaml#/definitions/phandle
```
The `$ref` key appears to have been stripped (possibly by the email toolchain mangling `$`). This will cause `dt_binding_check` to fail. This is a must-fix.
**2. `rockchip,pmu` not conditionally required for RK3568**
The commit message says the phandle is "Required on RK3568" and the driver will fail at probe without it (`syscon_regmap_lookup_by_phandle` returns an error). But the binding doesn't add a conditional `required` block:
```yaml
if:
properties:
compatible:
contains:
const: rockchip,rk3568-rknn-core
then:
required:
- rockchip,pmu
```
Without this, `dtbs_check` won't catch a missing `rockchip,pmu` on RK3568 boards.
**3. The if/then for `sram-supply` looks correct**
Making `sram-supply` conditional on RK3588-only is the right approach.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-06-04 6:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 15:58 [PATCH v2 0/4] accel: rocket: Add RK3568 NPU support MidG971
2026-05-29 15:58 ` [PATCH v2 1/4] accel: rocket: Add support for Rockchip RK3568 MidG971
2026-05-29 18:19 ` Heiko Stuebner
2026-06-04 6:18 ` Claude review: " Claude Code Review Bot
2026-05-29 15:58 ` [PATCH v2 2/4] dt-bindings: npu: rockchip, rk3588-rknn-core: Add RK3568 support MidG971
2026-05-29 16:18 ` [PATCH v2 2/4] dt-bindings: npu: rockchip,rk3588-rknn-core: " Krzysztof Kozlowski
2026-06-04 6:18 ` Claude Code Review Bot [this message]
2026-05-29 15:58 ` [PATCH v2 3/4] arm64: dts: rockchip: rk356x: Add NPU and its IOMMU MidG971
2026-06-04 6:18 ` Claude review: " Claude Code Review Bot
2026-05-29 15:58 ` [PATCH v2 4/4] arm64: dts: rockchip: rk3568-rock-3b: Enable NPU MidG971
2026-06-04 6:18 ` Claude review: " Claude Code Review Bot
2026-05-29 16:17 ` [PATCH v2 0/4] accel: rocket: Add RK3568 NPU support Krzysztof Kozlowski
2026-06-04 6:18 ` Claude review: " Claude Code Review Bot
2026-05-29 18:04 ` Heiko Stuebner
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-53c4249e-8d6c-4bf7-86ff-b8d02117338a@kernel.org \
--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