Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yureka Lilian" <yureka@cyberchaos.dev>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 10/10] arm64: dts: apple: Add minimal t8132 (M4) device trees
Date: Sun, 05 Jul 2026 13:28:08 +0000	[thread overview]
Message-ID: <20260705132808.82D2B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260705-apple-m4-initial-devicetrees-v1-10-e5655ee56523@cyberchaos.dev>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Medium] The `aic` node has a mismatched unit address and overlapping memory regions in its `reg` property.
- [Low] The `model` property for the MacBook Air (13-inch) erroneously declares the year as 2024 instead of 2025.
- [Low] `t8132` device trees are incorrectly placed at the very top of the `Makefile`, breaking the chronological sorting order.
--

commit 281d92c4ca5eb8a2224c6bb0b9116c7518b422d1
Author: Yureka Lilian <yureka@cyberchaos.dev>

arm64: dts: apple: Add minimal t8132 (M4) device trees

This commit adds minimal device trees for a series of new Apple M4 devices,
including MacBook Pros, MacBook Airs, iMacs, and the Mac mini. The device
trees are limited to essential components like CPU cores, interrupts, and
serial, allowing a basic boot. It also notes that SMP support currently
remains unreliable.

> diff --git a/arch/arm64/boot/dts/apple/Makefile b/arch/arm64/boot/dts/apple/Makefile
> index 6fc3349a58428..181bd0e289653 100644
> --- a/arch/arm64/boot/dts/apple/Makefile
> +++ b/arch/arm64/boot/dts/apple/Makefile
> @@ -1,4 +1,10 @@
>  # SPDX-License-Identifier: GPL-2.0
> +dtb-$(CONFIG_ARCH_APPLE) += t8132-j604.dtb
> +dtb-$(CONFIG_ARCH_APPLE) += t8132-j623.dtb
> +dtb-$(CONFIG_ARCH_APPLE) += t8132-j624.dtb
> +dtb-$(CONFIG_ARCH_APPLE) += t8132-j713.dtb
> +dtb-$(CONFIG_ARCH_APPLE) += t8132-j715.dtb
> +dtb-$(CONFIG_ARCH_APPLE) += t8132-j773g.dtb
>  dtb-$(CONFIG_ARCH_APPLE) += s5l8960x-j71.dtb

[Severity: Low]
This isn't a bug, but should these new t8132 device trees be appended
to the bottom of the list rather than prepended at the top, to maintain
chronological sorting order in the Makefile?

[ ... ]

> diff --git a/arch/arm64/boot/dts/apple/t8132-j713.dts b/arch/arm64/boot/dts/apple/t8132-j713.dts
> index 0000000000000..b1f779c37d5fe
> --- /dev/null
> +++ b/arch/arm64/boot/dts/apple/t8132-j713.dts
[ ... ]
> +/ {
> +	compatible = "apple,j713", "apple,t8132", "apple,arm-platform";
> +	model = "Apple MacBook Air (13-inch, M4, 2024)";

[Severity: Low]
This isn't a bug, but does the model string contain a typo? The header
comment for this file identifies the target as a 2025 model, but the model
string exposes 2024 to userspace.

[ ... ]

> diff --git a/arch/arm64/boot/dts/apple/t8132.dtsi b/arch/arm64/boot/dts/apple/t8132.dtsi
> index 0000000000000..715980b5c7de4
> --- /dev/null
> +++ b/arch/arm64/boot/dts/apple/t8132.dtsi
[ ... ]
> +		aic: interrupt-controller@381180000 {
> +			compatible = "apple,t8132-aic3", "apple,t8122-aic3";
> +			#interrupt-cells = <3>;
> +			interrupt-controller;
> +			reg = <0x00000003 0x81000000 0x00000000 0x1cc000>,
> +			      <0x00000003 0x81040000 0x00000000 0x4000>;

[Severity: Medium]
Is the base address and memory region mapping for aic intentional?

The node defines a unit address of @381180000, but the reg property specifies
a base of 0x81000000 (translating to 0x381000000). Also, the first memory
region of size 0x1cc000 completely overlaps the second region starting at
0x81040000. 

Could this typo in the physical address map explain the unreliable smp boot
behavior mentioned in the commit message?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260705-apple-m4-initial-devicetrees-v1-0-e5655ee56523@cyberchaos.dev?part=10

  reply	other threads:[~2026-07-05 13:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 13:17 [PATCH 00/10] Initial Apple silicon M4 device trees and dt-bindings Yureka Lilian
2026-07-05 13:17 ` [PATCH 01/10] dt-bindings: arm: cpus: Add Apple M4 CPU core compatibles Yureka Lilian
2026-07-05 13:17 ` [PATCH 02/10] dt-bindings: interrupt-controller: apple,aic2: Add apple,t8132 compatible Yureka Lilian
2026-07-05 13:24   ` sashiko-bot
2026-07-05 13:36     ` Yureka Lilian
2026-07-05 13:17 ` [PATCH 03/10] dt-bindings: watchdog: apple,wdt: Add t8132 compatible Yureka Lilian
2026-07-05 13:17 ` [PATCH 04/10] dt-bindings: arm: apple: apple,pmgr: " Yureka Lilian
2026-07-05 13:27   ` sashiko-bot
2026-07-05 13:17 ` [PATCH 05/10] dt-bindings: power: apple,pmgr-pwrstate: " Yureka Lilian
2026-07-05 13:25   ` sashiko-bot
2026-07-05 13:17 ` [PATCH 06/10] dt-bindings: pinctrl: apple,pinctrl: " Yureka Lilian
2026-07-05 13:17 ` [PATCH 07/10] dt-bindings: i2c: apple,i2c: " Yureka Lilian
2026-07-05 13:25   ` sashiko-bot
2026-07-05 13:17 ` [PATCH 08/10] dt-bindings: pwm: apple,s5l-fpwm: " Yureka Lilian
2026-07-05 13:17 ` [PATCH 09/10] dt-bindings: arm: apple: Add M4 based devices Yureka Lilian
2026-07-05 13:28   ` sashiko-bot
2026-07-05 13:37     ` Yureka Lilian
2026-07-05 13:17 ` [PATCH 10/10] arm64: dts: apple: Add minimal t8132 (M4) device trees Yureka Lilian
2026-07-05 13:28   ` sashiko-bot [this message]
2026-07-05 13:44     ` Yureka Lilian

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=20260705132808.82D2B1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=yureka@cyberchaos.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