From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] ASoC: Fix DAPM sequence run for per-widget I/O methods
Date: Mon, 20 Jun 2011 06:33:53 +0100 [thread overview]
Message-ID: <4DFEDBC1.9080806@ti.com> (raw)
In-Reply-To: <1308487790-13071-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On 19/06/11 13:49, Mark Brown wrote:
> Previously we were using the DAPM context rather than a widget as the
> argument for update_bits() so we didn't need to care that our list walk
> of widgets left us one beyond the end of the list. Now we're using them
> for the register update we need to make sure we're pointing at an actual
> widget not the list_head.
>
> Fix originally suggested by Liam on IM.
>
Thanks, was planning to send this yesterday but ended up being delayed at several airports yesterday.
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/soc-dapm.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
> index 605c225..ceb2ba4 100644
> --- a/sound/soc/soc-dapm.c
> +++ b/sound/soc/soc-dapm.c
> @@ -918,6 +918,12 @@ static void dapm_seq_run_coalesced(struct snd_soc_dapm_context *dapm,
> }
>
> if (reg >= 0) {
> + /* Any widget will do, they should all be updating the
> + * same register.
> + */
> + w = list_first_entry(pending, struct snd_soc_dapm_widget,
> + power_list);
> +
> pop_dbg(dapm->dev, card->pop_time,
> "pop test : Applying 0x%x/0x%x to %x in %dms\n",
> value, mask, reg, card->pop_time);
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2011-06-20 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 12:49 [PATCH] ASoC: Fix DAPM sequence run for per-widget I/O methods Mark Brown
2011-06-20 5:33 ` Liam Girdwood [this message]
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=4DFEDBC1.9080806@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.