From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Tushar Behera <tushar.behera@linaro.org>
Subject: Re: [PATCH 0/8] ASoC: Replace remaining users of the CODEC mutex
Date: Mon, 10 Nov 2014 08:49:30 +0000 [thread overview]
Message-ID: <20141110084930.GA23178@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1415548864-27203-1-git-send-email-lars@metafoo.de>
On Sun, Nov 09, 2014 at 05:00:56PM +0100, Lars-Peter Clausen wrote:
> We've stopped using the snd_soc_codec mutex in the ASoC core itself a while
> ago. There is still a handful of drivers which use the mutex to protect some
> of their data structures. This patch moves the lock for the remaining users
> to the drivers private data struct and then removes it from the
> snd_soc_codec struct.
>
> - Lars
>
> Lars-Peter Clausen (8):
> ASoC: ab8500-codec: Move control lock to the driver level
> ASoC: max98095: Move mutex to the driver level
> ASoC: wm5102: Move ultrasonic response settings lock to the driver
> level
> ASoC: wm8731: Move the deemph lock to the driver level
> ASoC: wm8903: Move the deemph lock to the driver level
> ASoC: wm8958: Move DSP firmware lock to driver level
> ASoC: wm8962: Move DSP enable lock to the driver level
> ASoC: Remove CODEC mutex
>
> include/linux/mfd/arizona/core.h | 1 +
> include/sound/soc.h | 1 -
> sound/soc/codecs/ab8500-codec.c | 32 ++++++++++++++++----------------
> sound/soc/codecs/arizona.c | 4 ++--
> sound/soc/codecs/max98095.c | 12 ++++++++----
> sound/soc/codecs/wm5102.c | 16 ++++++++--------
> sound/soc/codecs/wm8731.c | 9 +++++++--
> sound/soc/codecs/wm8903.c | 8 ++++++--
> sound/soc/codecs/wm8958-dsp2.c | 12 ++++++------
> sound/soc/codecs/wm8962.c | 8 ++++++--
> sound/soc/codecs/wm8994.c | 2 ++
> sound/soc/codecs/wm8994.h | 2 ++
> sound/soc/soc-core.c | 1 -
> 13 files changed, 64 insertions(+), 44 deletions(-)
>
> --
> 1.8.0
>
For the Wolfson parts:
Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Thanks,
Charles
next prev parent reply other threads:[~2014-11-10 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 16:00 [PATCH 0/8] ASoC: Replace remaining users of the CODEC mutex Lars-Peter Clausen
2014-11-09 16:00 ` [PATCH 1/8] ASoC: ab8500-codec: Move control lock to the driver level Lars-Peter Clausen
2014-11-09 16:00 ` [PATCH 2/8] ASoC: max98095: Move mutex " Lars-Peter Clausen
2014-11-09 16:00 ` [PATCH 3/8] ASoC: wm5102: Move ultrasonic response settings lock " Lars-Peter Clausen
2014-11-09 16:01 ` [PATCH 4/8] ASoC: wm8731: Move the deemph " Lars-Peter Clausen
2014-11-09 16:01 ` [PATCH 5/8] ASoC: wm8903: " Lars-Peter Clausen
2014-11-09 16:01 ` [PATCH 6/8] ASoC: wm8958: Move DSP firmware lock to " Lars-Peter Clausen
2014-11-09 16:01 ` [PATCH 7/8] ASoC: wm8962: Move DSP enable lock to the " Lars-Peter Clausen
2014-11-09 16:01 ` [PATCH 8/8] ASoC: Remove CODEC mutex Lars-Peter Clausen
2014-11-10 8:49 ` Charles Keepax [this message]
2014-11-10 19:08 ` [PATCH 0/8] ASoC: Replace remaining users of the " 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=20141110084930.GA23178@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=tushar.behera@linaro.org \
/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