From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Pedro I. Sanchez" <psanchez@colcan.ca>
Cc: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>, alsa-devel@alsa-project.org
Subject: Re: How to support multiple audio codecs on a single?board
Date: Mon, 31 Aug 2009 21:10:40 +0100 [thread overview]
Message-ID: <20090831201040.GA4079@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <2562dcd3427ea040da0cb1365c7f5184@colcan.ca>
On Mon, Aug 31, 2009 at 01:25:39PM -0400, Pedro I. Sanchez wrote:
> On Mon, 31 Aug 2009 14:16:06 +0100, Mark Brown
> > For now you'll need to write three machine drivers only one of which is
> > permitted to be loaded at once; once the core has this support added
> > you'll then be able to load all three at once and have the three appear
> > as separate sound cards. If you'd like to contribute the core support
> > that'd be excellent :)
> What if the codecs are different? My board has a playback-only device
> (TAS5709) and a capture-only device (PCM1800). Would it be OK to implement
> a single machine driver with num_dai=2? Or would you suggest to implement
> two different sound cards?
It only depends on what's idiomatic for your system - if your system
makes most sense with them both as part of the same sound card then do
that, if it makes more sense with them split into two cards then that
would be better. When ASoC supports this properly it should be happy
with either configuration.
next prev parent reply other threads:[~2009-08-31 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 9:18 How to support multiple audio codecs on a single board Aggarwal, Anuj
2009-08-31 13:16 ` Mark Brown
2009-08-31 17:25 ` Pedro I. Sanchez
2009-08-31 20:10 ` Mark Brown [this message]
2009-08-31 21:14 ` How to support multiple audio codecs on a single?board Pedro I. Sanchez
2009-08-31 21:21 ` Pedro I. Sanchez
2009-08-31 17:30 ` How to support multiple audio codecs on a single board Pedro I. Sanchez
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=20090831201040.GA4079@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=psanchez@colcan.ca \
/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.