From: Benoit Cousson <bcousson@baylibre.com>
To: Petr Kulhavy <petr@barix.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: ASoC: Two codecs on a single CPU DAI
Date: Wed, 21 May 2014 13:29:37 +0200 [thread overview]
Message-ID: <537C8E21.8040400@baylibre.com> (raw)
In-Reply-To: <537B5CA4.8010607@metafoo.de>
Hi Petr,
I'm about to release a v4, but you can used the previous version that
was working fine for my setup.
I'm glad to have more users for the series, because my setup is so
simple that I cannot validate all the code I'm about to change :-(
Bottom line; The more, the merrier.
Regards,
Benoit
On 20/05/2014 15:46, Lars-Peter Clausen wrote:
> On 05/20/2014 03:08 PM, Petr Kulhavy wrote:
>> Hi,
>>
>> I'm writing a driver for a custom DaVinci board, which has two codecs
>> (Wolfson and STA323 amplifier) connected to the same CPU DAI. The
>> intention
>> is that both codecs always play the same audio, only the volume/mixer
>> settings are controlled separately. In addition to that the design is
>> atypical by the fact, that the Wolfson is the clock master. So in
>> order to
>> play audio on the amplifier the Wolfson must be initialized as well.
>>
>> My question is: how to reflect this architecture in a SOC platform
>> driver?
>>
>> As the first approach I tried to create two DAI links, one for each
>> codec.
>> That worked if audio was first played on the Wolfson link (clock
>> master was
>> initialized) and then on the second link, using the same sampling rate.
>>
>> But in fact I would need only one DAI link to both. So then I tried to
>> make
>> just one link to Wolfson and put the amplifier as an "aux_dev". However
>> there I need to set hw_params and format for the amplifier codec DAI and
>> those functions were not called. In fact there was no codec DAI
>> created for
>> the amplifier. I've also seen that one can define rtd_aux runtimes,
>> but have
>> nowhere found how to use it.
>>
>> Could someone please help me?
>
> Hi,
>
> Benoit is currently working on adding support for this to the ASoC
> framework, see this patch series:
> http://comments.gmane.org/gmane.linux.alsa.devel/122160
>
> - Lars
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Benoît Cousson
BayLibre
Embedded Linux Technology Lab
www.baylibre.com
next prev parent reply other threads:[~2014-05-21 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 13:08 ASoC: Two codecs on a single CPU DAI Petr Kulhavy
2014-05-20 13:46 ` Lars-Peter Clausen
2014-05-21 11:29 ` Benoit Cousson [this message]
2014-05-22 13:49 ` Petr Kulhavy
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=537C8E21.8040400@baylibre.com \
--to=bcousson@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
--cc=petr@barix.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).