From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>, Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC: Dynamic CODEC DAI
Date: Mon, 5 Dec 2011 11:49:35 +0000 [thread overview]
Message-ID: <20111205114935.GG11150@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4EDC712E.9040409@codeaurora.org>
On Sun, Dec 04, 2011 at 11:22:22PM -0800, Patrick Lai wrote:
> My problem has more to do with ability to form PCM device at run-time
> by grouping available slimbus ports at the CPU side and CODEC side
> after knowing number of channels required. Furthermore, the CODEC I am
> working on does not allow all mic inputs going to all audio interface
> capture ports. Unless application can provide the mic input it is
> interested before initiation of capture stream, it is hard to utilize
> very slimbus port on the CODEC. Do you have work in progress code on
> gitorious.org? Perhaps, I can take a look to understand more about your
> proposed design and see what I can leverage.
You get pretty much exactly the same problem on PCM links using TDM -
you can get a single link which you can combine into groups of channels
dynamically. For example, you might use two channels for speaker and
two for headphones or you might use those four plus another two for 5.1
speaker all depending on use case.
next prev parent reply other threads:[~2011-12-05 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 0:49 ASoC: Dynamic CODEC DAI Patrick Lai
2011-11-29 0:58 ` Patrick Lai
2011-11-29 1:19 ` Pierre-Louis Bossart
[not found] ` <000001ccae35$0122cf60$03686e20$@bossart@linux.intel.com>
2011-11-29 6:14 ` Patrick Lai
2011-11-29 21:20 ` Pierre-Louis Bossart
2011-11-29 13:49 ` Mark Brown
2011-12-02 2:56 ` Patrick Lai
2011-12-02 10:11 ` Liam Girdwood
2011-12-05 7:22 ` Patrick Lai
2011-12-05 11:49 ` Mark Brown [this message]
2011-12-02 11:45 ` 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=20111205114935.GG11150@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=plai@codeaurora.org \
/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).