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>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v5 0/2] Add device tree for NVIDIA BMC MSX4 CX8 switchboard
Date: Wed, 26 Nov 2025 16:43:05 -0800 [thread overview]
Message-ID: <20251126-msx1_devicetree-v5-0-e508d13e2dda@nvidia.com> (raw)
Patch 1 Adds the binding for the MSX4 CX8 switchboard
Patch 2 Adds the device tree for the MSX4 CX8 switchboard reference implementation.
This is an Aspeed AST2600 based reference implementation for a BMC
managing the NVIDIA MGX CX8 switchboard.
Reference to Ast2600 Soc [1].
Reference to host architecture [2].
Link: https://www.aspeedtech.com/server_ast2600/ [1]
Link: https://developer.nvidia.com/blog/nvidia-connectx-8-supernics-advance-ai-platform-architecture-with-pcie-gen6-connectivity/ [2]
Signed-off-by: Marc Olberding <molberding@nvidia.com>
---
Changes in v5:
- Fixed the spi-lane count for flash0 on the fmc.
- Cleaned up the commit messages per Andrew Jeffery's request
- Link to v4: https://lore.kernel.org/r/20251124-msx1_devicetree-v4-0-a3ebe3110a67@nvidia.com
Changes in v4:
- Changed model name to be accurate per Andrew Jeffery
- Added comments about why there are no i2c devices described here per Andrew Jeffery
- Added support for probing the backup spi device through fmc
- Link to v3: https://lore.kernel.org/r/20251108-msx1_devicetree-v3-0-c7cb477ade27@nvidia.com
Changes in v3:
- Removed mac and mdio node completely per Andrew Lunn's request. Will add back
once the mac driver is fixed
- Link to v2: https://lore.kernel.org/r/20251107-msx1_devicetree-v2-0-6e36eb878db2@nvidia.com
Changes in v2:
- Added ack by Conor Dooley on patch 1
- Changed phy-mode attribute after discussion with Andrew Jeffery and feedback from Andrew Lunn
and added a comment with a better explanation
- Link to v1: https://lore.kernel.org/r/20250918-msx1_devicetree-v1-1-18dc07e02118@nvidia.com
---
Marc Olberding (2):
dt-bindings: arm: aspeed: Add Nvidia msx4 board
ARM: dts: aspeed: Add NVIDIA MSX4 HPM
.../devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../boot/dts/aspeed/aspeed-bmc-nvidia-msx4-bmc.dts | 246 +++++++++++++++++++++
3 files changed, 248 insertions(+)
---
base-commit: ac3fd01e4c1efce8f2c054cdeb2ddd2fc0fb150d
change-id: 20250908-msx1_devicetree-7af2c1fc15d0
Best regards,
--
Marc Olberding <molberding@nvidia.com>
next reply other threads:[~2025-11-27 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 0:43 Marc Olberding [this message]
2025-11-27 0:43 ` [PATCH v5 1/2] dt-bindings: arm: aspeed: Add Nvidia msx4 board Marc Olberding
2025-11-27 0:43 ` [PATCH v5 2/2] ARM: dts: aspeed: Add NVIDIA MSX4 HPM Marc Olberding
2025-12-04 0:29 ` [PATCH v5 0/2] Add device tree for NVIDIA BMC MSX4 CX8 switchboard Andrew Jeffery
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=20251126-msx1_devicetree-v5-0-e508d13e2dda@nvidia.com \
--to=molberding@nvidia.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--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