summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Brown <broonie@opensource.wolfsonmicro.com>2011-03-08 19:29:53 +0000
committerMark Brown <broonie@opensource.wolfsonmicro.com>2011-03-09 12:32:50 +0000
commit28e868081086c495c897a48c50d2d5187ef677d2 (patch)
treea7eb8edcf9190899bceacad8fc1f60a14c0424c5
parent823dba5191220fc94b83dc0b3f2178ff0842e294 (diff)
downloadlinux-3.10-28e868081086c495c897a48c50d2d5187ef677d2.tar.gz
linux-3.10-28e868081086c495c897a48c50d2d5187ef677d2.tar.bz2
linux-3.10-28e868081086c495c897a48c50d2d5187ef677d2.zip
ASoC: Use the correct DAPM context when cleaning up final widget set
Now we've got multi-component we need to make sure that the DAPM context (and hence register I/O context) we use to apply the pending updates at the end of a DAPM sequence is the one we were processing rather than the one that was used to initate the state change. Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com> Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
-rw-r--r--sound/soc/soc-dapm.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
index 25e54230cc6..1790f83ee66 100644
--- a/sound/soc/soc-dapm.c
+++ b/sound/soc/soc-dapm.c
@@ -941,7 +941,7 @@ static void dapm_seq_run(struct snd_soc_dapm_context *dapm,
}
if (!list_empty(&pending))
- dapm_seq_run_coalesced(dapm, &pending);
+ dapm_seq_run_coalesced(cur_dapm, &pending);
}
static void dapm_widget_update(struct snd_soc_dapm_context *dapm)