From: sashiko-bot@kernel.org
To: "Janne Grunau" <j@jannau.net>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 10/10] arm64: dts: apple: Initial T6030 (M3 Pro) device trees
Date: Wed, 15 Jul 2026 09:27:52 +0000 [thread overview]
Message-ID: <20260715092752.989531F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715-apple-t603x-initial-devices-v2-10-df65b2485710@jannau.net>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `pinctrl_nub` device is missing its `power-domains` property, which is explicitly defined as `ps_nub_gpio` in `t6030-pmgr.dtsi`.
--
--- Patch [10]: [PATCH v2 10/10] arm64: dts: apple: Initial T6030 (M3 Pro) device trees ---
commit 2e87765dac6c4901eb4d023fc0b86ec40441a4ad
Author: Janne Grunau <j@jannau.net>
arm64: dts: apple: Initial T6030 (M3 Pro) device trees
This commit introduces minimal device trees for the M3 Pro SoC, supporting the
14-inch and 16-inch MacBook Pro models from November 2023. It includes base
device nodes in t6030.dtsi and device-specific overlays.
> diff --git a/arch/arm64/boot/dts/apple/t6030.dtsi b/arch/arm64/boot/dts/apple/t6030.dtsi
> new file mode 100644
> --- /dev/null
> +++ b/arch/arm64/boot/dts/apple/t6030.dtsi
[ ... ]
> + pinctrl_nub: pinctrl@3641f0000 {
> + compatible = "apple,t6030-pinctrl", "apple,t8103-pinctrl";
> + reg = <0x3 0x641f0000 0x0 0x4000>;
> +
> + interrupt-parent = <&aic>;
[Severity: Medium]
Is pinctrl_nub missing its power-domains property?
The ps_nub_gpio power domain is defined in t6030-pmgr.dtsi, but it doesn't
appear to be referenced here. Does this node need power-domains =
<&ps_nub_gpio>; added so the genpd dependency graph is complete?
> + interrupts = <AIC_IRQ 472 IRQ_TYPE_LEVEL_HIGH>,
> + <AIC_IRQ 473 IRQ_TYPE_LEVEL_HIGH>,
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260715-apple-t603x-initial-devices-v2-0-df65b2485710@jannau.net?part=10
prev parent reply other threads:[~2026-07-15 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 9:11 [PATCH v2 00/10] Initial Apple M3 Pro, Max and Ultra device trees Janne Grunau
2026-07-15 9:11 ` [PATCH v2 01/10] dt-bindings: arm: apple: Add M3 Pro/Max/Ultra devices (T603x) Janne Grunau
2026-07-15 9:11 ` [PATCH v2 02/10] dt-bindings: interrupt-controller: apple,aic2: Invert #interrupt-cells condition Janne Grunau
2026-07-15 9:24 ` sashiko-bot
2026-07-15 9:11 ` [PATCH v2 03/10] dt-bindings: interrupt-controller: apple,aic2: Add apple,t6031-aic3 compatible Janne Grunau
2026-07-15 9:11 ` [PATCH v2 04/10] dt-bindings: arm: apple: apple,pmgr: Add t6030 and t6031 compatibles Janne Grunau
2026-07-15 9:19 ` sashiko-bot
2026-07-15 9:11 ` [PATCH v2 05/10] dt-bindings: power: apple,pmgr-pwrstate: " Janne Grunau
2026-07-15 9:17 ` sashiko-bot
2026-07-15 9:11 ` [PATCH v2 06/10] dt-bindings: watchdog: apple,wdt: " Janne Grunau
2026-07-15 9:11 ` [PATCH v2 07/10] dt-bindings: i2c: apple,i2c: " Janne Grunau
2026-07-15 9:11 ` [PATCH v2 08/10] dt-bindings: pwm: apple,s5l-fpwm: " Janne Grunau
2026-07-15 9:11 ` [PATCH v2 09/10] arm64: dts: apple: Initial T603[124] (M3 Max and Ultra) device trees Janne Grunau
2026-07-15 9:11 ` [PATCH v2 10/10] arm64: dts: apple: Initial T6030 (M3 Pro) " Janne Grunau
2026-07-15 9:27 ` sashiko-bot [this message]
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=20260715092752.989531F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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