From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
"; Liam Girdwood" <lrg@slimlogic.co.uk>
Subject: Re: Does ASoC support sound card with multiple interfaces?
Date: Wed, 4 Jan 2012 11:06:53 +0530 [thread overview]
Message-ID: <1325655413.12508.79.camel@matrix> (raw)
In-Reply-To: <20120102201642.GA30932@sirena.org.uk>
> > I have a codec with multiple TX and RX channels. In ASoC tree, I have
> > seen examples where these kind of codecs are implemented as multichannel
> > codecs. Instead I want it to be treated as card with multiple
>
> Yes, this is totally supported. There are quite a few examples of this
> in the tree. Your CODEC driver should just implement one DAI per audio
> interface.
>
Thanks.
I am looking at some of the examples in the tree and have a small query.
I want to know how alsa-utils (aplay, arecord) will behave when a codec
driver supports multiple DAIs. For example, let's assume that a codec
driver implements two DAIs, both capable of doing stereo playback. Then
I try to play two files simultaneously using aplay, e.g.
$ aplay x.wav
$ aplay y.wav
AFAIK first "aplay" will result in play back on default interface/DAI
(i.e. 0). What will happen with second aplay? Will it automatically find
a free DAI to playback? or it is mandatory to explicitly specify the
PCM/card # for second aplay?
Similarly what will happen in case of arecord when a codec supports
multiple DAIs capable of capturing?
next prev parent reply other threads:[~2012-01-04 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 15:06 Does ASoC support sound card with multiple interfaces? Ashish Chavan
2012-01-02 20:16 ` Mark Brown
2012-01-04 5:36 ` Ashish Chavan [this message]
2012-01-04 5:47 ` Rajeev kumar
2012-01-04 7:00 ` Ashish Chavan
2012-01-04 7:03 ` Rajeev kumar
2012-01-05 6:02 ` 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=1325655413.12508.79.camel@matrix \
--to=ashish.chavan@kpitcummins.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.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 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.