From: Kelly Hung <ppighouse@gmail.com>
To: robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Kelly Hung <Kelly_Hung@asus.com>,
joel@jms.id.au, krzysztof.kozlowski+dt@linaro.org,
Allenyy_Hsu@asus.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board
Date: Thu, 29 Feb 2024 17:09:12 +0800 [thread overview]
Message-ID: <20240229090913.1892215-1-Kelly_Hung@asus.com> (raw)
Document the new compatibles used on ASUS X4TF.
Signed-off-by: Kelly Hung <Kelly_Hung@asus.com>
---
Changes in v4:
- The new compatible is a BMC for a ASUS X4TF server which use a ast2600-a3 chip,
so correct string to asus,x4tf-bmc.
---
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 749ee54a3..0047eb4ab 100644
--- a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
+++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
@@ -74,6 +74,7 @@ properties:
- ampere,mtmitchell-bmc
- aspeed,ast2600-evb
- aspeed,ast2600-evb-a1
+ - asus,x4tf-bmc
- facebook,bletchley-bmc
- facebook,cloudripper-bmc
- facebook,elbert-bmc
--
2.25.1
next reply other threads:[~2024-02-29 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 9:09 Kelly Hung [this message]
2024-02-29 9:09 ` [PATCH v4 2/2] ARM: dts: aspeed: x4tf: Add dts for asus x4tf project Kelly Hung
[not found] ` <7f60e293-8076-4a06-9b6b-35f9c19578c4@linaro.org>
2024-02-29 11:18 ` [PATCH v4 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board Kelly Hung(洪嘉莉)
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=20240229090913.1892215-1-Kelly_Hung@asus.com \
--to=ppighouse@gmail.com \
--cc=Allenyy_Hsu@asus.com \
--cc=Kelly_Hung@asus.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@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 read-only IMAP folder(s) and NNTP newsgroup(s).