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 v2 1/2] dt-bindings: arm: aspeed: add ASRock X470D4U BMC
Date: Sat, 11 Oct 2025 13:21:19 +0200 [thread overview]
Message-ID: <20251011112124.17588-2-tan@siewert.io> (raw)
In-Reply-To: <20251011112124.17588-1-tan@siewert.io>
Document ASRock's X470D4U BMC board compatible.
Signed-off-by: Tan Siewert <tan@siewert.io>
---
v2: No changes
---
Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
index aedefca7cf4a..02ac7c4d92e9 100644
--- a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
+++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
@@ -38,6 +38,7 @@ properties:
- asrock,e3c256d4i-bmc
- asrock,romed8hm3-bmc
- asrock,spc621d8hm3-bmc
+ - asrock,x470d4u-bmc
- asrock,x570d4u-bmc
- bytedance,g220a-bmc
- facebook,cmm-bmc
--
2.50.1
next prev parent reply other threads:[~2025-10-11 11:21 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 ` Tan Siewert [this message]
2025-10-12 3:03 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: add ASRock X470D4U BMC 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
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=20251011112124.17588-2-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 \
--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).