From: PeterYin <peteryin.openbmc@gmail.com>
To: 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@codeconstruct.com.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Revise Meta(Facebook) Harma BMC(AST2600)
Date: Thu, 21 Nov 2024 12:33:50 +0800 [thread overview]
Message-ID: <b13e5063-3b07-43ec-a7cc-b19e73b7c9e0@gmail.com> (raw)
In-Reply-To: <20241121025323.1403409-1-peteryin.openbmc@gmail.com>
Hi Andrew,
I believe this series' path will conflict with upstream due to
version differences between OpenBMC and upstream. I will update to the
latest version of the DTS from upstream and submit a new version
accordingly.
Thanks,
Peter.
Peter Yin 於 11/21/24 10:53 寫道:
> Summary:
> Revise linux device tree entry related to Meta(Facebook) Harma
> specific devices connected to BMC(AST2600) SoC.
>
> Base on:
> https://github.com/openbmc/linux/blob/dev-6.6/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
>
> Base on:
> https://lore.kernel.org/all/14e1a0f581417d4228aea8c2569598d42b4bd334.camel@codeconstruct.com.au/
>
> v1->v2
> - Provide additional details for SGPIO.
> - Add adc128d818 device
>
> v1
> - Patch 0001 - Harma: Revise node name
> - Patch 0002 - Harma: Add retimer device
> - Patch 0003 - Harma: Revise GPIO line name
> - Patch 0004 - Harma: add e1s power monitor
> - Patch 0005 - Harma: fan board io-expande
> - Patch 0006 - Harma: add adc128d818
>
> Peter Yin (6):
> ARM: dts: aspeed: Harma: Revise node name
> ARM: dts: aspeed: Harma: Add retimer device
> ARM: dts: aspeed: Harma: Revise GPIO line name
> ARM: dts: aspeed: Harma: add e1s power monitor
> ARM: dts: aspeed: Harma: fan board io-expander
> ARM: dts: aspeed: Harma: add adc128d818
>
> .../dts/aspeed/aspeed-bmc-facebook-harma.dts | 134 ++++++++++++++----
> 1 file changed, 110 insertions(+), 24 deletions(-)
>
next prev parent reply other threads:[~2024-11-21 4:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 2:53 Peter Yin
2024-11-21 2:53 ` [PATCH v2 1/6] ARM: dts: aspeed: Harma: Revise node name Peter Yin
2024-11-21 2:53 ` [PATCH v2 2/6] ARM: dts: aspeed: Harma: Add retimer device Peter Yin
2024-11-21 2:53 ` [PATCH v2 3/6] ARM: dts: aspeed: Harma: Revise GPIO line name Peter Yin
2024-11-21 2:53 ` [PATCH v2 4/6] ARM: dts: aspeed: Harma: add e1s power monitor Peter Yin
2024-11-21 2:53 ` [PATCH v2 5/6] ARM: dts: aspeed: Harma: fan board io-expander Peter Yin
2024-11-21 2:53 ` [PATCH v2 6/6] ARM: dts: aspeed: Harma: add adc128d818 Peter Yin
2024-11-21 4:33 ` PeterYin [this message]
2024-11-22 0:57 ` [PATCH v2 0/6] Revise Meta(Facebook) Harma BMC(AST2600) Andrew Jeffery
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 13:45 Peter Yin
2024-01-04 14:28 ` Patrick Williams
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=b13e5063-3b07-43ec-a7cc-b19e73b7c9e0@gmail.com \
--to=peteryin.openbmc@gmail.com \
--cc=andrew@codeconstruct.com.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=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
all inboxes | Powered by JetHome®