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>, Zev Weiss <zev@bewilderbeest.net>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] ARM: dts: aspeed: ASRock Rack X470D4U BMC support
Date: Wed, 12 Aug 2026 22:28:25 +0200 [thread overview]
Message-ID: <20260812-ts-x470d4u-v3-0-c8e266f1663b@siewert.io> (raw)
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.
There are two device trees, one that has all the config and uses a 32MB
flash layout, and another one called "data64" (similar to facebook-fuji)
that uses the 64MB flash layout.
Please note that this board has been fully reverse-engineered.
Thanks,
Tan
Signed-off-by: Tan Siewert <tan@siewert.io>
---
Changes in v3:
- remove mdio pinctrl from mac1 nc-si interface [Andrew Jeffrey]
- remove "st,24c128" compatibility from fru eeprom [Tan]
- enable uart1-4 [Tan]
- add a data64 tree as alternative for boards with a 64M SPI [Zev]
- add hog to bmc-ready GPIO pin as required by the host BIOS [Tan]
- fix offenses reported by scripts/dtc/dt-check-style --mode strict [Tan]
- Link to v2: https://lore.kernel.org/all/20251011112124.17588-1-tan@siewert.io/
Changes in v2:
- fix led node names [robh]
- fix missing gfx memory region and other fixable dtbs_check issues [Tan]
- Link to v1: https://lore.kernel.org/all/20250919185621.6647-1-tan@siewert.io/
To: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk+dt@kernel.org>
To: Conor Dooley <conor+dt@kernel.org>
To: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: Zev Weiss <zev@bewilderbeest.net>
Cc: devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-aspeed@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
---
Tan Siewert (2):
dt-bindings: arm: aspeed: add ASRock X470D4U BMC
ARM: dts: aspeed: add asrock x470d4u bmc
.../devicetree/bindings/arm/aspeed/aspeed.yaml | 2 +
arch/arm/boot/dts/aspeed/Makefile | 2 +
.../aspeed/aspeed-bmc-asrock-x470d4u-data64.dts | 15 +
.../boot/dts/aspeed/aspeed-bmc-asrock-x470d4u.dts | 381 +++++++++++++++++++++
4 files changed, 400 insertions(+)
---
base-commit: 749c34389679f8d56cb200a69b62f9a64670034f
change-id: 20251017-ts-x470d4u-54b9e98e4333
Best regards,
--
Tan Siewert <tan@siewert.io>
next reply other threads:[~2026-08-12 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 20:28 Tan Siewert [this message]
2026-08-12 20:28 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASRock X470D4U BMC Tan Siewert
2026-08-12 20:28 ` [PATCH v3 2/2] ARM: dts: aspeed: add asrock x470d4u bmc Tan Siewert
2026-08-16 4:49 ` Zev Weiss
2026-08-16 10:55 ` Tan Siewert
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=20260812-ts-x470d4u-v3-0-c8e266f1663b@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 \
--cc=zev@bewilderbeest.net \
/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