From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: myungjoo.ham@samsung.com, cw00.choi@samsung.com,
dmitry.torokhov@gmail.com, lgirdwood@gmail.com, lars@metafoo.de,
peter.ujfalusi@ti.com, jarkko.nikula@bitmer.com,
eric.y.miao@gmail.com, haojian.zhuang@gmail.com,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
linux@arm.linux.org.uk
Subject: [PATCH 00/17 v2] Update locking for snd_soc_dapm_xxxx_pin functions
Date: Tue, 18 Feb 2014 15:22:11 +0000 [thread overview]
Message-ID: <1392736948-26623-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)
This patchset updates the locking around the
snd_soc_dapm_xxxx_pin functions. First we add an unlocked
version of the functions and add locking to the standard
call, this also requires us to remove the few places where
these functions are externally locked. Then we patch usages
of the functions that look like they are expecting to do an
atomic update to do so, using external locking.
Thanks,
Charles
Updates since v1:
- Added helper functions to lock/unlock the dapm mutex
- Added an unlocked version of snd_soc_dapm_sync, so it can
be called under the same mutex lock as the pin functions,
this is not required just saves a mutex lock
Charles Keepax (17):
Input - arizona-haptics: Fix double lock of dapm_mutex
ASoC: dapm: Add helpers to lock/unlock DAPM mutex
ASoC: dapm: Add locking to snd_soc_dapm_xxxx_pin functions
ASoC: dapm: Add unlocked version of snd_soc_dapm_sync
ASoC: adav80x: Update locking around use of DAPM pin API
ASoC: wm5100: Update locking around use of DAPM pin API
ASoC: wm8962: Update locking around use of DAPM pin API
ASoC: wm8994: Update locking around use of DAPM pin API
ASoC: wm8996: Update locking around use of DAPM pin API
ASoC: mfld_machine: Update locking around use of DAPM pin API
ASoC: ams-delta: Update locking around use of DAPM pin API
ASoC: omap: n810: Update locking around use of DAPM pin API
ASoC: omap: rx51: Update locking around use of DAPM pin API
ASoC: pxa: corgi: Update locking around use of DAPM pin API
ASoC: pxa: magician: Update locking around use of DAPM pin API
ASoC: pxa: spitz: Update locking around use of DAPM pin API
ASoC: pxa: tosa: Update locking around use of DAPM pin API
drivers/extcon/extcon-arizona.c | 12 ---
drivers/input/misc/arizona-haptics.c | 19 ----
include/sound/soc-dapm.h | 9 ++
include/sound/soc.h | 9 ++
sound/soc/codecs/adav80x.c | 17 +++--
sound/soc/codecs/wm5100.c | 12 ++-
sound/soc/codecs/wm8962.c | 13 ++-
sound/soc/codecs/wm8994.c | 45 ++++++----
sound/soc/codecs/wm8996.c | 9 ++-
sound/soc/intel/mfld_machine.c | 65 +++++++++-----
sound/soc/omap/ams-delta.c | 45 ++++++----
sound/soc/omap/n810.c | 22 +++--
sound/soc/omap/rx51.c | 22 +++--
sound/soc/pxa/corgi.c | 42 +++++----
sound/soc/pxa/magician.c | 22 +++--
sound/soc/pxa/spitz.c | 51 ++++++-----
sound/soc/pxa/tosa.c | 28 ++++---
sound/soc/soc-dapm.c | 160 ++++++++++++++++++++++++++++++---
18 files changed, 399 insertions(+), 203 deletions(-)
--
1.7.2.5
next reply other threads:[~2014-02-18 15:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 15:22 Charles Keepax [this message]
2014-02-18 15:22 ` [PATCH 01/17 v2] Input - arizona-haptics: Fix double lock of dapm_mutex Charles Keepax
2014-02-20 3:54 ` Mark Brown
2014-02-20 4:20 ` Dmitry Torokhov
2014-02-20 9:12 ` Mark Brown
2014-02-18 15:22 ` [PATCH 02/17 v2] ASoC: dapm: Add helpers to lock/unlock DAPM mutex Charles Keepax
2014-02-20 10:23 ` Mark Brown
2014-02-18 15:22 ` [PATCH 03/17 v2] ASoC: dapm: Add locking to snd_soc_dapm_xxxx_pin functions Charles Keepax
2014-02-20 9:40 ` Mark Brown
2014-02-18 15:22 ` [PATCH 04/17 v2] ASoC: dapm: Add unlocked version of snd_soc_dapm_sync Charles Keepax
2014-02-18 16:14 ` Lars-Peter Clausen
2014-02-19 3:28 ` Mark Brown
2014-02-20 10:24 ` Mark Brown
2014-02-18 15:22 ` [PATCH 05/17 v2] ASoC: adav80x: Update locking around use of DAPM pin API Charles Keepax
2014-02-18 16:12 ` Lars-Peter Clausen
2014-02-20 10:25 ` Mark Brown
2014-02-18 15:22 ` [PATCH 06/17 v2] ASoC: wm5100: " Charles Keepax
2014-02-20 10:26 ` Mark Brown
2014-02-18 15:22 ` [PATCH 07/17 v2] ASoC: wm8962: " Charles Keepax
2014-02-20 10:26 ` Mark Brown
2014-02-18 15:22 ` [PATCH 08/17 v2] ASoC: wm8994: " Charles Keepax
2014-02-20 10:26 ` Mark Brown
2014-02-18 15:22 ` [PATCH 09/17 v2] ASoC: wm8996: " Charles Keepax
2014-02-20 10:27 ` Mark Brown
2014-02-18 15:22 ` [PATCH 10/17 v2] ASoC: mfld_machine: " Charles Keepax
2014-02-20 10:27 ` Mark Brown
2014-02-18 15:22 ` [PATCH 11/17 v2] ASoC: ams-delta: " Charles Keepax
2014-02-20 10:27 ` Mark Brown
2014-02-18 15:22 ` [PATCH 12/17 v2] ASoC: omap: n810: " Charles Keepax
2014-02-20 10:28 ` Mark Brown
2014-02-18 15:22 ` [PATCH 13/17 v2] ASoC: omap: rx51: " Charles Keepax
2014-02-20 10:28 ` Mark Brown
2014-02-18 15:22 ` [PATCH 14/17 v2] ASoC: pxa: corgi: " Charles Keepax
2014-02-20 10:53 ` Mark Brown
2014-02-18 15:22 ` [PATCH 15/17 v2] ASoC: pxa: magician: " Charles Keepax
2014-02-20 10:54 ` Mark Brown
2014-02-18 15:22 ` [PATCH 16/17 v2] ASoC: pxa: spitz: " Charles Keepax
2014-02-20 10:54 ` Mark Brown
2014-02-18 15:22 ` [PATCH 17/17 v2] ASoC: pxa: tosa: " Charles Keepax
2014-02-20 10:54 ` 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=1392736948-26623-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=jarkko.nikula@bitmer.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=peter.ujfalusi@ti.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