From: Chanh Nguyen <chanh@os.amperecomputing.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Chanh Nguyen <chanh@os.amperecomputing.com>
Subject: [PATCH 3/7] ARM: dts: aspeed: mtjade: Add the gpio-hog
Date: Thu, 5 Oct 2023 10:55:21 +0700 [thread overview]
Message-ID: <20231005035525.19036-4-chanh@os.amperecomputing.com> (raw)
In-Reply-To: <20231005035525.19036-1-chanh@os.amperecomputing.com>
Add the GPIOR5 as a gpio-hog with output high so that can
power the OCP card once the BMC booting.
Add the GPIOAC5 as a gpio-hog with output high to notice
the BMC state.
Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
---
.../boot/dts/aspeed/aspeed-bmc-ampere-mtjade.dts | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-ampere-mtjade.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-ampere-mtjade.dts
index c87be433bdd0..8ab5f301f926 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ampere-mtjade.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ampere-mtjade.dts
@@ -805,4 +805,18 @@
output-high;
line-name = "i2c4-o-en";
};
+
+ ocp-aux-pwren-hog {
+ gpio-hog;
+ gpios = <ASPEED_GPIO(R, 3) GPIO_ACTIVE_HIGH>;
+ output-high;
+ line-name = "ocp-aux-pwren";
+ };
+
+ bmc-ready {
+ gpio-hog;
+ gpios = <ASPEED_GPIO(AC, 5) GPIO_ACTIVE_HIGH>;
+ output-high;
+ line-name = "bmc-ready";
+ };
};
--
2.17.1
next prev parent reply other threads:[~2023-10-05 3:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 3:55 [PATCH 0/7] Update the device tree for Ampere's BMC platform Chanh Nguyen
2023-10-05 3:55 ` [PATCH 1/7] ARM: dts: aspeed: mtjade, mtmitchell: Update gpio-line-names Chanh Nguyen
2023-10-11 1:48 ` Joel Stanley
2023-10-05 3:55 ` [PATCH 2/7] ARM: dts: aspeed: mtjade, mtmitchell: Add new gpio-line-names Chanh Nguyen
2023-10-11 1:48 ` Joel Stanley
2023-10-05 3:55 ` Chanh Nguyen [this message]
2023-10-11 1:49 ` [PATCH 3/7] ARM: dts: aspeed: mtjade: Add the gpio-hog Joel Stanley
2023-10-05 3:55 ` [PATCH 4/7] ARM: dts: aspeed: mtmitchell: Add LEDs Chanh Nguyen
2023-10-05 7:31 ` Krzysztof Kozlowski
2023-10-10 3:28 ` Chanh Nguyen
2023-10-05 3:55 ` [PATCH 5/7] ARM: dts: aspeed: mtmitchell: Add inlet temperature sensor Chanh Nguyen
2023-10-11 1:51 ` Joel Stanley
2023-10-05 3:55 ` [PATCH 6/7] ARM: dts: aspeed: mtmitchell: Remove redundant ADC configurations Chanh Nguyen
2023-10-11 1:51 ` Joel Stanley
2023-10-05 3:55 ` [PATCH 7/7] ARM: dts: aspeed: mtmitchell: Add I2C NVMe alias port Chanh Nguyen
2023-10-11 1:52 ` Joel Stanley
2023-10-11 8:31 ` [PATCH 0/7] Update the device tree for Ampere's BMC platform Joel Stanley
2023-10-11 11:27 ` Chanh Nguyen
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=20231005035525.19036-4-chanh@os.amperecomputing.com \
--to=chanh@os.amperecomputing.com \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--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=robh+dt@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).