From: Andrew Geissler <geissonator@gmail.com>
To: joel@jms.id.au, andrew@aj.id.au, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Andrew Geissler <geissonator@yahoo.com>,
linux-gpio@vger.kernel.org, openbmc@lists.ozlabs.org
Subject: [PATCH 1/2] ARM: dts: aspeed: rainier: add reset-cause-pinhole
Date: Thu, 13 Jan 2022 15:17:34 -0600 [thread overview]
Message-ID: <20220113211735.37861-1-geissonator@yahoo.com> (raw)
This GPIO is used on the rainier system to indicate the BMC was reset
due to a physical pinhole reset.
See the following doc for more information:
https://github.com/openbmc/docs/blob/master/designs/device-tree-gpio-naming.md
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
---
arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts b/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts
index cfaa606666e2..7ea70c7d698f 100644
--- a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts
@@ -247,7 +247,8 @@ &gpio0 {
/*C0-C7*/ "","","","","","","","",
/*D0-D7*/ "","","","","","","","",
/*E0-E7*/ "","","","","","","","",
- /*F0-F7*/ "","","battery-voltage-read-enable","","","","factory-reset-toggle","",
+ /*F0-F7*/ "","","battery-voltage-read-enable","reset-cause-pinhole","","",
+ "factory-reset-toggle","",
/*G0-G7*/ "","","","","","","","",
/*H0-H7*/ "","bmc-ingraham0","rear-enc-id0","rear-enc-fault0","","","","",
/*I0-I7*/ "","","","","","","bmc-secure-boot","",
--
2.25.1
next reply other threads:[~2022-01-13 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 21:17 Andrew Geissler [this message]
2022-01-13 21:17 ` [PATCH 2/2] ARM: dts: aspeed: everest: " Andrew Geissler
2022-01-13 22:35 ` [PATCH 1/2] ARM: dts: aspeed: rainier: " Joel Stanley
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=20220113211735.37861-1-geissonator@yahoo.com \
--to=geissonator@gmail.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=geissonator@yahoo.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.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
Powered by JetHome