From: Marc Olberding <molberding@nvidia.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Marc Olberding <molberding@nvidia.com>
Subject: [PATCH v3 2/2] ARM: dts: aspeed: Add alt partition support to msx4
Date: Tue, 20 Jan 2026 11:26:17 -0800 [thread overview]
Message-ID: <20260120-alt-128-v3-2-a81bdafc00a7@nvidia.com> (raw)
In-Reply-To: <20260120-alt-128-v3-0-a81bdafc00a7@nvidia.com>
Add support for the alt 128M partition table to the msx4. This allows it
program the flash it didn't boot from by partition.
Signed-off-by: Marc Olberding <molberding@nvidia.com>
---
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-msx4-bmc.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-msx4-bmc.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-msx4-bmc.dts
index 44f95a3986cb..a12d4164de4a 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-msx4-bmc.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-msx4-bmc.dts
@@ -67,6 +67,7 @@ flash@1 {
spi-tx-bus-width = <1>;
spi-rx-bus-width = <1>;
status = "okay";
+ #include "openbmc-flash-layout-128-alt.dtsi"
};
};
--
2.34.1
prev parent reply other threads:[~2026-01-20 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 19:26 [PATCH v3 0/2] ARM: dts: aspeed: Add an alt 128M flash layout Marc Olberding
2026-01-20 19:26 ` [PATCH v3 1/2] ARM: dts: aspeed: add " Marc Olberding
2026-01-20 19:40 ` Krzysztof Kozlowski
2026-01-20 20:30 ` Marc Olberding
2026-01-20 19:26 ` Marc Olberding [this message]
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=20260120-alt-128-v3-2-a81bdafc00a7@nvidia.com \
--to=molberding@nvidia.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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