From: Nick Chan <towinchenmi@gmail.com>
To: Sven Peter <sven@svenpeter.dev>, Janne Grunau <j@jannau.net>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Nick Chan <towinchenmi@gmail.com>
Subject: [PATCH 0/9] arm64: dts: apple: Add CPU cache information for Apple A7-A11, T2 SoCs
Date: Thu, 20 Feb 2025 20:21:41 +0800 [thread overview]
Message-ID: <20250220-caches-v1-0-2c7011097768@gmail.com> (raw)
Add CPU cache information for Apple A7-A11, T2 SoCs. On Apple
A10 (T8010), A10X (T8011), T2 (T8012), only the caches in one of the
CPU clusters can be used due to the "Apple Fusion Architecture"
big.LITTLE switcher. The values for the P-cluster is used in this
case.
Signed-off-by: Nick Chan <towinchenmi@gmail.com>
---
Nick Chan (9):
arm64: dts: apple: s5l8960x: Add CPU caches
arm64: dts: apple: t7000: Add CPU caches
arm64: dts: apple: t7001: Add CPU caches
arm64: dts: apple: s800-0-3: Add CPU caches
arm64: dts: apple: s8001: Add CPU caches
arm64: dts: apple: t8010: Add CPU caches
arm64: dts: apple: t8011: Add CPU caches
arm64: dts: apple: t8012: Add CPU caches
arm64: dts: apple: t8015: Add CPU caches
arch/arm64/boot/dts/apple/s5l8960x.dtsi | 13 +++++++++++++
arch/arm64/boot/dts/apple/s800-0-3.dtsi | 13 +++++++++++++
arch/arm64/boot/dts/apple/s8001.dtsi | 13 +++++++++++++
arch/arm64/boot/dts/apple/t7000.dtsi | 13 +++++++++++++
arch/arm64/boot/dts/apple/t7001.dtsi | 16 ++++++++++++++++
arch/arm64/boot/dts/apple/t8010.dtsi | 13 +++++++++++++
arch/arm64/boot/dts/apple/t8011.dtsi | 16 ++++++++++++++++
arch/arm64/boot/dts/apple/t8012.dtsi | 13 +++++++++++++
arch/arm64/boot/dts/apple/t8015.dtsi | 32 ++++++++++++++++++++++++++++++++
9 files changed, 142 insertions(+)
---
base-commit: 3febe9de5ca5267618675650871a626d0901f8cb
change-id: 20250220-caches-bea5d32f91fb
Best regards,
--
Nick Chan <towinchenmi@gmail.com>
next reply other threads:[~2025-02-20 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 12:21 Nick Chan [this message]
2025-02-20 12:21 ` [PATCH 1/9] arm64: dts: apple: s5l8960x: Add CPU caches Nick Chan
2025-02-20 12:21 ` [PATCH 2/9] arm64: dts: apple: t7000: " Nick Chan
2025-02-20 12:21 ` [PATCH 3/9] arm64: dts: apple: t7001: " Nick Chan
2025-02-20 12:21 ` [PATCH 4/9] arm64: dts: apple: s800-0-3: " Nick Chan
2025-02-20 12:21 ` [PATCH 5/9] arm64: dts: apple: s8001: " Nick Chan
2025-02-20 12:21 ` [PATCH 6/9] arm64: dts: apple: t8010: " Nick Chan
2025-02-20 12:21 ` [PATCH 7/9] arm64: dts: apple: t8011: " Nick Chan
2025-02-20 12:21 ` [PATCH 8/9] arm64: dts: apple: t8012: " Nick Chan
2025-02-20 12:21 ` [PATCH 9/9] arm64: dts: apple: t8015: " Nick Chan
2025-03-01 11:11 ` [PATCH 0/9] arm64: dts: apple: Add CPU cache information for Apple A7-A11, T2 SoCs Sven Peter
2025-03-01 12:32 ` Nick Chan
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=20250220-caches-v1-0-2c7011097768@gmail.com \
--to=towinchenmi@gmail.com \
--cc=alyssa@rosenzweig.io \
--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=robh@kernel.org \
--cc=sven@svenpeter.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