From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: kimi.zy.chen@fii-foxconn.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
george.kw.lee@fii-foxconn.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH v2] ARM: dts: aspeed: clemente: add gpio line name to io expander
Date: Fri, 14 Nov 2025 14:40:44 +1030 [thread overview]
Message-ID: <580b0c6d979a69ea0c4590b5d9ba035b417effb8.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20251107-dts-add-gpio-to-io-expander-v2-1-585d48845546@fii-foxconn.com>
On Fri, 2025-11-07 at 00:58 +0800, Kimi Chen via B4 Relay wrote:
> From: Kimi Chen <kimi.zy.chen@fii-foxconn.com>
>
> The chassis power cycle process requires a forced shutdown before
> cutting off the standby power. Therefore, SCM CPLD adds a hard shutdown
> host function and triggers it via the IO expander in Clemente platform.
>
> Thus, a new GPIO line named "hard_shutdown_host" is added to the
Most of the Clemente GPIOs names appear to be styled as net names from
the schematics. Is that the source of this name as well? Or have you
somewhat arbitrarily chosen it? Can you expand on its importance (e.g.
wrt userspace software)?
Andrew
prev parent reply other threads:[~2025-11-14 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 16:58 [PATCH v2] ARM: dts: aspeed: clemente: add gpio line name to io expander Kimi Chen via B4 Relay
2025-11-14 4:10 ` 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=580b0c6d979a69ea0c4590b5d9ba035b417effb8.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.kw.lee@fii-foxconn.com \
--cc=joel@jms.id.au \
--cc=kimi.zy.chen@fii-foxconn.com \
--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).