From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Yang Chen <yangchen.openbmc@gmail.com>,
joel@jms.id.au, patrick@stwcx.xyz, amithash@meta.com,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Jerry.Lin@quantatw.com, yang.chen@quantatw.com
Subject: Re: [PATCH v1 1/1] ARM: dts: aspeed: minerva: add host0-ready pin
Date: Fri, 26 Jul 2024 15:30:43 +0930 [thread overview]
Message-ID: <a4c2a2c25c7582b7b45fc42662b60c589b4748d4.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240711130501.2900301-2-yangchen.openbmc@gmail.com>
On Thu, 2024-07-11 at 21:05 +0800, Yang Chen wrote:
> Add host0-ready pin for phosphor-state-manager.
>
> Signed-off-by: Yang Chen <yangchen.openbmc@gmail.com>
> ---
> arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts
> index f5ac248097b4..41e2246cfbd1 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts
> @@ -613,7 +613,7 @@ &gpio0 {
> /*P0-P7*/ "","","","","","","","",
> /*Q0-Q7*/ "","","","","","power-chassis-control","","",
> /*R0-R7*/ "","","","","","","","",
> - /*S0-S7*/ "","","","","","","","",
> + /*S0-S7*/ "","","","","","","","host0-ready",
> /*T0-T7*/ "","","","","","","","",
> /*U0-U7*/ "","","","","","","","",
> /*V0-V7*/ "","","","","BAT_DETECT","","power-chassis-good","",
Thanks, I've applied this to a tree for Joel to pick up.
Andrew
prev parent reply other threads:[~2024-07-26 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 13:05 [PATCH v1 0/1] Add gpio line name in Meta Minerva BMC(AST2600) Yang Chen
2024-07-11 13:05 ` [PATCH v1 1/1] ARM: dts: aspeed: minerva: add host0-ready pin Yang Chen
2024-07-26 6:00 ` Andrew Jeffery [this message]
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=a4c2a2c25c7582b7b45fc42662b60c589b4748d4.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Jerry.Lin@quantatw.com \
--cc=amithash@meta.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=yang.chen@quantatw.com \
--cc=yangchen.openbmc@gmail.com \
/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®