From: Tan Siewert <tan@siewert.io>
To: Andrew Jeffery <andrew@codeconstruct.com.au>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: 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: Re: [PATCH v2 2/2] ARM: dts: aspeed: add asrock x470d4u bmc
Date: Fri, 17 Oct 2025 21:49:17 +0200 [thread overview]
Message-ID: <cae47933-ccef-491f-a79f-910686047b42@siewert.io> (raw)
In-Reply-To: <eb9ed79a820b67d7d3dbb0ab7ec6349bf962fe9c.camel@codeconstruct.com.au>
On 17.10.25 07:42, Andrew Jeffery wrote:
> On Sat, 2025-10-11 at 13:21 +0200, Tan Siewert wrote:
>> The ASRock Rack X470D4U X470D4U is a single-socket X470-based microATX
>> motherboard for Ryzen processors with an AST2500 BMC and either 32MB or
>> 64MB SPI flash.
>>
>> This mainboard exists in three known "flavors" which only differ in the
>> used host NIC, the BMC SPI size and some parts that may be un-populated.
>>
>> To keep the complexity low with the BMC SPI, use the 32MB layout
>> regardless of the used SPI or mainboard flavor.
>>
>> Signed-off-by: Tan Siewert <tan@siewert.io>
>> ---
>> v2:
>> - fix led node names [robh]
>> - fix missing gfx memory region and other offenses [Tan]
>> ---
>> arch/arm/boot/dts/aspeed/Makefile | 1 +
>> .../dts/aspeed/aspeed-bmc-asrock-x470d4u.dts | 350 ++++++++++++++++++
>> 2 files changed, 351 insertions(+)
>> create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-asrock-x470d4u.dts
>>
>> diff --git a/arch/arm/boot/dts/aspeed/Makefile b/arch/arm/boot/dts/aspeed/Makefile
>> index 0f0b5b707654..c601af36915e 100644
>> --- a/arch/arm/boot/dts/aspeed/Makefile
>> +++ b/arch/arm/boot/dts/aspeed/Makefile
>> @@ -13,6 +13,7 @@ dtb-$(CONFIG_ARCH_ASPEED) += \
>> aspeed-bmc-asrock-e3c256d4i.dtb \
>> aspeed-bmc-asrock-romed8hm3.dtb \
>> aspeed-bmc-asrock-spc621d8hm3.dtb \
>> + aspeed-bmc-asrock-x470d4u.dtb \
>> aspeed-bmc-asrock-x570d4u.dtb \
>> aspeed-bmc-asus-x4tf.dtb \
>> aspeed-bmc-bytedance-g220a.dtb \
>> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-asrock-x470d4u.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-asrock-x470d4u.dts
>> new file mode 100644
>> index 000000000000..e9804b0ace9f
>> --- /dev/null
>> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-asrock-x470d4u.dts
>> @@ -0,0 +1,350 @@
>> +// SPDX-License-Identifier: GPL-2.0+
>> +/dts-v1/;
>> +
>> +#include "aspeed-g5.dtsi"
>> +#include <dt-bindings/gpio/aspeed-gpio.h>
>> +#include <dt-bindings/leds/common.h>
>> +#include <dt-bindings/interrupt-controller/irq.h>
>> +
>> +/ {
>> + model = "Asrock Rack X470D4U-series BMC";
>> + compatible = "asrock,x470d4u-bmc", "aspeed,ast2500";
>> +
>> + aliases {
>> + serial4 = &uart5;
>> + };
>> +
>> + chosen {
>> + stdout-path = &uart5;
>> + };
>>
>>
>
> *snip*
>
>> nvmem-cell-names = "mac-address";
>> +};
>> +
>> +&mac1 {
>> + status = "okay";
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pinctrl_rmii2_default &pinctrl_mdio2_default>;
>
> If you're using NCSI you don't need the MDIO pins here, right?
Right. Will be addressed with v3.
Thanks!
Tan
>
>> + use-ncsi;
>> +
>> + nvmem-cells = <ð1_macaddress>;
>> + nvmem-cell-names = "mac-address";
>> +};
>> +
>
> Andrew
next prev parent reply other threads:[~2025-10-17 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 11:21 [PATCH v2 0/2] ARM: dts: aspeed: ASRock Rack X470D4U BMC support Tan Siewert
2025-10-11 11:21 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: add ASRock X470D4U BMC Tan Siewert
2025-10-12 3:03 ` Krzysztof Kozlowski
2025-10-11 11:21 ` [PATCH v2 2/2] ARM: dts: aspeed: add asrock x470d4u bmc Tan Siewert
2025-10-17 5:42 ` Andrew Jeffery
2025-10-17 19:49 ` Tan Siewert [this message]
2025-10-20 9:40 ` Zev Weiss
2025-10-24 20:23 ` 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=cae47933-ccef-491f-a79f-910686047b42@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;
as well as URLs for NNTP newsgroup(s).