From: Neil Cheng <neilcheng0417@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
geert+renesas@glider.be, magnus.damm@gmail.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Neil Cheng <neilcheng0417@gmail.com>
Subject: [PATCH v2 0/2] Add Meta Rainiera6 BMC support
Date: Tue, 19 May 2026 10:38:36 +0800 [thread overview]
Message-ID: <cover.1779157117.git.neilcheng0417@gmail.com> (raw)
In-Reply-To: <cover.1779088499.git.neilcheng0417@gmail.com>
Add initial device tree support for the Meta Rainiera6 platform.
Changes in v2:
- reorder adc0/adc1 properties
- add Acked-by from Conor Dooley
This series adds:
- Meta Rainiera6 compatible entry
- Rainiera6 BMC DTS
The DTS has been validated with:
- make dtbs
- make dt_binding_check
- make CHECK_DTBS=y
Neil Cheng (2):
dt-bindings: arm: aspeed: Add Meta Rainiera6 board
ARM: dts: aspeed: rainiera6: Add Meta Rainiera6 BMC
.../bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../aspeed/aspeed-bmc-facebook-rainiera6.dts | 1012 +++++++++++++++++
3 files changed, 1014 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-rainiera6.dts
--
2.25.1
next prev parent reply other threads:[~2026-05-19 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 8:13 [PATCH 0/2] Add Meta Rainiera6 BMC support Neil Cheng
2026-05-18 8:13 ` [PATCH 1/2] dt-bindings: arm: aspeed: Add Meta Rainiera6 board Neil Cheng
2026-05-18 16:28 ` Conor Dooley
2026-05-18 8:13 ` [PATCH 2/2] ARM: dts: aspeed: rainiera6: Add Meta Rainiera6 BMC Neil Cheng
2026-05-18 9:45 ` Biju Das
2026-05-19 2:38 ` Neil Cheng [this message]
2026-05-19 2:38 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: Add Meta Rainiera6 board Neil Cheng
2026-05-19 2:38 ` [PATCH v2 2/2] ARM: dts: aspeed: rainiera6: Add Meta Rainiera6 BMC Neil Cheng
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=cover.1779157117.git.neilcheng0417@gmail.com \
--to=neilcheng0417@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--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=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@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