From: Fred Chen <fredchen.openbmc@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>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Add Meta (Facebook) Santabarbara BMC (AST2600)
Date: Wed, 25 Jun 2025 15:38:36 +0800 [thread overview]
Message-ID: <20250625073847.4054971-1-fredchen.openbmc@gmail.com> (raw)
Summary:
Add linux device tree entry related to Meta (Facebook) Santabarbara
specific devices connected to BMC (AST2600) SoC.
Change log
v1 -> v2:
- Enable mac3 node
- Add GPIO line-name FM_MUX1_SEL_R
- Remove 'pinctrl-names' from gpio0 node
- Reorder top-level nodes alphabetically
- Reorder device node properties per style
v1:
- Create santabarbara dts file.
Fred Chen (2):
dt-bindings: arm: aspeed: add Meta Santabarbara board
ARM: dts: aspeed: santabarbara: Add Meta Santabarbara BMC
.../bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../aspeed-bmc-facebook-santabarbara.dts | 982 ++++++++++++++++++
3 files changed, 984 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts
--
2.49.0
next reply other threads:[~2025-06-25 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 7:38 Fred Chen [this message]
2025-06-25 7:38 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: add Meta Santabarbara board Fred Chen
2025-06-27 20:38 ` Rob Herring (Arm)
2025-06-25 7:38 ` [PATCH v2 2/2] ARM: dts: aspeed: santabarbara: Add Meta Santabarbara BMC Fred Chen
2025-06-25 20:25 ` [PATCH v2 0/2] Add Meta (Facebook) Santabarbara BMC (AST2600) Rob Herring (Arm)
2025-06-27 0:59 ` Andrew Jeffery
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=20250625073847.4054971-1-fredchen.openbmc@gmail.com \
--to=fredchen.openbmc@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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;
as well as URLs for NNTP newsgroup(s).