From: Lars-Peter Clausen <lars@metafoo.de>
To: Sergej Sawazki <ssawazki@gmx.de>, alsa-devel@alsa-project.org
Cc: Benoit Cousson <bcousson@baylibre.com>
Subject: Re: ASoC: How to connect a single CPU DAI to two codecs?
Date: Sat, 27 Sep 2014 19:17:24 +0200 [thread overview]
Message-ID: <5426F124.2070607@metafoo.de> (raw)
In-Reply-To: <5426BCB8.6030002@gmx.de>
On 09/27/2014 03:33 PM, Sergej Sawazki wrote:
> Hello,
>
> I'm writing an ALSA SoC machine driver for a board that has two mono codecs
> (left and right audio channel). Each codec is controlled over I2C and has
> itsown address.Both codecs are connected to the same I2S CPU DAI (as shown
> below).
>
> +--------- (adr: 0x1a) -----+
> | |
> | +--------> codec_1 ----> (left channel audio)
> | |
> I2C I2S ----+
> | |
> | +--------> codec_2 ----> (right channel audio)
> | |
> +--------- (adr: 0x1b) -----+
>
> Can someone give me some advice on how to setup the 'snd_soc_card' and
> 'snd_soc_dai_link' in this case? Do I need two dai_links with the same
> 'cpu_dai_name' and 'platform_name'?
>
> Are there examples for such a configuration? I didn't had much luck in
> finding one in the mainline?
>
> Any help would be highly appreciated. Thanks!
Hi,
Support for multiple CODEC DAIs on the same link has recently been added by
Benoit. See commit 88bd870f ("ASoC: core: Add initial support for DAI
multicodec"). You now have the possibility to specify multiple CODEC DAIs in
the link using the snd_soc_dai_link_component struct.
- Lars
next prev parent reply other threads:[~2014-09-27 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 13:33 ASoC: How to connect a single CPU DAI to two codecs? Sergej Sawazki
2014-09-27 17:17 ` Lars-Peter Clausen [this message]
2014-09-28 17:20 ` Sergej Sawazki
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=5426F124.2070607@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=bcousson@baylibre.com \
--cc=ssawazki@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.