From: Renze Nicolai <renze@rnplus.nl>
To: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
arnd@arndb.de, olof@lixom.net, soc@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
joel@jms.id.au, andrew@aj.id.au, renze@rnplus.nl
Subject: [PATCH v3 0/2] ARM: dts: aspeed: asrock: Add ASRock X570D4U BMC
Date: Sat, 2 Dec 2023 01:38:43 +0100 [thread overview]
Message-ID: <20231202003908.3635695-1-renze@rnplus.nl> (raw)
Hello,
These patches add a device-tree (and a bindings update) for the
Aspeed BMC on the ASRock X570D4U, so that it can be added as a
supported OpenBMC platform.
Changes since v2:
- Renamed leds to led-0 and led-1 to match Documentation/devicetree/bindings/leds/leds-gpio.yaml
- Added aliasses and labels for the i2c-mux on i2c bus 4
- Added the missing blank line between the ehci1 and uhci nodes
Greetings,
Renze Nicolai
Renze Nicolai (2):
dt-bindings: arm: aspeed: add Asrock X570D4U board
ARM: dts: aspeed: asrock: Add ASRock X570D4U BMC
.../bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../dts/aspeed/aspeed-bmc-asrock-x570d4u.dts | 377 ++++++++++++++++++
3 files changed, 379 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-asrock-x570d4u.dts
--
2.43.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-12-02 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 0:38 Renze Nicolai [this message]
2023-12-02 0:38 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: add Asrock X570D4U board Renze Nicolai
2023-12-02 0:38 ` [PATCH v3 2/2] ARM: dts: aspeed: asrock: Add ASRock X570D4U BMC Renze Nicolai
2023-12-02 0:44 ` [PATCH v3 0/2] " Renze Nicolai
2023-12-06 6:46 ` Joel Stanley
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=20231202003908.3635695-1-renze@rnplus.nl \
--to=renze@rnplus.nl \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--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=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@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