From: Michael Reeves via B4 Relay <devnull+michael.reeves077.gmail.com@kernel.org>
To: Sven Peter <sven@kernel.org>, Janne Grunau <j@jannau.net>,
Neal Gompa <neal@gompa.dev>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Hector Martin <marcan@marcan.st>
Cc: asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Michael Reeves <michael.reeves077@gmail.com>,
Yureka Lilian <yureka@cyberchaos.dev>
Subject: [PATCH 0/4] arm64: dts: apple: Add CPU frequency scaling and OPPs for M3 family
Date: Sat, 21 Nov 2026 11:42:45 +0000 [thread overview]
Message-ID: <20261121-m3-cpufreq-opp-v1-0-42a0c07c48a4@gmail.com> (raw)
Hi folks,
This series adds CPU frequency scaling support, operating performance
point tables, and asymmetric CPU capacity values for the following
Apple M3 family SoCs:
- T8122 (M3)
- T6030 (M3 Pro)
- T6031 / T6034 (M3 Max)
On T6032 (M3 Ultra), the cores on the first die inherit this support
from M3 Max, however those on the second are not supported yet.
This series is based on apple-soc/dt-7.5.
Thanks,
Michael
Signed-off-by: Michael Reeves <michael.reeves077@gmail.com>
---
Janne Grunau (2):
arm64: dts: apple: t8122: Add CPU frequency scaling and OPPs
arm64: dts: apple: t6030: Add CPU frequency scaling and OPPs
Michael Reeves (1):
dt-bindings: cpufreq: apple,cluster-cpufreq: Add M3 family compatibles
Yureka Lilian (1):
arm64: dts: apple: t6031: Add CPU frequency scaling and OPPs
.../bindings/cpufreq/apple,cluster-cpufreq.yaml | 6 +-
arch/arm64/boot/dts/apple/t6030.dtsi | 228 +++++++++++++++++++++
arch/arm64/boot/dts/apple/t6031-base.dtsi | 213 +++++++++++++++++++
arch/arm64/boot/dts/apple/t6031-dieX.dtsi | 21 ++
arch/arm64/boot/dts/apple/t8122.dtsi | 210 +++++++++++++++++++
5 files changed, 677 insertions(+), 1 deletion(-)
---
base-commit: 477f3d0f46b0d885f162a64d13ca51e2f7afa542
change-id: 20261121-m3-cpufreq-opp-e6d93a871c2b
Best regards,
--
Michael Reeves <michael.reeves077@gmail.com>
next reply other threads:[~2026-11-21 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 11:42 Michael Reeves via B4 Relay [this message]
2026-11-21 11:42 ` [PATCH 1/4] dt-bindings: cpufreq: apple,cluster-cpufreq: Add M3 family compatibles Michael Reeves via B4 Relay
2026-11-21 11:42 ` [PATCH 2/4] arm64: dts: apple: t8122: Add CPU frequency scaling and OPPs Michael Reeves via B4 Relay
2026-11-21 11:42 ` [PATCH 3/4] arm64: dts: apple: t6030: " Michael Reeves via B4 Relay
2026-11-21 11:42 ` [PATCH 4/4] arm64: dts: apple: t6031: " Michael Reeves via B4 Relay
2026-11-21 11:52 ` Michael Reeves
2026-11-21 11:52 ` [PATCH 0/4] arm64: dts: apple: Add CPU frequency scaling and OPPs for M3 family 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=20261121-m3-cpufreq-opp-v1-0-42a0c07c48a4@gmail.com \
--to=devnull+michael.reeves077.gmail.com@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=michael.reeves077@gmail.com \
--cc=neal@gompa.dev \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sven@kernel.org \
--cc=viresh.kumar@linaro.org \
--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
all inboxes | Powered by JetHome®