From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 PATCH 1/1] ASoC: soc-core: symmetry checking for each DAIs separately
Date: Fri, 2 Sep 2011 16:44:48 +0200 [thread overview]
Message-ID: <20110902144448.GH1901@pengutronix.de> (raw)
In-Reply-To: <1314609314-22162-1-git-send-email-b29396@freescale.com>
On Mon, Aug 29, 2011 at 05:15:14PM +0800, Dong Aisheng wrote:
> The orginal code does not cover the case that one DAI such as codec
> may be shared between other two DAIs(CPU).
> When do symmetry checking, altough the codec DAI requires symmetry,
> the two CPU DAIs may still be configured to run on different rates.
>
> We change to check each DAI's state separately instead of only checking
> the dai link to prevent this issue.
>
> Signed-off-by: Dong Aisheng <b29396@freescale.com>
Removes the race warning for me:
Tested-by: Wolfram Sang <w.sang@pengutronix.de>
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110902/a8f9e3d3/attachment.sig>
next prev parent reply other threads:[~2011-09-02 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 9:15 [RFC v2 PATCH 1/1] ASoC: soc-core: symmetry checking for each DAIs separately Dong Aisheng
2011-08-29 20:34 ` [alsa-devel] " Tabi Timur-B04825
2011-08-30 2:54 ` Dong Aisheng-B29396
2011-08-31 10:52 ` Liam Girdwood
2011-08-31 11:55 ` Tabi Timur-B04825
2011-08-31 12:17 ` Lars-Peter Clausen
2011-09-01 18:58 ` Timur Tabi
2011-09-01 19:32 ` Lars-Peter Clausen
2011-09-01 20:35 ` Timur Tabi
2011-09-16 3:02 ` Dong Aisheng
2011-09-02 14:44 ` Wolfram Sang [this message]
2011-09-21 14:59 ` Mark Brown
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=20110902144448.GH1901@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).