alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sebastien LEDUC <sebastien.leduc@st.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Liam  Girdwood (lrg@ti.com)" <lrg@ti.com>
Subject: Re: question on snd_soc_dai_link_event
Date: Thu, 22 Nov 2012 09:32:41 +0900	[thread overview]
Message-ID: <20121122003239.GA4371@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <9C1683ABA24673439FCD019782C9F4BBDE4BD6E569@SAFEX1MAIL1.st.com>


[-- Attachment #1.1: Type: text/plain, Size: 505 bytes --]

On Wed, Nov 21, 2012 at 06:56:55PM +0100, Sebastien LEDUC wrote:

> For a capture stream, it creates the following routes:
> Cpu_dai widget -> dai_link widget -> codec_dai widget

> And for a playback stream:
> Codec_dai widget -> dai_link widget -> cpu_dai widget

Remember that for a CODEC<->CODEC link both devices will be CODECs so
their widgets have the opposite sense as everything is named in a CPU
centric fashion.  The important thing is that we link playback to
capture and capture to playback.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-11-22  0:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 11:58 question on snd_soc_dai_link_event Sebastien LEDUC
2012-10-26 17:01 ` Mark Brown
2012-11-21 17:56   ` Sebastien LEDUC
2012-11-22  0:32     ` Mark Brown [this message]
2013-01-18 14:07   ` Sebastien LEDUC
2013-01-21  4:31     ` 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=20121122003239.GA4371@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=sebastien.leduc@st.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).