From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio <linux-gpio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v3 2/2] gpio: pca953x: Add support for the PCAL9535
Date: Tue, 16 Jun 2020 10:50:18 +0200 [thread overview]
Message-ID: <CAMpxmJWF8uKf2iGP3cF2mOC7nozFD-hZh0wE9VFAqP+P-zAC9g@mail.gmail.com> (raw)
In-Reply-To: <eecfadcb92f9f9c1446b4824471e9d7f45a9d8aa.1592227348.git.jan.kiszka@siemens.com>
pon., 15 cze 2020 o 15:22 Jan Kiszka <jan.kiszka@siemens.com> napisał(a):
>
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> The PCAL9535 is compatible to the PCA9535. Additionally, it comes with
> interrupt support and input latching. Other features are not supported
> by the GPIO subsystem.
>
> Datasheet: https://www.nxp.com/docs/en/data-sheet/PCAL9535A.pdf
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> drivers/gpio/gpio-pca953x.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c
> index 1fca8dd7824f..cd5fb522563e 100644
> --- a/drivers/gpio/gpio-pca953x.c
> +++ b/drivers/gpio/gpio-pca953x.c
> @@ -89,6 +89,7 @@ static const struct i2c_device_id pca953x_id[] = {
>
> { "pcal6416", 16 | PCA953X_TYPE | PCA_LATCH_INT, },
> { "pcal6524", 24 | PCA953X_TYPE | PCA_LATCH_INT, },
> + { "pcal9535", 16 | PCA953X_TYPE | PCA_LATCH_INT, },
> { "pcal9555a", 16 | PCA953X_TYPE | PCA_LATCH_INT, },
>
> { "max7310", 8 | PCA953X_TYPE, },
> @@ -1145,6 +1146,7 @@ static const struct of_device_id pca953x_dt_ids[] = {
>
> { .compatible = "nxp,pcal6416", .data = OF_953X(16, PCA_LATCH_INT), },
> { .compatible = "nxp,pcal6524", .data = OF_953X(24, PCA_LATCH_INT), },
> + { .compatible = "nxp,pcal9535", .data = OF_953X(16, PCA_LATCH_INT), },
> { .compatible = "nxp,pcal9555a", .data = OF_953X(16, PCA_LATCH_INT), },
>
> { .compatible = "maxim,max7310", .data = OF_953X( 8, 0), },
> --
> 2.26.2
>
Patch applied with Andy's review tag.
Bart
next prev parent reply other threads:[~2020-06-16 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 13:22 [PATCH v3 0/2] gpio: Add support for the PCAL9535 Jan Kiszka
2020-06-15 13:22 ` [PATCH v3 1/2] dt-bindings: gpio: pca953x: add nxp,pcal9535 Jan Kiszka
2020-06-16 8:50 ` Bartosz Golaszewski
2020-06-15 13:22 ` [PATCH v3 2/2] gpio: pca953x: Add support for the PCAL9535 Jan Kiszka
2020-06-16 8:50 ` Bartosz Golaszewski [this message]
2020-06-15 13:39 ` [PATCH v3 0/2] gpio: " Andy Shevchenko
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=CAMpxmJWF8uKf2iGP3cF2mOC7nozFD-hZh0wE9VFAqP+P-zAC9g@mail.gmail.com \
--to=bgolaszewski@baylibre.com \
--cc=andy.shevchenko@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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).