From: Ninad Palsule <ninad@linux.ibm.com>
To: minyard@acm.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
ratbert@faraday-tech.com,
openipmi-developer@lists.sourceforge.net, netdev@vger.kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, eajames@linux.ibm.com,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Ninad Palsule <ninad@linux.ibm.com>
Subject: [PATCH v3 09/10] ARM: dts: aspeed: system1: Mark GPIO line high/low
Date: Wed, 8 Jan 2025 10:36:37 -0600 [thread overview]
Message-ID: <20250108163640.1374680-10-ninad@linux.ibm.com> (raw)
In-Reply-To: <20250108163640.1374680-1-ninad@linux.ibm.com>
- Mark following GPIO lines as input high:
- GPIOL4 (reset PCH registers)
- GPIOL5 (reset portition of intel ME)
- Mark isolate errors from cpu1 gpio (GPIOO6) as active low output.
- The fan controller reset line should be active high.
Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
---
.../dts/aspeed/aspeed-bmc-ibm-system1.dts | 28 +++++++++++++++++++
1 file changed, 28 insertions(+)
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 90570b4d6d35..8026c67ecaee 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
@@ -383,6 +383,34 @@ &gpio0 {
/*X0-X7*/ "fpga-pgood","power-chassis-good","pch-pgood","","","","","",
/*Y0-Y7*/ "","","","","","","","",
/*Z0-Z7*/ "","","","","","","","";
+
+ hog-0 {
+ gpio-hog;
+ gpios = <ASPEED_GPIO(L, 4) GPIO_ACTIVE_HIGH>;
+ input;
+ line-name = "RST_RTCRST_N";
+ };
+
+ hog-1 {
+ gpio-hog;
+ gpios = <ASPEED_GPIO(L, 5) GPIO_ACTIVE_HIGH>;
+ input;
+ line-name = "RST_SRTCRST_N";
+ };
+
+ hog-2 {
+ gpio-hog;
+ gpios = <ASPEED_GPIO(L, 6) GPIO_ACTIVE_HIGH>;
+ output-high;
+ line-name = "BMC_FAN_E3_SVC_PEX_INT_N";
+ };
+
+ hog-3 {
+ gpio-hog;
+ gpios = <ASPEED_GPIO(O, 6) GPIO_ACTIVE_LOW>;
+ output-low;
+ line-name = "isolate_errs_cpu1";
+ };
};
&emmc_controller {
--
2.43.0
next prev parent reply other threads:[~2025-01-08 16:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 16:36 [PATCH v3 00/10] DTS updates for system1 BMC Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 01/10] dt-bindings: net: faraday,ftgmac100: Add phys mode Ninad Palsule
2025-01-10 16:02 ` Rob Herring (Arm)
2025-01-13 19:49 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 02/10] bindings: ipmi: Add binding for IPMB device intf Ninad Palsule
2025-01-10 16:07 ` Rob Herring
2025-01-10 17:53 ` Corey Minyard
2025-01-13 19:50 ` Ninad Palsule
2025-01-14 14:21 ` Ninad Palsule
2025-01-13 19:49 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 03/10] ARM: dts: aspeed: system1: Add IPMB device Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 04/10] ARM: dts: aspeed: system1: Add GPIO line name Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 05/10] ARM: dts: aspeed: system1: Add RGMII support Ninad Palsule
2025-01-08 17:03 ` Andrew Lunn
2025-01-08 18:43 ` Ninad Palsule
2025-01-08 20:13 ` Andrew Lunn
2025-01-08 20:42 ` Ninad Palsule
2025-01-13 19:51 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 06/10] ARM: dts: aspeed: system1: Reduce sgpio speed Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 07/10] ARM: dts: aspeed: system1: Update LED gpio name Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 08/10] ARM: dts: aspeed: system1: Remove VRs max8952 Ninad Palsule
2025-01-08 16:36 ` Ninad Palsule [this message]
2025-01-08 16:36 ` [PATCH v3 10/10] ARM: dts: aspeed: system1: Disable gpio pull down Ninad Palsule
2025-01-08 22:34 ` [PATCH v3 00/10] DTS updates for system1 BMC Rob Herring (Arm)
2025-01-13 19:52 ` Ninad Palsule
2025-01-14 0:07 ` Rob Herring
2025-01-14 22:09 ` 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=20250108163640.1374680-10-ninad@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=edumazet@google.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pabeni@redhat.com \
--cc=ratbert@faraday-tech.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).