From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Rajeev kumar <rajeev-dlh.kumar@st.com>,
"; Liam Girdwood" <lrg@slimlogic.co.uk>
Subject: Re: Does ASoC support sound card with multiple interfaces?
Date: Thu, 5 Jan 2012 06:02:55 +0000 [thread overview]
Message-ID: <20120105060255.GF11867@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1325660401.12508.113.camel@matrix>
On Wed, Jan 04, 2012 at 12:30:01PM +0530, Ashish Chavan wrote:
> 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.
That's not implemented since genuinely identical interfaces should be
implemented by supporting multiple opens on a single device but those
essentailly don't exist in embedded hardware. Pretty much all embedded
hardware with multiple routes out of the CPU has either distinct fixed
functions for the outputs or independant routing of them so they can't
reliably be used interchangibly.
You could implement it but it'd have to be a system specific option to
use it.
prev parent reply other threads:[~2012-01-05 6:02 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
2012-01-05 6:02 ` Mark Brown [this message]
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=20120105060255.GF11867@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashish.chavan@kpitcummins.com \
--cc=lrg@slimlogic.co.uk \
--cc=rajeev-dlh.kumar@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).