From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: pl bossart <bossart.nospam@gmail.com>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: UCM questions
Date: Fri, 21 Jan 2011 16:43:29 +0000 [thread overview]
Message-ID: <20110121164329.GB6200@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTinxwo_GErQroF4S-_z3G0UyT2sD4nBVbXVJz122@mail.gmail.com>
On Fri, Jan 21, 2011 at 09:12:51AM -0600, pl bossart wrote:
> > The device/use case names there are just defaults, systems can add their
> > own. The default set of use cases and devices are likely to handle
> > most cases but there's going to be a dependence on the system
> > integration.
> I am fine with a system-specific configuration file for each use case,
> but if I have to change the defines in alsa-lib it's a bit of a pain.
> It'll imply branches and specific packages just for a stupid include
> file.
If the define isn't there you should just be able to use a string - no
need to update the header file unless the thing being added is
sufficiently general that it seems like a good idea.
> >> - has anyone generated a typical configuration file for USB and
> >> HDAudio? I only see an OMAP conf.
> > Someone asked this at LPC as well - my thought there is that probably
> > PC systems would be happier trying to work without explicit use case
> > configuration as they are currently.
> Humm, not sure people are totally happy with audio on Linux PC
> systems... we still don't have a simple solution for
> routing/configuration/policy, UCM could provide simple hooks for users
> (or PulseAudio) to do what they do most, e.g for a voice call the
> headset is used while for movies the HDMI output is used.
It's certainly useful for overriding the default behaviour - I'm more
worried about the idea of using it for the default.
next prev parent reply other threads:[~2011-01-21 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 22:06 UCM questions pl bossart
2011-01-21 11:37 ` Mark Brown
2011-01-21 15:12 ` pl bossart
2011-01-21 16:43 ` Mark Brown [this message]
2011-01-21 20:53 ` pl bossart
2011-01-21 23:37 ` Liam Girdwood
2011-01-22 5:22 ` Raymond Yau
2011-01-23 0:41 ` Mark Brown
2011-01-23 13:49 ` Jaroslav Kysela
2011-01-21 15:24 ` Liam Girdwood
2011-01-21 21:03 ` pl bossart
2011-01-21 23:37 ` Liam Girdwood
2011-01-23 13:39 ` Jaroslav Kysela
2011-01-24 22:31 ` pl bossart
2011-01-25 12:13 ` Liam Girdwood
2011-01-25 21:58 ` pl bossart
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=20110121164329.GB6200@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=bossart.nospam@gmail.com \
--cc=lrg@slimlogic.co.uk \
/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.