From: sashiko-bot@kernel.org
To: "Janne Grunau" <j@jannau.net>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 5/5] arm64: dts: apple: Initial t8122 (M3) device trees
Date: Thu, 07 May 2026 20:59:48 +0000 [thread overview]
Message-ID: <20260507205951.9B58EC2BCB2@smtp.kernel.org> (raw)
In-Reply-To: <20260507-apple-m3-initial-devicetrees-v3-5-ca07c81b5dc7@jannau.net>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Critical] The `aic` node uses a new compatible string without a fallback, which will prevent the interrupt controller driver from probing.
- [High] The 'aic' node defines overlapping physical memory regions in its 'reg' property.
--
commit 14b9a4a178ff9110e283f578f130160b0dd626f8
Author: Janne Grunau <j@jannau.net>
arm64: dts: apple: Initial t8122 (M3) device trees
This commit adds initial device trees for all t8122 based devices. The device
trees provide a minimal set of devices, including the CPU cores, interrupt
controller, and basic peripherals.
> diff --git a/arch/arm64/boot/dts/apple/t8122.dtsi b/arch/arm64/boot/dts/apple/t8122.dtsi
> new file mode 100644
> index 0000000000000..c6196225e96ef
> --- /dev/null
> +++ b/arch/arm64/boot/dts/apple/t8122.dtsi
[ ... ]
> + aic: interrupt-controller@2d1000000 {
> + compatible = "apple,t8122-aic3";
Is a fallback compatible string missing here? If the driver does not yet
have a matching declaration for "apple,t8122-aic3", the interrupt controller
could be ignored by of_irq_init() and the kernel may fail to boot.
> + #interrupt-cells = <3>;
> + interrupt-controller;
> + reg = <0x2 0xd1000000 0x0 0x184000>,
> + <0x2 0xd1040000 0x0 0x4>;
Do these physical memory regions overlap? The first region starts at
0xd1000000 and extends for 0x184000 bytes (ending at 0xd1184000), which
fully contains the second region starting at 0xd1040000.
> + reg-names = "core", "event";
> + power-domains = <&ps_aic>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260507-apple-m3-initial-devicetrees-v3-0-ca07c81b5dc7@jannau.net?part=5
prev parent reply other threads:[~2026-05-07 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 7:33 [PATCH v3 0/5] Initial Apple silicon M3 device trees and dt-bindings Janne Grunau
2026-05-07 7:33 ` [PATCH v3 1/5] dt-bindings: power: apple,pmgr-pwrstate: Add t8122 compatible Janne Grunau
2026-05-07 19:23 ` sashiko-bot
2026-05-07 7:33 ` [PATCH v3 2/5] dt-bindings: watchdog: apple,wdt: " Janne Grunau
2026-05-07 20:20 ` sashiko-bot
2026-05-10 15:29 ` Guenter Roeck
2026-05-11 8:50 ` Janne Grunau
2026-05-11 14:07 ` Guenter Roeck
2026-05-11 14:06 ` Guenter Roeck
2026-05-07 7:33 ` [PATCH v3 3/5] dt-bindings: pwm: apple,s5l-fpwm: " Janne Grunau
2026-05-07 7:33 ` [PATCH v3 4/5] dt-bindings: arm: apple: Add M3 based devices Janne Grunau
2026-05-07 7:33 ` [PATCH v3 5/5] arm64: dts: apple: Initial t8122 (M3) device trees Janne Grunau
2026-05-07 20:59 ` 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=20260507205951.9B58EC2BCB2@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=j@jannau.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=sashiko@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