From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/2] ASoC: Mark WM8962 Additional Control 4 register as volatile
Date: Thu, 30 Sep 2010 14:54:54 +0100 [thread overview]
Message-ID: <1285854894.3101.0.camel@odin> (raw)
In-Reply-To: <1285806521-23090-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Wed, 2010-09-29 at 17:28 -0700, Mark Brown wrote:
> There are some status bits for microphone detection in here.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/codecs/wm8962-tables.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/sound/soc/codecs/wm8962-tables.c b/sound/soc/codecs/wm8962-tables.c
> index f21a8c1..6fa98ea 100644
> --- a/sound/soc/codecs/wm8962-tables.c
> +++ b/sound/soc/codecs/wm8962-tables.c
> @@ -21204,7 +21204,7 @@ const struct wm8962_reg_access wm8962_reg_access[WM8962_MAX_REGISTER + 1] = {
> { 0x0000, 0x0000, 0x0000 }, /* R45 */
> { 0x0000, 0x0000, 0x0000 }, /* R46 */
> { 0x000F, 0x0000, 0x0000 }, /* R47 - Thermal Shutdown Status */
> - { 0x7EC7, 0x7E07, 0x0000 }, /* R48 - Additional Control (4) */
> + { 0x7EC7, 0x7E07, 0xFFFF }, /* R48 - Additional Control (4) */
> { 0x00D3, 0x00D7, 0xFFFF }, /* R49 - Class D Control 1 */
> { 0x0000, 0x0000, 0x0000 }, /* R50 */
> { 0x0047, 0x0047, 0x0000 }, /* R51 - Class D Control 2 */
Both
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
prev parent reply other threads:[~2010-09-30 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 0:28 [PATCH 1/2] ASoC: Mark WM8962 Additional Control 4 register as volatile Mark Brown
2010-09-30 0:28 ` [PATCH 2/2] ASoC: Provide microphone bias configuration for WM8962 Mark Brown
2010-09-30 13:54 ` Liam Girdwood [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=1285854894.3101.0.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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.