From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
broonie@kernel.org, lgirdwood@gmail.com, sameo@linux.intel.com
Subject: Re: [PATCH v2 2/3] mfd: wm5110: Add register patch for rev E and above
Date: Tue, 7 Jul 2015 11:52:55 +0100 [thread overview]
Message-ID: <20150707105255.GT3182@x1> (raw)
In-Reply-To: <1436260993-8814-2-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Tue, 07 Jul 2015, Charles Keepax wrote:
> Add a register patch for rev E and above that configures the location of
> some write sequences to assist with the headphone enables.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
>
> Changes since v1:
> - Added a comment with the write sequence
>
> Thanks,
> Charles
>
> drivers/mfd/wm5110-tables.c | 13 ++++++++++++-
> 1 files changed, 12 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mfd/wm5110-tables.c b/drivers/mfd/wm5110-tables.c
> index 62a4aa1..b70f76b 100644
> --- a/drivers/mfd/wm5110-tables.c
> +++ b/drivers/mfd/wm5110-tables.c
> @@ -249,6 +249,15 @@ static const struct reg_default wm5110_revd_patch[] = {
> { 0x80, 0x0 },
> };
>
> +static const struct reg_default wm5110_reve_patch[] = {
> + { 0x80, 0x3 },
> + { 0x80, 0x3 },
> + { 0x4b, 0x138 }, /* Add extra headphone write sequence locations */
> + { 0x4c, 0x13d },
> + { 0x80, 0x0 },
> + { 0x80, 0x0 },
> +};
Now the other lines look undocumented. Can you please provide an
over-arching comment which describes what the entire sequence does
please.
> /* We use a function so we can use ARRAY_SIZE() */
> int wm5110_patch(struct arizona *arizona)
> {
> @@ -266,7 +275,9 @@ int wm5110_patch(struct arizona *arizona)
> wm5110_revd_patch,
> ARRAY_SIZE(wm5110_revd_patch));
> default:
> - return 0;
> + return regmap_register_patch(arizona->regmap,
> + wm5110_reve_patch,
> + ARRAY_SIZE(wm5110_reve_patch));
> }
> }
> EXPORT_SYMBOL_GPL(wm5110_patch);
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-07-07 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 9:23 [PATCH v2 1/3] mfd: wm5110: Add registers for custom write sequence triggers Charles Keepax
2015-07-07 9:23 ` [PATCH v2 2/3] mfd: wm5110: Add register patch for rev E and above Charles Keepax
2015-07-07 10:52 ` Lee Jones [this message]
2015-07-07 9:23 ` [PATCH v2 3/3] ASoC: wm5110: Add special DRE on/off handling for the headphone path Charles Keepax
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=20150707105255.GT3182@x1 \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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