From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: lgirdwood@gmail.com, patches@opensource.wolfsonmicro.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 1/3] regulator: arizona: add support for WM8998 and WM1814
Date: Mon, 28 Sep 2015 14:01:07 +0100 [thread overview]
Message-ID: <1443445269-11746-2-git-send-email-rf@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1443445269-11746-1-git-send-email-rf@opensource.wolfsonmicro.com>
Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Acked-by: Mark Brown <broonie@kernel.org>
---
drivers/regulator/arizona-ldo1.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index 5e947a8..e3c5982 100644
--- a/drivers/regulator/arizona-ldo1.c
+++ b/drivers/regulator/arizona-ldo1.c
@@ -245,6 +245,8 @@ static int arizona_ldo1_probe(struct platform_device *pdev)
switch (arizona->type) {
case WM5102:
case WM8997:
+ case WM8998:
+ case WM1814:
desc = &arizona_ldo1_hc;
ldo1->init_data = arizona_ldo1_dvfs;
break;
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <patches@opensource.wolfsonmicro.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 1/3] regulator: arizona: add support for WM8998 and WM1814
Date: Mon, 28 Sep 2015 14:01:07 +0100 [thread overview]
Message-ID: <1443445269-11746-2-git-send-email-rf@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1443445269-11746-1-git-send-email-rf@opensource.wolfsonmicro.com>
Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Acked-by: Mark Brown <broonie@kernel.org>
---
drivers/regulator/arizona-ldo1.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index 5e947a8..e3c5982 100644
--- a/drivers/regulator/arizona-ldo1.c
+++ b/drivers/regulator/arizona-ldo1.c
@@ -245,6 +245,8 @@ static int arizona_ldo1_probe(struct platform_device *pdev)
switch (arizona->type) {
case WM5102:
case WM8997:
+ case WM8998:
+ case WM1814:
desc = &arizona_ldo1_hc;
ldo1->init_data = arizona_ldo1_dvfs;
break;
--
1.9.1
next prev parent reply other threads:[~2015-09-28 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 13:01 [PATCH v2 0/3] Add support for Wolfson Micro WM8998 codec Richard Fitzgerald
2015-09-28 13:01 ` Richard Fitzgerald
2015-09-28 13:01 ` Richard Fitzgerald [this message]
2015-09-28 13:01 ` [PATCH v2 1/3] regulator: arizona: add support for WM8998 and WM1814 Richard Fitzgerald
2015-09-30 18:16 ` Mark Brown
2015-10-01 7:51 ` Charles Keepax
2015-10-01 7:51 ` Charles Keepax
2015-09-28 13:01 ` [PATCH v2 2/3] ASoC: arizona: add defines for single-input gain control Richard Fitzgerald
2015-09-28 13:01 ` Richard Fitzgerald
2015-09-28 13:01 ` [PATCH v2 3/3] ASoC: wm8998: Initial WM8998 codec driver Richard Fitzgerald
2015-09-28 13:01 ` Richard Fitzgerald
2015-10-02 17:13 ` Applied "ASoC: wm8998: Initial WM8998 codec driver" to the asoc tree Mark Brown
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=1443445269-11746-2-git-send-email-rf@opensource.wolfsonmicro.com \
--to=rf@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.