summaryrefslogtreecommitdiff
path: root/sound/soc
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2014-12-05 23:06:31 +0300
committerMark Brown <broonie@kernel.org>2014-12-08 16:08:42 +0300
commit47370022d2ca552ab524bb14211fefa3a2518ba8 (patch)
tree04bf94ef927205c883163d52b245512dd8e8be82 /sound/soc
parentbd6b87c104bae49816808fde5f55a262093e85ed (diff)
downloadlinux-47370022d2ca552ab524bb14211fefa3a2518ba8.tar.xz
ASoC: wm5102: Initialize dac_comp_lock mutex
Commit d74bcaaeb6682 (ASoC: wm5102: Move ultrasonic response settings lock to the driver level) created a driver local mutex for protecting the ultrasonic response settings but neglected to initialize that mutex, causing loud complaints from lockep and potential runtime failures. Fix this by initializing the mutex. Signed-off-by: Mark Brown <broonie@kernel.org> Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Diffstat (limited to 'sound/soc')
-rw-r--r--sound/soc/codecs/wm5102.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/sound/soc/codecs/wm5102.c b/sound/soc/codecs/wm5102.c
index 1f7553492667..d78fb8dffc8c 100644
--- a/sound/soc/codecs/wm5102.c
+++ b/sound/soc/codecs/wm5102.c
@@ -1900,6 +1900,8 @@ static int wm5102_probe(struct platform_device *pdev)
return -ENOMEM;
platform_set_drvdata(pdev, wm5102);
+ mutex_init(&arizona->dac_comp_lock);
+
wm5102->core.arizona = arizona;
wm5102->core.num_inputs = 6;