From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: kernel@collabora.com,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Sean Wang" <sean.wang@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH v1 4/4] dt-bindings: pinctrl: mt8192: Add gpio-line-names property
Date: Tue, 15 Mar 2022 17:19:36 -0400 [thread overview]
Message-ID: <20220315211936.442708-5-nfraprado@collabora.com> (raw)
In-Reply-To: <20220315211936.442708-1-nfraprado@collabora.com>
Add the gpio-line-names optional property to the pinctrl-mt8192 binding
to prevent dt_binding_check warnings when it is present in the pinctrl
node in the Devicetree.
Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
---
Documentation/devicetree/bindings/pinctrl/pinctrl-mt8192.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8192.yaml b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8192.yaml
index e27cbcc6e8f9..c90a132fbc79 100644
--- a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8192.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8192.yaml
@@ -29,6 +29,8 @@ properties:
description: gpio valid number range.
maxItems: 1
+ gpio-line-names: true
+
reg:
description: |
Physical address base for gpio base registers. There are 11 GPIO
--
2.35.1
next prev parent reply other threads:[~2022-03-15 21:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 21:19 [PATCH v1 0/4] dt-bindings: pinctrl: mt8192: Add missing wrapping node and properties Nícolas F. R. A. Prado
2022-03-15 21:19 ` [PATCH v1 1/4] dt-bindings: pinctrl: mt8192: Add wrapping node for pin configurations Nícolas F. R. A. Prado
2022-03-16 8:39 ` AngeloGioacchino Del Regno
2022-03-23 18:51 ` Rob Herring
2022-04-19 21:12 ` Linus Walleij
2022-03-15 21:19 ` [PATCH v1 2/4] dt-bindings: pinctrl: mt8192: Add mediatek,drive-strength-adv property Nícolas F. R. A. Prado
2022-03-16 8:39 ` AngeloGioacchino Del Regno
2022-03-23 18:53 ` Rob Herring
2022-04-19 21:13 ` Linus Walleij
2022-03-15 21:19 ` [PATCH v1 3/4] dt-bindings: pinctrl: mt8192: Add mediatek,pull-up-adv property Nícolas F. R. A. Prado
2022-03-16 8:39 ` AngeloGioacchino Del Regno
2022-03-23 18:53 ` Rob Herring
2022-04-19 21:14 ` Linus Walleij
2022-03-15 21:19 ` Nícolas F. R. A. Prado [this message]
2022-03-16 8:39 ` [PATCH v1 4/4] dt-bindings: pinctrl: mt8192: Add gpio-line-names property AngeloGioacchino Del Regno
2022-03-23 18:54 ` Rob Herring
2022-04-19 21:15 ` Linus Walleij
2022-03-16 8:49 ` [PATCH v1 0/4] dt-bindings: pinctrl: mt8192: Add missing wrapping node and properties AngeloGioacchino Del Regno
2022-04-04 16:02 ` Nícolas F. R. A. Prado
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=20220315211936.442708-5-nfraprado@collabora.com \
--to=nfraprado@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®