From: Janne Grunau <j@jannau.net>
To: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Sven Peter" <sven@kernel.org>, "Neal Gompa" <neal@gompa.dev>,
"Wim Van Sebroeck" <wim@linux-watchdog.org>,
"Guenter Roeck" <linux@roeck-us.net>,
"Mark Kettenis" <kettenis@openbsd.org>,
"Sasha Finkelstein" <k@chaosmail.tech>,
"Uwe Kleine-König" <ukleinek@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-watchdog@vger.kernel.org, linux-pwm@vger.kernel.org,
Janne Grunau <j@jannau.net>,
Joshua Peisach <jpeisach@ubuntu.com>,
Michael Reeves <michael.reeves077@gmail.com>
Subject: [PATCH v3 0/5] Initial Apple silicon M3 device trees and dt-bindings
Date: Thu, 07 May 2026 09:33:06 +0200 [thread overview]
Message-ID: <20260507-apple-m3-initial-devicetrees-v3-0-ca07c81b5dc7@jannau.net> (raw)
Hej,
This series adds initial device trees for M3 Apple silicon devices. The
device trees contain only a minimal set of hardware not going much
beyond the minimum required for booting kernel and initramfs and
verify via serial console that the hardware and drivers work.
The hardware with the exception of the interrupt controller is
compatible with the M1 and M2 SoCs and the existing drivers.
`make dtbs_check` depends on the already applied and dropped apple,i2c
and apple,pmgr dt-binding changes.
The watchdog load depends on stalled and forgotten addition of the
"apple,t8103-wdt" compatible posted in [1]. I've replied to the thread
to get the change merged.
Merge strategy:
Apply whole series via apple-soc / arm-soc to keep `make dtbs_check`
errors minimal. Otherwise no dependencies between the patches.
I might want to send another series which depends on this later in this
cycle.
Link: https://lore.kernel.org/linux-watchdog/20251231-watchdog-apple-t8103-base-compat-v1-1-1702a02e0c45@jannau.net/ [1]
Signed-off-by: Janne Grunau <j@jannau.net>
---
Changes in v3:
- adjust reg size of pmgr node to fit all its childrens' regs. Improper
size was caused by a bug in the script used to convert Apple's
power-states into DT nodes
- drop picked up changes from v2:
- [PATCH v2 1/6] dt-bindings: arm: apple: apple,pmgr: Add t8122 compatible" (for v7.2-rc1)
- Link to v2: https://lore.kernel.org/r/20260505-apple-m3-initial-devicetrees-v2-0-b0c2f3519e0e@jannau.net
Changes in v2:
- specify merge strategy
- rebased onto v7.1-rc1 and thus dropping the aic3 comment
- collect Acked-by and Reviewed-by: tags
- drop already picked up changes:
- [PATCH 1/9] dt-bindings: arm: cpus: Add Apple M3 CPU core compatibles (in v7.1-rc1)
- [PATCH 5/9] dt-bindings: pinctrl: apple,pinctrl: Add t8122 compatible (in v7.1-rc1)
- [PATCH 6/9] dt-bindings: i2c: apple,i2c: Add t8122 compatible (for v7.2-rc1)
- Link to v1: https://lore.kernel.org/r/20260320-apple-m3-initial-devicetrees-v1-0-5842e1e393a8@jannau.net
---
Janne Grunau (5):
dt-bindings: power: apple,pmgr-pwrstate: Add t8122 compatible
dt-bindings: watchdog: apple,wdt: Add t8122 compatible
dt-bindings: pwm: apple,s5l-fpwm: Add t8122 compatible
dt-bindings: arm: apple: Add M3 based devices
arm64: dts: apple: Initial t8122 (M3) device trees
Documentation/devicetree/bindings/arm/apple.yaml | 18 +
.../bindings/power/apple,pmgr-pwrstate.yaml | 4 +-
.../devicetree/bindings/pwm/apple,s5l-fpwm.yaml | 1 +
.../devicetree/bindings/watchdog/apple,wdt.yaml | 4 +-
arch/arm64/boot/dts/apple/Makefile | 5 +
arch/arm64/boot/dts/apple/t8122-j433.dts | 19 +
arch/arm64/boot/dts/apple/t8122-j434.dts | 19 +
arch/arm64/boot/dts/apple/t8122-j504.dts | 37 +
arch/arm64/boot/dts/apple/t8122-j613.dts | 35 +
arch/arm64/boot/dts/apple/t8122-j615.dts | 35 +
arch/arm64/boot/dts/apple/t8122-jxxx.dtsi | 48 +
arch/arm64/boot/dts/apple/t8122-pmgr.dtsi | 1149 ++++++++++++++++++++
arch/arm64/boot/dts/apple/t8122-usbpd-i2c.dtsi | 32 +
arch/arm64/boot/dts/apple/t8122.dtsi | 444 ++++++++
14 files changed, 1848 insertions(+), 2 deletions(-)
---
base-commit: 37a578184d32b2e8110aa88c1c1fd10a23419e01
change-id: 20260319-apple-m3-initial-devicetrees-5c546ad977a2
Best regards,
--
Janne Grunau <j@jannau.net>
next reply other threads:[~2026-05-07 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 7:33 Janne Grunau [this message]
2026-05-07 7:33 ` [PATCH v3 1/5] dt-bindings: power: apple,pmgr-pwrstate: Add t8122 compatible Janne Grunau
2026-05-07 7:33 ` [PATCH v3 2/5] dt-bindings: watchdog: apple,wdt: " Janne Grunau
2026-05-10 15:29 ` 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
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=20260507-apple-m3-initial-devicetrees-v3-0-ca07c81b5dc7@jannau.net \
--to=j@jannau.net \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jpeisach@ubuntu.com \
--cc=k@chaosmail.tech \
--cc=kettenis@openbsd.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lpieralisi@kernel.org \
--cc=michael.reeves077@gmail.com \
--cc=neal@gompa.dev \
--cc=robh@kernel.org \
--cc=sven@kernel.org \
--cc=ukleinek@kernel.org \
--cc=wim@linux-watchdog.org \
/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