From: Peter Yin <peteryin.openbmc@gmail.com>
To: patrick@stwcx.xyz, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 00/10] Revise Meta(Facebook) Harma BMC(AST2600)
Date: Tue, 27 Feb 2024 09:47:09 +0800 [thread overview]
Message-ID: <20240227014719.3037588-1-peteryin.openbmc@gmail.com> (raw)
Summary:
Revise linux device tree entry related to Meta(Facebook) Harma
specific devices connected to BMC(AST2600) SoC.
Base on : https://lore.kernel.org/all/CACPK8XePx+PvDKzPMjPRn_g9z8yrtAmLvP8Qbepm1AVjuCbaKw@mail.gmail.com/
Change log:
v3 -> v4
- Patch 0010 - Revise node name
- fixed PDB temperature node name in Patch 0006
v2 -> v3
- Patch 0007 - Revise max31790 address
- Patch 0008 - Harma: Add NIC Fru device
- Patch 0009 - Add ltc4286 device
v1 -> v2
- Add infineon,slb9670 information for tpm.
- Patch 0006 - Add PDB temperature.
v1
- Patch 0001 - Revise SGPIO line name.
- Patch 0002 - Mapping ttyS2 to UART4.
- Patch 0003 - Remove Vuart.
- Patch 0004 - Add cpu power good line name.
- Patch 0005 - Add spi-gpio.
Peter Yin (10):
ARM: dts: aspeed: Harma: Revise SGPIO line name.
ARM: dts: aspeed: Harma: mapping ttyS2 to UART4.
ARM: dts: aspeed: Harma: Remove Vuart
ARM: dts: aspeed: Harma: Add cpu power good line name
ARM: dts: aspeed: Harma: Add spi-gpio
ARM: dts: aspeed: Harma: Add PDB temperature
ARM: dts: aspeed: Harma: Revise max31790 address
ARM: dts: aspeed: Harma: Add NIC Fru device
ARM: dts: aspeed: Harma: Add ltc4286 device
ARM: dts: aspeed: Harma: Revise node name
.../dts/aspeed/aspeed-bmc-facebook-harma.dts | 63 ++++++++++++++-----
1 file changed, 49 insertions(+), 14 deletions(-)
--
2.25.1
next reply other threads:[~2024-02-27 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 1:47 Peter Yin [this message]
2024-02-27 1:47 ` [PATCH v4 01/10] ARM: dts: aspeed: Harma: Revise SGPIO line name Peter Yin
2024-02-27 1:47 ` [PATCH v4 02/10] ARM: dts: aspeed: Harma: mapping ttyS2 to UART4 Peter Yin
2024-02-27 1:47 ` [PATCH v4 03/10] ARM: dts: aspeed: Harma: Remove Vuart Peter Yin
2024-02-27 1:47 ` [PATCH v4 04/10] ARM: dts: aspeed: Harma: Add cpu power good line name Peter Yin
2024-02-27 1:47 ` [PATCH v4 05/10] ARM: dts: aspeed: Harma: Add spi-gpio Peter Yin
2024-02-27 1:47 ` [PATCH v4 06/10] ARM: dts: aspeed: Harma: Add PDB temperature Peter Yin
2024-02-27 1:47 ` [PATCH v4 07/10] ARM: dts: aspeed: Harma: Revise max31790 address Peter Yin
2024-02-27 1:47 ` [PATCH v4 08/10] ARM: dts: aspeed: Harma: Add NIC Fru device Peter Yin
2024-02-27 1:47 ` [PATCH v4 09/10] ARM: dts: aspeed: Harma: Add ltc4286 device Peter Yin
2024-02-27 1:47 ` [PATCH v4 10/10] ARM: dts: aspeed: Harma: Revise node name Peter Yin
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=20240227014719.3037588-1-peteryin.openbmc@gmail.com \
--to=peteryin.openbmc@gmail.com \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--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=patrick@stwcx.xyz \
--cc=robh+dt@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).