From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Arnaud POULIQUEN <arnaud.pouliquen@st.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@cassiel.sirena.org.uk" <broonie@cassiel.sirena.org.uk>
Subject: Re: ASOC: stream widget created two times
Date: Mon, 25 Nov 2013 18:48:02 +0000 [thread overview]
Message-ID: <1385405282.2479.8.camel@loki> (raw)
In-Reply-To: <A4ED9057F6AB394EB1BF089A056089A853220EBBA8@SAFEX1MAIL5.st.com>
On Fri, 2013-11-22 at 15:19 +0100, Arnaud POULIQUEN wrote:
> Hello,
> I 'm newbie on asoc dev. I'm trying to develop a driver based on dynamic
> PCM implementation with backend and frontend. I'm working on 3.10
>
> I have declared a FE :
> {
> .name = "MMDL0",
> .stream_name = "MM DL0 Frontend",
> .cpu_dai_name = "mm_dl0",
>
> .codec_name = "snd-soc-dummy",
> .codec_dai_name = "snd-soc-dummy-dai",
>
> .dynamic=1,
> .trigger = {SND_SOC_DPCM_TRIGGER_POST, SND_SOC_DPCM_TRIGGER_POST},
> .ignore_pmdown_time = 1, /* Power down without delay */
> .init = sti_dummy_init,
> },
>
> CPU DAI associated:
> static struct snd_soc_dai_driver sti_frontend_cpu_dais[] = {
> {
> .name = "mm_dl0",
> .playback = {
> .stream_name = "MM_DL0",
> .channels_min = 1,
> .channels_max = 8,
> .rates = SNDRV_PCM_RATE_48000,
> .formats = SNDRV_PCM_FMTBIT_S16_LE
> },
> .probe = sti_frontend_dai_probe,
> .probe_order = SND_SOC_COMP_ORDER_FIRST,
> },
> }
> Platform is declared using platform_of_node using DTS.
> I have also declared a BE and the route that links the FE cpu dai widget with
> the BE codec dai widget.
>
> My concern is that MM_DL0 widget is created 2 times. One time in soc_probe_link_dais
> and one time in soc_probe_platform.
This bug has been fixed in later kernel. Can you cherry pick commit
ae10e7e8f1c9d021c8daca750d743cc3baa12e6d from 3.12.
Thanks
Liam
prev parent reply other threads:[~2013-11-25 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 14:19 ASOC: stream widget created two times Arnaud POULIQUEN
2013-11-25 18:48 ` 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=1385405282.2479.8.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@cassiel.sirena.org.uk \
/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).