From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Tony Lindgren <tony@atomide.com>, <devicetree@vger.kernel.org>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>,
Aswath Govindraju <a-govindraju@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [PATCH v2 4/5] ARM: dts: omap5-board-common: align gpio hog names with dt-schema
Date: Tue, 25 May 2021 20:58:57 +0300 [thread overview]
Message-ID: <20210525175858.11611-5-grygorii.strashko@ti.com> (raw)
In-Reply-To: <20210525175858.11611-1-grygorii.strashko@ti.com>
The GPIO Hog dt-schema node naming convention expect GPIO hogs node names
to end with a 'hog' suffix.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
---
arch/arm/boot/dts/omap5-board-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap5-board-common.dtsi b/arch/arm/boot/dts/omap5-board-common.dtsi
index d8f13626cfd1..45435bb88c89 100644
--- a/arch/arm/boot/dts/omap5-board-common.dtsi
+++ b/arch/arm/boot/dts/omap5-board-common.dtsi
@@ -149,7 +149,7 @@
&gpio8 {
/* TI trees use GPIO instead of msecure, see also muxing */
- p234 {
+ msecure-hog {
gpio-hog;
gpios = <10 GPIO_ACTIVE_HIGH>;
output-high;
--
2.17.1
next prev parent reply other threads:[~2021-05-25 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 17:58 [PATCH v2 0/5] dt-bindings: gpio: omap: Convert to json-schema Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 1/5] ARM: dts: am335x: align GPIO hog names with dt-schema Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 2/5] ARM: dts: am437x: align gpio " Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 3/5] ARM: dts: omap3: " Grygorii Strashko
2021-05-25 17:58 ` Grygorii Strashko [this message]
2021-05-25 17:58 ` [PATCH v2 5/5] dt-bindings: gpio: omap: Convert to json-schema Grygorii Strashko
2021-05-26 11:28 ` Bartosz Golaszewski
2021-05-26 10:06 ` [PATCH v2 0/5] " Grygorii Strashko
2021-05-27 12:01 ` Tony Lindgren
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=20210525175858.11611-5-grygorii.strashko@ti.com \
--to=grygorii.strashko@ti.com \
--cc=a-govindraju@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.