From: Kelly Hung <ppighouse@gmail.com>
To: robh+dt@kernel.org
Cc: krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
kelly_hung@asus.com, Kelly Hung <Kelly_Hung@asus.com>
Subject: [PATCH] ARM: dts: aspeed: asus: Add ASUS X4TF BMC
Date: Tue, 30 Jan 2024 16:56:51 +0800 [thread overview]
Message-ID: <20240130085652.198010-1-Kelly_Hung@asus.com> (raw)
This initial device-tree provides the necessary configuration for
basic BMC functionality and work on ASUS X4TF production.
Signed-off-by: Kelly Hung <Kelly_Hung@asus.com>
---
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 749ee54a3ff8..80009948e14a 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
- facebook,bletchley-bmc
- facebook,cloudripper-bmc
- facebook,elbert-bmc
--
2.25.1
next reply other threads:[~2024-01-30 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 8:56 Kelly Hung [this message]
2024-01-30 8:56 ` [PATCH] ARM: dts: aspeed: asus: Add ASUS X4TF BMC Kelly Hung
2024-01-30 10:39 ` Krzysztof Kozlowski
2024-03-04 10:45 ` Kelly Hung(洪嘉莉)
2024-03-04 11:23 ` Krzysztof Kozlowski
2024-03-05 3:52 ` Kelly Hung(洪嘉莉)
2024-01-30 10:39 ` Krzysztof Kozlowski
2024-03-05 4:04 ` Kelly Hung(洪嘉莉)
2024-01-30 10:35 ` Krzysztof Kozlowski
2024-03-05 4:15 ` 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=20240130085652.198010-1-Kelly_Hung@asus.com \
--to=ppighouse@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=kelly_hung@asus.com \
--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=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