From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"; Liam Girdwood" <lrg@slimlogic.co.uk>
Subject: Re: Does ASoC support sound card with multiple interfaces?
Date: Wed, 4 Jan 2012 12:33:39 +0530 [thread overview]
Message-ID: <4F03F9CB.20407@st.com> (raw)
In-Reply-To: <1325660401.12508.113.camel@matrix>
On 1/4/2012 12:30 PM, Ashish Chavan wrote:
>
>> You need to redirect it . You can use
>>
>> aplay -Dplughw:0,1 x.wav.
>>
>> Here '0' indicated card number and '1' indicates device number
>
> Is it really mandatory to specify card and device id? Isn't there a
> middle layer that takes care of using "first free" interface for
> playback or recording, if interface is not explicitly specified? As we
> register DAIs with ALSA subsystem, it should be fairly easy for alsa-lib
> to find out "first free" interface.
>
> I am aware that this wouldn't be practically useful in most cases,
> because generally we know beforehand which specific interface to be used
> for playback/recording. In such cases, automatic selection of interface
> may be confusing to users. But I just want to confirm if this is at all
> possible?
>
>
AFAIK, automatic selection is not there
~Rajeev
next prev parent reply other threads:[~2012-01-04 7:04 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
2012-01-04 5:47 ` Rajeev kumar
2012-01-04 7:00 ` Ashish Chavan
2012-01-04 7:03 ` Rajeev kumar [this message]
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=4F03F9CB.20407@st.com \
--to=rajeev-dlh.kumar@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashish.chavan@kpitcummins.com \
--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 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).