ASoC: Use the correct DAPM context when cleaning up final widget set
PATCH 1/1 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 <[email protected]>
--- sound/soc/soc-dapm.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
sound/soc/soc-dapm.c +1 -1
@@ -984,7 +984,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);if (cur_dapm && cur_dapm->seq_notifier) {for (i =0 ; i <ARRAY_SIZE (dapm_up_seq); i++)
Signature · 1 line
1.7.2.3
Quoted 10 lines · Mark Brown
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 <[email protected]>--- sound/soc/soc-dapm.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
Acked-by Liam Girdwood <[email protected]>