From: sashiko-bot@kernel.org
To: "Yureka Lilian" <yureka@cyberchaos.dev>
Cc: linux-watchdog@vger.kernel.org, robh@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH 09/10] dt-bindings: arm: apple: Add M4 Pro/Max based devices
Date: Sat, 10 Oct 2026 17:12:44 +0000 [thread overview]
Message-ID: <sashiko-outbox-166773@kernel.org> (raw)
In-Reply-To: <20261010-apple-m4-pro-max-initial-devicetrees-v1-9-781fb3f2d9f6@cyberchaos.dev>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] dt-bindings: missing blank line before M4 Pro/Max list in description
- [Low] dt-bindings: orphaned t6050-aic3 compatible in aic2 schema
--
commit fae2108ff5a60b40ae253b364d3bc3ad16bac012
Author: Yureka Lilian <yureka@cyberchaos.dev>
dt-bindings: arm: apple: Add M4 Pro/Max based devices
This commit adds device tree compatibles for the M4 Pro and M4 Max
based MacBook Pro, Mac mini, and Mac Studio devices. It updates the
top-level device listing and defines the required matching properties
for these platforms.
> diff --git a/Documentation/devicetree/bindings/arm/apple.yaml b/Documentation/devicetree/bindings/arm/apple.yaml
> --- a/Documentation/devicetree/bindings/arm/apple.yaml
> +++ b/Documentation/devicetree/bindings/arm/apple.yaml
> @@ -144,6 +144,14 @@ description: |
> - MacBook Pro (16-inch, M3 Max, 2023)
> - Mac Studio (M3 Ultra, 2025)
>
> + Devices based on the "M4 Pro" and "M4 Max" SoCs:
[Severity: Low]
Is there a missing blank line before this heading?
Most prior generation entries in this description block separate the
generation heading and device list with a blank line for readability.
Adding a blank line before this heading would keep the text formatting
consistent.
> + - MacBook Pro (14-inch, M4 Pro, 2024)
> + - MacBook Pro (14-inch, M4 Max, 2024)
[ ... ]
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml b/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
> --- a/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
> @@ -134,6 +136,7 @@ allOf:
> - apple,t6000-aic
> - apple,t6020-aic
> - apple,t6031-aic3
> + - apple,t6050-aic3
> then:
> properties:
[Severity: Low]
Does this compatible string also need to be in the top-level enum list?
This compatible string was added to the conditional block here in an earlier
commit in this series, but it appears to be completely missing from the
top-level properties:compatible enum definition.
Any device tree attempting to use apple,t6050-aic3 will fail schema
validation at the top-level compatible check, which makes this condition
effectively dead code.
While t6041-aic3 correctly uses 3 interrupt cells and does not belong in this
4-cell branch, the apple,t6050-aic3 string added here has no matching
top-level enum. Should it be added to the top-level list, or was this string
included here by mistake?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261010-apple-m4-pro-max-initial-devicetrees-v1-0-781fb3f2d9f6@cyberchaos.dev?part=9
next prev parent reply other threads:[~2026-10-10 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 16:59 [PATCH 00/10] Initial Apple Silicon M4 Pro/Max device trees and dt-bindings Yureka Lilian
2026-10-10 16:59 ` [PATCH 01/10] dt-bindings: watchdog: apple,wdt: Add t6041 compatible Yureka Lilian
2026-10-10 16:59 ` [PATCH 02/10] dt-bindings: interrupt-controller: apple,aic2: " Yureka Lilian
2026-10-10 17:07 ` sashiko-bot
2026-10-10 17:11 ` Yureka Lilian
2026-10-10 17:16 ` Yureka Lilian
2026-10-10 16:59 ` [PATCH 03/10] dt-bindings: arm: cpus: Add Apple M4 Pro/Max CPU core compatibles Yureka Lilian
2026-10-10 16:59 ` [PATCH 04/10] dt-bindings: arm: power: apple,pmgr-pwrstate: Add t6041 compatible Yureka Lilian
2026-10-10 16:59 ` [PATCH 05/10] dt-bindings: arm: apple: apple,pmgr: " Yureka Lilian
2026-10-10 16:59 ` [PATCH 06/10] dt-bindings: pwm: apple,s5l-fpwm: " Yureka Lilian
2026-10-10 16:59 ` [PATCH 07/10] dt-bindings: pinctrl: apple,pinctrl: " Yureka Lilian
2026-10-11 20:23 ` Linus Walleij
2026-10-12 11:55 ` Yureka Lilian
2026-10-10 16:59 ` [PATCH 08/10] dt-bindings: i2c: apple,i2c: " Yureka Lilian
2026-10-10 16:59 ` [PATCH 09/10] dt-bindings: arm: apple: Add M4 Pro/Max based devices Yureka Lilian
2026-10-10 17:12 ` sashiko-bot [this message]
2026-10-10 16:59 ` [PATCH 10/10] arm64: dts: apple: Add minimal t604x (M4 Pro/Max) device trees Yureka Lilian
2026-10-10 17:09 ` sashiko-bot
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=sashiko-outbox-166773@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-gpio@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