From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: alsa-devel@alsa-project.org
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: Ensure DAPM widgets are set up before we sync jacks
Date: Thu, 06 Oct 2011 15:51:15 +0300 [thread overview]
Message-ID: <2522011.aBmFsviLZv@barack> (raw)
In-Reply-To: <1317904284-7846-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Thursday 06 October 2011 13:31:24 Mark Brown wrote:
> We synchronise jack state on startup - when we do that make sure that we
> have set up all the DAPM widgets first in case we end up touching any of
> the partially set up widgets when syncing the jack pins.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Tested-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
prev parent reply other threads:[~2011-10-06 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 12:31 [PATCH] ASoC: Ensure DAPM widgets are set up before we sync jacks Mark Brown
2011-10-06 12:51 ` Péter Ujfalusi [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=2522011.aBmFsviLZv@barack \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox