From: "Rob Herring (Arm)" <robh@kernel.org>
To: soc@kernel.org,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
Richard Cochran <richardcochran@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/4] arm64: dts: amd/seattle: Base Overdrive B1 on top of B0 version
Date: Thu, 06 Mar 2025 19:07:43 -0600 [thread overview]
Message-ID: <20250306-dt-amd-fixes-v1-1-011c423ba99a@kernel.org> (raw)
In-Reply-To: <20250306-dt-amd-fixes-v1-0-011c423ba99a@kernel.org>
AMD Overdrive B1 version is just more peripherals enabled over B0
version. Rework the B1 .dts to use the B0 .dts.
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts | 61 +-----------------------
1 file changed, 1 insertion(+), 60 deletions(-)
diff --git a/arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts b/arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts
index 58e2b0a6f841..b34dd8d5d1b1 100644
--- a/arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts
+++ b/arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts
@@ -8,32 +8,10 @@
/dts-v1/;
-/include/ "amd-seattle-soc.dtsi"
-/include/ "amd-seattle-cpus.dtsi"
+/include/ "amd-overdrive-rev-b0.dts"
/ {
model = "AMD Seattle (Rev.B1) Development Board (Overdrive)";
- compatible = "amd,seattle-overdrive", "amd,seattle";
-
- chosen {
- stdout-path = &serial0;
- };
-
- psci {
- compatible = "arm,psci-0.2";
- method = "smc";
- };
-};
-
-&ccp0 {
- status = "okay";
-};
-
-/**
- * NOTE: In Rev.B, gpio0 is reserved.
- */
-&gpio1 {
- status = "okay";
};
&gpio2 {
@@ -44,48 +22,11 @@ &gpio3 {
status = "okay";
};
-&gpio4 {
- status = "okay";
-};
-
-&i2c0 {
- status = "okay";
-};
-
-&i2c1 {
- status = "okay";
-};
-
-&pcie0 {
- status = "okay";
-};
-
&sata1 {
status = "okay";
};
-&spi0 {
- status = "okay";
-};
-
-&spi1 {
- status = "okay";
- sdcard0: sdcard@0 {
- compatible = "mmc-spi-slot";
- reg = <0>;
- spi-max-frequency = <20000000>;
- voltage-ranges = <3200 3400>;
- pl022,interface = <0>;
- pl022,com-mode = <0x0>;
- pl022,rx-level-trig = <0>;
- pl022,tx-level-trig = <0>;
- };
-};
-
&ipmi_kcs {
status = "okay";
};
-&smb0 {
- /include/ "amd-seattle-xgbe-b.dtsi"
-};
--
2.47.2
next prev parent reply other threads:[~2025-03-07 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 1:07 [PATCH 0/4] arm64: dts: AMD Seattle clean-ups Rob Herring (Arm)
2025-03-07 1:07 ` Rob Herring (Arm) [this message]
2025-03-07 15:54 ` [PATCH 1/4] arm64: dts: amd/seattle: Base Overdrive B1 on top of B0 version Krzysztof Kozlowski
2025-03-07 1:07 ` [PATCH 2/4] arm64: dts: amd/seattle: Move and simplify fixed clocks Rob Herring (Arm)
2025-03-07 15:52 ` Krzysztof Kozlowski
2025-03-07 1:07 ` [PATCH 3/4] arm64: dts: amd/seattle: Fix bus, mmc, and ethernet node names Rob Herring (Arm)
2025-03-07 15:53 ` Krzysztof Kozlowski
2025-03-07 1:07 ` [PATCH 4/4] arm64: dts: amd/seattle: Drop undocumented "spi-controller" properties Rob Herring (Arm)
2025-03-07 15:51 ` Krzysztof Kozlowski
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=20250306-dt-amd-fixes-v1-1-011c423ba99a@kernel.org \
--to=robh@kernel.org \
--cc=Shyam-sundar.S-k@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=soc@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=thomas.lendacky@amd.com \
/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;
as well as URLs for NNTP newsgroup(s).