devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: Ninad Palsule <ninad@linux.ibm.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	joel@jms.id.au, andrew@codeconstruct.com.au
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/3] ARM: dts: aspeed: system1: Add GPIO line names
Date: Tue, 1 Oct 2024 15:50:01 -0500	[thread overview]
Message-ID: <a795fef5-b2c4-4201-b481-86d97d60c81e@linux.ibm.com> (raw)
In-Reply-To: <20241001191756.234096-4-ninad@linux.ibm.com>


On 10/1/24 14:17, Ninad Palsule wrote:
> Add following GPIO line names so that userspace can control them
> - PCH related GPIOs
> - FPGA related GPIOs


Reviewed-by: Eddie James <eajames@linux.ibm.com>


>
> Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
> ---
>   arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
> index c0219167a337a..35cb9fea308e8 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
> @@ -370,17 +370,17 @@ &gpio0 {
>   	/*K0-K7*/	"","","","","","","","",
>   	/*L0-L7*/	"","","","","","","","bmc-ready",
>   	/*M0-M7*/	"","","","","","","","",
> -	/*N0-N7*/	"","","","","","","","",
> +	/*N0-N7*/	"fpga-debug-enable","","","","","","","",
>   	/*O0-O7*/	"","","","","","","","",
>   	/*P0-P7*/	"","","","","","","","bmc-hb",
> -	/*Q0-Q7*/	"","","","","","","","",
> +	/*Q0-Q7*/	"","","","","","","pch-ready","",
>   	/*R0-R7*/	"","","","","","","","",
>   	/*S0-S7*/	"","","","","","","rear-enc-fault0","rear-enc-id0",
>   	/*T0-T7*/	"","","","","","","","",
>   	/*U0-U7*/	"","","","","","","","",
>   	/*V0-V7*/	"","rtc-battery-voltage-read-enable","","power-chassis-control","","","","",
>   	/*W0-W7*/	"","","","","","","","",
> -	/*X0-X7*/	"","power-chassis-good","","","","","","",
> +	/*X0-X7*/	"fpga-pgood","power-chassis-good","pch-pgood","","","","","",
>   	/*Y0-Y7*/	"","","","","","","","",
>   	/*Z0-Z7*/	"","","","","","","","";
>   };

  reply	other threads:[~2024-10-01 20:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 19:17 [PATCH v1 0/3] Device tree changes for system1 BMC Ninad Palsule
2024-10-01 19:17 ` [PATCH v1 1/3] ARM: dts: aspeed: system1: Bump up i2c busses freq Ninad Palsule
2024-10-01 20:48   ` Eddie James
2024-10-01 19:17 ` [PATCH v1 2/3] ARM: dts: aspeed: system1: Enable serial gpio0 Ninad Palsule
2024-10-01 20:49   ` Eddie James
2024-10-01 19:17 ` [PATCH v1 3/3] ARM: dts: aspeed: system1: Add GPIO line names Ninad Palsule
2024-10-01 20:50   ` Eddie James [this message]
2024-10-02  0:26 ` [PATCH v1 0/3] Device tree changes for system1 BMC Andrew Jeffery
2024-10-02  3:12   ` Ninad Palsule

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=a795fef5-b2c4-4201-b481-86d97d60c81e@linux.ibm.com \
    --to=eajames@linux.ibm.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --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=ninad@linux.ibm.com \
    --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).