From: lrg@ti.com (Liam Girdwood)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [RFC v2 PATCH 1/1] ASoC: soc-core: symmetry checking for each DAIs separately
Date: Wed, 31 Aug 2011 11:52:53 +0100 [thread overview]
Message-ID: <4E5E1285.8020508@ti.com> (raw)
In-Reply-To: <65EE16ACC360FA4D99C96DC085B3F77222AE40@039-SN1MPN1-001.039d.mgd.msft.net>
On 30/08/11 03:54, Dong Aisheng-B29396 wrote:
>> -----Original Message-----
>> From: Tabi Timur-B04825
>> Sent: Tuesday, August 30, 2011 4:35 AM
>> To: Dong Aisheng-B29396
>> Cc: alsa-devel at alsa-project.org; lars at metafoo.de; s.hauer at pengutronix.de;
>> broonie at opensource.wolfsonmicro.com; w.sang at pengutronix.de; lrg at ti.com;
>> linux-arm-kernel at lists.infradead.org
>> Subject: Re: [alsa-devel] [RFC v2 PATCH 1/1] ASoC: soc-core: symmetry
>> checking for each DAIs separately
>>
>> On Mon, Aug 29, 2011 at 4:15 AM, Dong Aisheng <b29396@freescale.com>
>> wrote:
>>> The orginal code does not cover the case that one DAI such as codec
>>> may be shared between other two DAIs(CPU).
>>
>> Can you give me an example of how this can occur?
>>
>
> Pls check the following case used in mx28evk.
> static struct snd_soc_dai_link mxs_sgtl5000_dai[] = {
> {
> .name = "HiFi Tx",
> .stream_name = "HiFi Playback",
> .codec_dai_name = "sgtl5000",
> .codec_name = "sgtl5000.0-000a",
> .cpu_dai_name = "mxs-saif.0",
> .platform_name = "mxs-pcm-audio.0",
> .ops = &mxs_sgtl5000_hifi_ops,
> }, {
> .name = "HiFi Rx",
> .stream_name = "HiFi Capture",
> .codec_dai_name = "sgtl5000",
> .codec_name = "sgtl5000.0-000a",
> .cpu_dai_name = "mxs-saif.1",
> .platform_name = "mxs-pcm-audio.1",
> .ops = &mxs_sgtl5000_hifi_ops,
> },
> };
> You can also refer to:
> http://thread.gmane.org/gmane.linux.ports.arm.kernel/129789/focus=129839
>
Timur, iirc your driver has some special symmetry requirement (maybe something todo with having 2 DAIs) ?
I assume this is OK for you too ?
Acked-by: Liam Girdwood <lrg@ti.com>
Liam
next prev parent reply other threads:[~2011-08-31 10:52 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 [this message]
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
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=4E5E1285.8020508@ti.com \
--to=lrg@ti.com \
--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).