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/4] Revise Meta Santabarbara devicetree
Date: Thu, 14 Aug 2025 21:16:56 +0800 [thread overview]
Message-ID: <20250814131706.1567067-1-fredchen.openbmc@gmail.com> (raw)
Summary:
Revise linux device tree entry related to Meta (Facebook) Santabarbara.
Change log
v1 -> v2:
- add 'bmc_ready_noled' LED and update commit message
- add sgpio line name for leak detection
v1:
- add sensor nodes for extension board
- add mctp node for NIC
- adjust LED configuration
Fred Chen (4):
ARM: dts: aspeed: santabarbara: add sensor support for extension
boards
ARM: dts: aspeed: santabarbara: Enable MCTP for frontend NIC
ARM: dts: aspeed: santabarbara: Adjust LED configuration
ARM: dts: aspeed: santabarbara: add sgpio line name for leak detection
.../aspeed-bmc-facebook-santabarbara.dts | 857 +++++++++++++++++-
1 file changed, 853 insertions(+), 4 deletions(-)
--
2.49.0
next reply other threads:[~2025-08-14 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:16 Fred Chen [this message]
2025-08-14 13:16 ` [PATCH v2 1/4] ARM: dts: aspeed: santabarbara: add sensor support for extension boards Fred Chen
2025-08-14 13:16 ` [PATCH v2 2/4] ARM: dts: aspeed: santabarbara: Enable MCTP for frontend NIC Fred Chen
2025-08-14 13:16 ` [PATCH v2 3/4] ARM: dts: aspeed: santabarbara: Adjust LED configuration Fred Chen
2025-08-14 13:17 ` [PATCH v2 4/4] ARM: dts: aspeed: santabarbara: add sgpio line name for leak detection Fred Chen
2025-08-15 21:19 ` [PATCH v2 0/4] Revise Meta Santabarbara devicetree Rob Herring (Arm)
2025-09-03 5:16 ` 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=20250814131706.1567067-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).