Skip to contentSkip to conversation

ASoC: wm5102: Initialize dac_comp_lock mutex

PATCH In review Mark Brown 2 participants 2 messages Dec 5, 2014 – Dec 8, 2014

Subsystems (3)
lore
Share & tools
lore

Mark Brown

author maintainer
#0 lore raw

PATCH 1/1 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.

---
 sound/soc/codecs/wm5102.c | 2 ++
 1 file changed, 2 insertions(+)
sound/soc/codecs/wm5102.c +2 -0
index 8c99b7cf47e0..f439ae052128 100644
@@ -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;
 
Signature · 1 line
2.1.3
Acked-by on v1 1/1
#1 lore raw
Quoted 8 lines · Mark Brown

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.

---

Thanks,
Charles