From: leo.jt.wang@gmail.com
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: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
george.kw.lee@fii-foxconn.com, leo.jt.wang@fii-foxconn.com
Subject: [PATCH v4 0/2] Add Meta(Facebook) Clemente BMC(AST2600)
Date: Tue, 27 May 2025 23:08:47 +0800 [thread overview]
Message-ID: <6835d5d4.050a0220.14ffd7.0e10@mx.google.com> (raw)
In-Reply-To: <f168126c-e0e2-40d3-9b9b-2a5002a75474@kernel.org>
From: Leo Wang <leo.jt.wang@fii-foxconn.com>
Add Linux device tree entry related to Meta(Facebook) Clemente specific
devices connected to BMC(AST2600) SoC.
Signed-off-by: Leo Wang <leo.jt.wang@fii-foxconn.com>
---
Changes in v3:
- Dropped blank line as requested by reviewer.
Changes in v2:
- Fixed all dt-schema warnings/errors reported by checkpatch.
Changes in v2:
- Added 'Acked-by: Conor Dooley <conor.dooley@microchip.com>' tag.
Leo Wang (2):
dt-bindings: arm: aspeed: add Meta Clemente board
ARM: dts: aspeed: clemente: add Meta Clemente BMC
.../bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../aspeed/aspeed-bmc-facebook-clemente.dts | 1195 +++++++++++++++++
3 files changed, 1197 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts
--
2.43.0
next prev parent reply other threads:[~2025-05-27 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 3:10 [PATCH 1/2] dt-bindings: arm: aspeed: add Meta Clemente board leo.jt.wang
2025-05-13 7:44 ` Krzysztof Kozlowski
2025-05-14 3:24 ` leo.jt.wang
2025-05-14 6:44 ` [PATCH V2 " leo.jt.wang
2025-05-26 9:59 ` [PATCH V3 " leo.jt.wang
2025-05-26 12:51 ` Krzysztof Kozlowski
2025-05-27 15:08 ` leo.jt.wang [this message]
[not found] ` <20250527150946.2815348-1-LeoWang>
2025-05-27 15:08 ` [PATCH v4 " leo.jt.wang
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=6835d5d4.050a0220.14ffd7.0e10@mx.google.com \
--to=leo.jt.wang@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.kw.lee@fii-foxconn.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=leo.jt.wang@fii-foxconn.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--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