From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: "Frkuska, Joshua" <Joshua_Frkuska@mentor.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC: no-pcm (backend) error propagation
Date: Mon, 04 Mar 2013 19:42:10 +0000 [thread overview]
Message-ID: <1362426130.4448.62.camel@loki> (raw)
In-Reply-To: <190351B32828744FBA3BD9565204D27B01CA7704@NA-MBX-03.mgc.mentorg.com>
Re-flowed.
On Mon, 2013-03-04 at 01:30 +0000, Frkuska, Joshua wrote:
> If you could tell me the area you have in mind for the routing back
propagation when re-parenting, I can study that, before creating
something that isn’t inline with the existing code.
>
There is some re parenting code in soc-pcm.c dpcm_be_reparent(). It
shows the list connect each FE and BE and should give some ideas for the
back routing.
Liam
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2013-03-04 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 2:21 ASoC: no-pcm (backend) error propagation Frkuska, Joshua
2013-02-27 8:23 ` Liam Girdwood
2013-02-27 15:43 ` Pierre-Louis Bossart
2013-03-01 21:25 ` Liam Girdwood
2013-03-04 1:30 ` Frkuska, Joshua
2013-03-04 19:42 ` Liam Girdwood [this message]
2013-03-05 15:34 ` Frkuska, Joshua
2013-02-28 0:49 ` Frkuska, Joshua
2013-03-01 21:24 ` Liam Girdwood
2013-03-02 3:32 ` Mark Brown
2013-03-04 1:17 ` Frkuska, Joshua
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=1362426130.4448.62.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=Joshua_Frkuska@mentor.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=pierre-louis.bossart@linux.intel.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;
as well as URLs for NNTP newsgroup(s).