From: Liam Girdwood <lrg@ti.com>
To: Tanu Kaskinen <tanuk@iki.fi>
Cc: Raymond Yau <superquad.vortex2@gmail.com>,
tiwai@suse.de, alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: How to define card specific pcm devices?
Date: Thu, 06 Sep 2012 18:18:34 +0100 [thread overview]
Message-ID: <1346951914.4893.6.camel@odin> (raw)
In-Reply-To: <CABS+qY3kEPr3aknPvTU+iRyGxSo2G_iDawv+fr7WBJrJQUO+2w@mail.gmail.com>
On Wed, 2012-09-05 at 12:24 +0100, Girdwood, Liam wrote:
> On 5 September 2012 06:41, Tanu Kaskinen <tanuk@iki.fi> wrote:
> On Wed, 2012-08-29 at 09:44 +0800, Raymond Yau wrote:
> > strictly speaking your mic is not a true stereo mic and the
> channel
> > map is [left, null] instead of the normal map [left,right]
> of line-in
> > or stereo mic
>
>
> I think specifying the channel map like you suggest would be a
> good
> solution. Supporting it would require some extra work in
> PulseAudio, but
> I think PulseAudio will anyway have to be extended to query
> the channel
> map information from UCM.
>
> Now the problem is that UCM doesn't provide the channel map
> information
> at all. Should the channel map be provided in the device
> "Value"
> section? Like this:
>
> SectionDevice."my-mono-mic" {
>
> ...
>
> Value {
> # Does this value become redundant if
> # the "CaptureChannelMap" value is added?
> CaptureChannels "2"
>
I would expect to see a "1" here unless we cannot open the pcm in mono
mode.
> # Channel names match the constants in
> # Takashi's proposed channel map API
> CaptureChannelMap "FL, NA"
> }
>
> }
This seems fine and should be a simple patch for UCM too. Pulsaudio
could use the map information/preference from UCM (like above) to
configure the driver using Takashi's new channel map API.
>
> Opinions? (Liam added to CC - am I right in that you should be
> CC'd in
> all UCM related discussions?)
Yes, please and Mark too (now on CC).
Thanks
Liam
>
next prev parent reply other threads:[~2012-09-06 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 11:25 How to define card specific pcm devices? Tanu Kaskinen
2012-08-17 14:50 ` Tanu Kaskinen
[not found] ` <CAN8cciYX4krbJvb9PWQFswAKq0AqiC_oh20n+NB2Ak=BF8Zgxw@mail.gmail.com>
2012-08-18 1:26 ` Raymond Yau
2012-08-18 4:09 ` Tanu Kaskinen
2012-08-24 4:20 ` Raymond Yau
2012-08-29 1:44 ` Raymond Yau
2012-09-05 5:41 ` Tanu Kaskinen
[not found] ` <CABS+qY3kEPr3aknPvTU+iRyGxSo2G_iDawv+fr7WBJrJQUO+2w@mail.gmail.com>
2012-09-06 17:18 ` Liam Girdwood [this message]
2012-09-07 9:03 ` Tanu Kaskinen
2012-09-07 9:35 ` Takashi Iwai
2012-09-08 8:04 ` Tanu Kaskinen
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=1346951914.4893.6.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=superquad.vortex2@gmail.com \
--cc=tanuk@iki.fi \
--cc=tiwai@suse.de \
/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.