From: Liam Girdwood <lrg@slimlogic.co.uk>
To: pl bossart <bossart.nospam@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Stephen Warren <swarren@nvidia.com>,
"Mark Brown (broonie@opensource.wolfsonmicro.com)"
<broonie@opensource.wolfsonmicro.com>,
"jiesun@chromium.org" <jiesun@chromium.org>,
Liam Girdwood <lrg@ti.com>
Subject: Re: UCM files for tegra-wm8903 on seaboard
Date: Sat, 21 May 2011 16:48:20 +0100 [thread overview]
Message-ID: <1305992900.3317.16.camel@odin> (raw)
In-Reply-To: <BANLkTi=3n1P7V_TOdOzGY0dX9jO5ri9cQA@mail.gmail.com>
On Thu, 2011-05-19 at 14:22 -0500, pl bossart wrote:
> >> 2) In the ChromeOS kernel, there's a separate PCM for playback to WM8903
> >> and playback to the SPDIF controller, and hence on to HDMI. Since these
> >> use different values for PlaybackPCM, I defined separate use-cases for
> >> analog and HDMI/SPDIF playback. Is this the typical way of splitting
> >> things up, or would one typically have a unified use-case with the
> >> PlaybackPCM Value being part of the SectionDevice?
> >
> > If the use case is the same, e.g. "Music", I would just add them as different Music devices and have a PlaybackPCM for each of them.
>
> Looks like Stephen and I share the same questions.
> If we have a single "Music" use case with multiple PCM playback
> devices (in the ALSA sense hw:x,y) listed the same file, how would one
> specify that for example the UCM headphone or speaker devices are
> valid only for the WM8903 output?
Do you mean here that the headphones or speaker are only valid with a
WM8903 PCM i.e. hw0,0 ? If so, I would use the PlaybackPCM tag to
identify that the valid PCM device.
> I am struggling a bit to link Devices as defined by UCM (headset,
> earpiece, etc) and Devices as defined by ALSA...for example I am not
> sure what the cdev statement means in the device definition.
> Confused...
> -Pierre
Sorry, there is a little overlap here with naming. Devices wrt to ALSA
mean the PCM device or card device i.e. the cdev refers the to the sound
card (Jaroslav, pls correct me if I'm wrong here with the cdev naming).
UCM treats devices as the physical audio transducers (like speakers,
headphones, mic, etc).
Liam
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2011-05-21 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 22:40 UCM files for tegra-wm8903 on seaboard Stephen Warren
2011-05-19 13:19 ` Liam Girdwood
2011-05-19 19:22 ` pl bossart
2011-05-21 15:48 ` Liam Girdwood [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=1305992900.3317.16.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bossart.nospam@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jiesun@chromium.org \
--cc=lrg@ti.com \
--cc=swarren@nvidia.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 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.