From: Trevor Woerner <twoerner@gmail.com>
To: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v3 1/2] dt-bindings: gpio: nxp,pcf8575: add gpio-line-names
Date: Thu, 9 Feb 2023 21:51:31 -0500 [thread overview]
Message-ID: <20230210025132.36605-1-twoerner@gmail.com> (raw)
In-Reply-To: <59efb87b-5f97-a409-46ae-095ab03d01b9@linaro.org>
The devices described in this binding represent 8-bit and 16-bit i2c i/o
expanders. Allow the user to specify names for up to 16 gpio lines.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
changes since v2:
- expand maxItems to 16 to accommodate that some of the io expanders
covered in this schema are 16-bit (e.g. PCA9675)
changes since v1:
- the original said [PATCH 1/2], there is no 2/2
(or at least there wasn't back then)
---
Documentation/devicetree/bindings/gpio/nxp,pcf8575.yaml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/gpio/nxp,pcf8575.yaml b/Documentation/devicetree/bindings/gpio/nxp,pcf8575.yaml
index f0ff66c4c74e..3718103e966a 100644
--- a/Documentation/devicetree/bindings/gpio/nxp,pcf8575.yaml
+++ b/Documentation/devicetree/bindings/gpio/nxp,pcf8575.yaml
@@ -39,6 +39,10 @@ properties:
reg:
maxItems: 1
+ gpio-line-names:
+ minItems: 1
+ maxItems: 16
+
gpio-controller: true
'#gpio-cells':
--
2.36.0.rc2.17.g4027e30c53
next prev parent reply other threads:[~2023-02-10 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 4:17 [PATCH 1/2] dt-bindings: gpio: nxp,pcf8575: add gpio-line-names Trevor Woerner
2023-02-09 4:31 ` [PATCH v2] " Trevor Woerner
2023-02-09 8:29 ` Krzysztof Kozlowski
2023-02-10 2:51 ` Trevor Woerner [this message]
2023-02-10 11:49 ` [PATCH v3 1/2] " Krzysztof Kozlowski
2023-02-27 21:37 ` Linus Walleij
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=20230210025132.36605-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).