From: Tan Siewert <tan@siewert.io>
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: Tan Siewert <tan@siewert.io>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ARM: dts: aspeed: ASRock Rack X470D4U BMC support
Date: Fri, 19 Sep 2025 20:56:16 +0200 [thread overview]
Message-ID: <20250919185621.6647-1-tan@siewert.io> (raw)
Hi,
This series adds support for the BMC of the ASRock Rack X470D4U mainboard,
which uses an ASPEED AST2500.
The mainboard exists in three known flavors, the "normal" X470D4U, the
X470D4U2-2T (with 2x10G RJ45) and the X470D4U2/1N1 (an ODM version with
2x1G RJ45 that is now available in retail). The 1N1 version also has a 64MB
BMC SPI by default, but they are all swappable.
All flavors will use the 32MB flash layout which should prevent unnecessary
complexity of the device tree.
Please note that this board has been fully reverse-engineered.
Thanks,
Tan
Tan Siewert (2):
dt-bindings: arm: aspeed: add ASRock X470D4U BMC
ARM: dts: aspeed: add asrock x470d4u bmc
.../bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../dts/aspeed/aspeed-bmc-asrock-x470d4u.dts | 345 ++++++++++++++++++
3 files changed, 347 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-asrock-x470d4u.dts
--
2.50.1
next reply other threads:[~2025-09-19 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 18:56 Tan Siewert [this message]
2025-09-19 18:56 ` [PATCH 1/2] dt-bindings: arm: aspeed: add ASRock X470D4U BMC Tan Siewert
2025-09-19 18:56 ` [PATCH 2/2] ARM: dts: aspeed: add asrock x470d4u bmc Tan Siewert
2025-09-22 20:07 ` Rob Herring
2025-09-23 14:48 ` Tan Siewert
2025-09-24 1:58 ` Andrew Jeffery
2025-10-12 3:03 ` 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=20250919185621.6647-1-tan@siewert.io \
--to=tan@siewert.io \
--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;
as well as URLs for NNTP newsgroup(s).