From: Patrick Lai <plai@codeaurora.org>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: ASoC: Dynamic CODEC DAI
Date: Sun, 04 Dec 2011 23:22:22 -0800 [thread overview]
Message-ID: <4EDC712E.9040409@codeaurora.org> (raw)
In-Reply-To: <1322820685.7185.12.camel@odin>
On 12/2/2011 2:11 AM, Liam Girdwood wrote:
>
> Fwiw, I'm looking at a similar channel mapping problem here for dyanmic
> PCM and have the start of some working code. Basically I want to be able
> to specify which channels from each PCM device are routed through each
> DAI and DAPM widget.
>
Would you mind sharing the use case you have in mind? It is not clear
to me how your design proposal correlate to the problem I have in hand.
It looks to me that you are trying to address shuffling of pcm channels
correct me if I am wrong. For example, 5.1 content is composed with
certain speaker allocation in mind but the actual speaker allocation is
different. So, through the approach you are proposing, software can
rearrange the pcm channels according to actual speaker allocation.
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.
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-12-05 7:22 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 [this message]
2011-12-05 11:49 ` Mark Brown
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=4EDC712E.9040409@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.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).