From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: <lee.jones@linaro.org>, <linus.walleij@linaro.org>, <broonie@kernel.org>
Cc: <patches@opensource.wolfsonmicro.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <alsa-devel@alsa-project.org>
Subject: [PATCH v2 2/3] gpio: arizona: Support Cirrus Logic CS47L24 and WM1831
Date: Mon, 19 Oct 2015 15:13:46 +0100 [thread overview]
Message-ID: <1445264027-7357-3-git-send-email-rf@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1445264027-7357-1-git-send-email-rf@opensource.wolfsonmicro.com>
The CS47L24 and WM1831 codecs only have two GPIO lines, but are
otherwise similar to the WM8280.
Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
---
drivers/gpio/gpio-arizona.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpio/gpio-arizona.c b/drivers/gpio/gpio-arizona.c
index ca00273..624ea54 100644
--- a/drivers/gpio/gpio-arizona.c
+++ b/drivers/gpio/gpio-arizona.c
@@ -122,6 +122,10 @@ static int arizona_gpio_probe(struct platform_device *pdev)
case WM1814:
arizona_gpio->gpio_chip.ngpio = 5;
break;
+ case WM1831:
+ case CS47L24:
+ arizona_gpio->gpio_chip.ngpio = 2;
+ break;
default:
dev_err(&pdev->dev, "Unknown chip variant %d\n",
arizona->type);
--
1.9.1
next prev parent reply other threads:[~2015-10-19 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 14:13 [PATCH v2 0/3] Add support for Cirrus Logic CS47L24 and WM1831 codecs Richard Fitzgerald
2015-10-19 14:13 ` [PATCH v2 1/3] mfd: arizona: Support Cirrus Logic CS47L24 and WM1831 Richard Fitzgerald
2015-10-30 18:29 ` Lee Jones
2015-10-19 14:13 ` Richard Fitzgerald [this message]
2015-10-27 9:58 ` [PATCH v2 2/3] gpio: " Linus Walleij
2015-10-28 11:42 ` Lee Jones
2015-10-29 14:29 ` Linus Walleij
2015-10-19 14:13 ` [PATCH v2 3/3] ASoC: cs47l24: Add driver for Cirrus Logic CS47L24 and WM1831 codecs Richard Fitzgerald
2015-10-22 12:40 ` Mark Brown
2015-10-19 14:52 ` [alsa-devel] [PATCH v2 0/3] Add support " Caleb Crome
2015-10-19 15:04 ` Richard Fitzgerald
2015-10-19 15:10 ` Caleb Crome
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=1445264027-7357-3-git-send-email-rf@opensource.wolfsonmicro.com \
--to=rf@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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).