From: sashiko-bot@kernel.org
To: "Yureka Lilian" <yureka@cyberchaos.dev>
Cc: conor+dt@kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 09/10] dt-bindings: arm: apple: Add M4 based devices
Date: Sun, 05 Jul 2026 13:28:19 +0000 [thread overview]
Message-ID: <20260705132819.9CA9C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260705-apple-m4-initial-devicetrees-v1-9-e5655ee56523@cyberchaos.dev>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The top-level text description block in the binding was not updated to list the new M4 devices.
- [Low] The inline comments for the newly added M4 MacBook Air models incorrectly label them as 'M3'.
--
commit 2d1ae3586bee901cafa8ffc62c9df52d3acdcf89
Author: Yureka Lilian <yureka@cyberchaos.dev>
dt-bindings: arm: apple: Add M4 based devices
This commit adds compatible strings for Apple M4-based devices. It introduces
the apple,t8132 SoC and associated platforms like the new MacBook Pro, iMac,
MacBook Air, and Mac mini.
Looking at the top-level description block in this file:
Documentation/devicetree/bindings/arm/apple.yaml:
Devices based on the "M3" SoC:
- MacBook Air (13-inch, M3, 2024)
- MacBook Air (15-inch, M3, 2024)
- MacBook Pro (14-inch, M3, 2023)
- iMac (24-inch, M3, 2023)
Devices based on the "M1 Pro", "M1 Max" and "M1 Ultra" SoCs:
[Severity: Low]
Should the new M4 devices be added to this top-level description block to
keep the documentation in sync with the schema definition below?
> diff --git a/Documentation/devicetree/bindings/arm/apple.yaml b/Documentation/devicetree/bindings/arm/apple.yaml
> index e49403c73f9d2..3262292252d25 100644
> --- a/Documentation/devicetree/bindings/arm/apple.yaml
> +++ b/Documentation/devicetree/bindings/arm/apple.yaml
> @@ -315,6 +315,18 @@ properties:
> - const: apple,t8122
> - const: apple,arm-platform
>
> + - description: Apple M4 SoC based platforms
> + items:
> + - enum:
> + - apple,j604 # MacBook Pro (14-inch, M4, 2024)
> + - apple,j623 # iMac (24-inch, 2x USB-C, M4, 2024)
> + - apple,j624 # iMac (24-inch, 4x USB-C, M4, 2024)
> + - apple,j713 # MacBook Air (13-inch, M3, 2025)
> + - apple,j715 # MacBook Air (15-inch, M3, 2025)
[Severity: Low]
Are these inline comments correct, or should they say M4 instead of M3 for
the new 2025 MacBook Air models?
> + - apple,j773g # Mac mini (M4, 2024)
> + - const: apple,t8132
> + - const: apple,arm-platform
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260705-apple-m4-initial-devicetrees-v1-0-e5655ee56523@cyberchaos.dev?part=9
next prev parent 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 [this message]
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
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=20260705132819.9CA9C1F000E9@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