From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@slimglogic.co.uk>,
alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: Avoid direct register cache access when setting defaults
Date: Mon, 17 Jan 2011 13:51:59 +0000 [thread overview]
Message-ID: <1295272319.3283.10.camel@odin> (raw)
In-Reply-To: <1293713859-4480-1-git-send-email-broonie@opensource.wolfsonmicro.com> (sfid-20101230_125733_199121_1B314023)
On Thu, 2010-12-30 at 12:57 +0000, Mark Brown wrote:
> Directly accessing the register cache means that we can't use anything
> except a flat register cache so use snd_soc_update_bits().
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/codecs/wm8523.c | 6 +++---
> sound/soc/codecs/wm8741.c | 13 ++++++++-----
> sound/soc/codecs/wm8904.c | 41 ++++++++++++++++++++++++++---------------
> sound/soc/codecs/wm8955.c | 27 +++++++++++++++++++--------
> sound/soc/codecs/wm8962.c | 30 ++++++++++++++++++++----------
> sound/soc/codecs/wm8978.c | 2 +-
> sound/soc/codecs/wm9090.c | 41 ++++++++++++++++++++++++-----------------
> 7 files changed, 101 insertions(+), 59 deletions(-)
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2011-01-17 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 12:57 [PATCH] ASoC: Avoid direct register cache access when setting defaults Mark Brown
2011-01-17 13:51 ` Liam Girdwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-24 17:08 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=1295272319.3283.10.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimglogic.co.uk \
--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).