From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
geert@linux-m68k.org, broonie@kernel.org
Subject: Re: [PATCH RESEND] mfd: Fixup clients of multi_reg_write/register_patch
Date: Sat, 19 Sep 2015 11:08:20 +0100 [thread overview]
Message-ID: <20150919100820.GK3218@x1> (raw)
In-Reply-To: <1442577358-6908-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Fri, 18 Sep 2015, Charles Keepax wrote:
> From: Nariman Poushin <nariman@opensource.wolfsonmicro.com>
>
> Introduced by:
> commit 8019ff6cfc04
> ("regmap: Use reg_sequence for multi_reg_write / register_patch")
>
> Interacting with:
> commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
> commit 81207880cef2 ("mfd: wm5110: Add register patch for rev E and above")
>
> Signed-off-by: Nariman Poushin <nariman@opensource.wolfsonmicro.com>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/wm5110-tables.c | 2 +-
> drivers/mfd/wm8998-tables.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.
> diff --git a/drivers/mfd/wm5110-tables.c b/drivers/mfd/wm5110-tables.c
> index 768f1ea..205fbd1 100644
> --- a/drivers/mfd/wm5110-tables.c
> +++ b/drivers/mfd/wm5110-tables.c
> @@ -250,7 +250,7 @@ static const struct reg_sequence wm5110_revd_patch[] = {
> };
>
> /* Add extra headphone write sequence locations */
> -static const struct reg_default wm5110_reve_patch[] = {
> +static const struct reg_sequence wm5110_reve_patch[] = {
> { 0x80, 0x3 },
> { 0x80, 0x3 },
> { 0x4b, 0x138 },
> diff --git a/drivers/mfd/wm8998-tables.c b/drivers/mfd/wm8998-tables.c
> index e6de3cd..607640c 100644
> --- a/drivers/mfd/wm8998-tables.c
> +++ b/drivers/mfd/wm8998-tables.c
> @@ -21,7 +21,7 @@
> #define WM8998_NUM_AOD_ISR 2
> #define WM8998_NUM_ISR 5
>
> -static const struct reg_default wm8998_rev_a_patch[] = {
> +static const struct reg_sequence wm8998_rev_a_patch[] = {
> { 0x0212, 0x0000 },
> { 0x0211, 0x0014 },
> { 0x04E4, 0x0E0D },
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2015-09-19 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 11:55 [PATCH RESEND] mfd: Fixup clients of multi_reg_write/register_patch Charles Keepax
2015-09-19 10:08 ` Lee Jones [this message]
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=20150919100820.GK3218@x1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
/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