From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: <bgolaszewski@baylibre.com>
Cc: <linus.walleij@linaro.org>, <linux-gpio@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: [PATCH 4/4] gpio: madera: Add support for Cirrus Logic CS47L92
Date: Mon, 22 Jul 2019 10:07:48 +0100 [thread overview]
Message-ID: <20190722090748.20807-4-ckeepax@opensource.cirrus.com> (raw)
In-Reply-To: <20190722090748.20807-1-ckeepax@opensource.cirrus.com>
As the gpio is common to all madera codecs all that is needed
is to setup the correct number of GPIO pins for the CS47L92.
Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
---
drivers/gpio/gpio-madera.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/gpio/gpio-madera.c b/drivers/gpio/gpio-madera.c
index c403899ff4500..7086f8b5388fd 100644
--- a/drivers/gpio/gpio-madera.c
+++ b/drivers/gpio/gpio-madera.c
@@ -150,6 +150,11 @@ static int madera_gpio_probe(struct platform_device *pdev)
case CS47L91:
madera_gpio->gpio_chip.ngpio = CS47L90_NUM_GPIOS;
break;
+ case CS42L92:
+ case CS47L92:
+ case CS47L93:
+ madera_gpio->gpio_chip.ngpio = CS47L92_NUM_GPIOS;
+ break;
default:
dev_err(&pdev->dev, "Unknown chip variant %d\n", madera->type);
return -EINVAL;
--
2.11.0
next prev parent reply other threads:[~2019-07-22 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 9:07 [PATCH 1/4] gpio: arizona: Use local copy of pdata Charles Keepax
2019-07-22 9:07 ` [PATCH 2/4] gpio: madera: " Charles Keepax
2019-08-05 9:43 ` Linus Walleij
2019-07-22 9:07 ` [PATCH 3/4] gpio: madera: Add support for Cirrus Logic CS47L15 Charles Keepax
2019-08-05 9:45 ` Linus Walleij
2019-07-22 9:07 ` Charles Keepax [this message]
2019-08-05 9:45 ` [PATCH 4/4] gpio: madera: Add support for Cirrus Logic CS47L92 Linus Walleij
2019-08-05 9:42 ` [PATCH 1/4] gpio: arizona: Use local copy of pdata 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=20190722090748.20807-4-ckeepax@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=patches@opensource.cirrus.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;
as well as URLs for NNTP newsgroup(s).