From: Quan Nguyen <quan@os.amperecomputing.com>
To: Joel Stanley <joel@jms.id.au>
Cc: linux-aspeed@lists.ozlabs.org,
Phong Vo <phong@os.amperecomputing.com>,
Open Source Submission <patches@amperecomputing.com>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andrew Jeffery <andrew@aj.id.au>,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Thang Nguyen <thang@os.amperecomputing.com>,
devicetree@vger.kernel.org, openbmc@lists.ozlabs.org
Subject: Re: [PATCH] ARM: dts: aspeed: mtjade: Remove gpio-keys entries
Date: Wed, 28 Sep 2022 10:30:06 +0700 [thread overview]
Message-ID: <6ec59a82-8d48-2b72-867b-ba465f655810@os.amperecomputing.com> (raw)
In-Reply-To: <20220915080828.2894070-1-quan@os.amperecomputing.com>
Thanks Joel,
Would you mind picking the patch to openbmc dev-5.15 branch ?
Thank you,
- Quan
On 15/09/2022 15:08, Quan Nguyen wrote:
> Remove the gpio-keys entries from the Ampere's Mt. Jade BMC device
> tree. The user space applications are going to change from using
> libevdev to libgpiod.
>
> Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
> ---
> .../arm/boot/dts/aspeed-bmc-ampere-mtjade.dts | 95 -------------------
> 1 file changed, 95 deletions(-)
>
> diff --git a/arch/arm/boot/dts/aspeed-bmc-ampere-mtjade.dts b/arch/arm/boot/dts/aspeed-bmc-ampere-mtjade.dts
> index 82a6f14a45f0..d127cbcc7998 100644
> --- a/arch/arm/boot/dts/aspeed-bmc-ampere-mtjade.dts
> +++ b/arch/arm/boot/dts/aspeed-bmc-ampere-mtjade.dts
> @@ -97,101 +97,6 @@ identify {
> };
> };
>
> - gpio-keys {
> - compatible = "gpio-keys";
> -
> - event-shutdown-ack {
> - label = "SHUTDOWN_ACK";
> - gpios = <&gpio ASPEED_GPIO(G, 2) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(G, 2)>;
> - };
> -
> - event-reboot-ack {
> - label = "REBOOT_ACK";
> - gpios = <&gpio ASPEED_GPIO(J, 3) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(J, 3)>;
> - };
> -
> - event-s0-overtemp {
> - label = "S0_OVERTEMP";
> - gpios = <&gpio ASPEED_GPIO(G, 3) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(G, 3)>;
> - };
> -
> - event-s0-hightemp {
> - label = "S0_HIGHTEMP";
> - gpios = <&gpio ASPEED_GPIO(J, 0) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(J, 0)>;
> - };
> -
> - event-s0-cpu-fault {
> - label = "S0_CPU_FAULT";
> - gpios = <&gpio ASPEED_GPIO(J, 1) GPIO_ACTIVE_HIGH>;
> - linux,code = <ASPEED_GPIO(J, 1)>;
> - };
> -
> - event-s0-scp-auth-fail {
> - label = "S0_SCP_AUTH_FAIL";
> - gpios = <&gpio ASPEED_GPIO(J, 2) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(J, 2)>;
> - };
> -
> - event-s1-scp-auth-fail {
> - label = "S1_SCP_AUTH_FAIL";
> - gpios = <&gpio ASPEED_GPIO(Z, 5) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(Z, 5)>;
> - };
> -
> - event-s1-overtemp {
> - label = "S1_OVERTEMP";
> - gpios = <&gpio ASPEED_GPIO(Z, 6) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(Z, 6)>;
> - };
> -
> - event-s1-hightemp {
> - label = "S1_HIGHTEMP";
> - gpios = <&gpio ASPEED_GPIO(AB, 0) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(AB, 0)>;
> - };
> -
> - event-s1-cpu-fault {
> - label = "S1_CPU_FAULT";
> - gpios = <&gpio ASPEED_GPIO(Z, 1) GPIO_ACTIVE_HIGH>;
> - linux,code = <ASPEED_GPIO(Z, 1)>;
> - };
> -
> - event-id {
> - label = "ID_BUTTON";
> - gpios = <&gpio ASPEED_GPIO(Q, 5) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(Q, 5)>;
> - };
> -
> - event-psu1-vin-good {
> - label = "PSU1_VIN_GOOD";
> - gpios = <&gpio ASPEED_GPIO(H, 4) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(H, 4)>;
> - };
> -
> - event-psu2-vin-good {
> - label = "PSU2_VIN_GOOD";
> - gpios = <&gpio ASPEED_GPIO(H, 5) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(H, 5)>;
> - };
> -
> - event-psu1-present {
> - label = "PSU1_PRESENT";
> - gpios = <&gpio ASPEED_GPIO(I, 0) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(I, 0)>;
> - };
> -
> - event-psu2-present {
> - label = "PSU2_PRESENT";
> - gpios = <&gpio ASPEED_GPIO(I, 1) GPIO_ACTIVE_LOW>;
> - linux,code = <ASPEED_GPIO(I, 1)>;
> - };
> -
> - };
> -
> gpioA0mux: mux-controller {
> compatible = "gpio-mux";
> #mux-control-cells = <0>;
prev parent reply other threads:[~2022-09-28 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 8:08 Quan Nguyen
2022-09-26 8:02 ` Quan Nguyen
2022-09-28 3:30 ` Quan Nguyen [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=6ec59a82-8d48-2b72-867b-ba465f655810@os.amperecomputing.com \
--to=quan@os.amperecomputing.com \
--cc=andrew@aj.id.au \
--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=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=robh+dt@kernel.org \
--cc=thang@os.amperecomputing.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®