From: Liam Beguin <liambeguin@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
devicetree@vger.kernel.org, Liam Beguin <liambeguin@gmail.com>
Subject: [PATCH 2/2] dt-bindings: gpio: pca95xx: document new tca9538 chip
Date: Thu, 24 Aug 2023 19:16:26 -0400 [thread overview]
Message-ID: <20230824-tca9538-v1-2-ee3bf2065065@gmail.com> (raw)
In-Reply-To: <20230824-tca9538-v1-0-ee3bf2065065@gmail.com>
The previous patch added support for this chip. Add its name to the list
of allowed compatibles.
Signed-off-by: Liam Beguin <liambeguin@gmail.com>
---
Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml b/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
index fa116148ee90..99febb8ea1b6 100644
--- a/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
+++ b/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
@@ -66,6 +66,7 @@ properties:
- ti,tca6408
- ti,tca6416
- ti,tca6424
+ - ti,tca9538
- ti,tca9539
- ti,tca9554
--
2.39.0
next prev parent reply other threads:[~2023-08-24 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 23:16 [PATCH 0/2] gpio: pca953x: add support for TCA9538 Liam Beguin
2023-08-24 23:16 ` [PATCH 1/2] " Liam Beguin
2023-08-25 1:59 ` Andy Shevchenko
2023-08-25 11:18 ` Bartosz Golaszewski
2023-08-24 23:16 ` Liam Beguin [this message]
2023-08-25 6:21 ` [PATCH 2/2] dt-bindings: gpio: pca95xx: document new tca9538 chip Krzysztof Kozlowski
2023-08-25 11:17 ` Bartosz Golaszewski
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=20230824-tca9538-v1-2-ee3bf2065065@gmail.com \
--to=liambeguin@gmail.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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).