From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 0/3] alsa-lib: UCM - Use Case Manager
Date: Wed, 25 Aug 2010 11:43:03 +0100 [thread overview]
Message-ID: <1282732983.2991.161.camel@odin> (raw)
In-Reply-To: <alpine.LNX.2.00.1008251128140.10278@eeebox2.perex-int.cz>
On Wed, 2010-08-25 at 11:35 +0200, Jaroslav Kysela wrote:
> On Wed, 25 Aug 2010, Liam Girdwood wrote:
>
> >> Next step may be to support the 'amixer' like syntax for the control and
> >> mixer element handling.
> >
> > Btw, we need to try and avoid using the control ID in any mixer syntax.
> > I found that minor driver changes could change ID numbering meaning
> > major updates to config files. The mixer names are pretty constant and
> > using them has been quite painless.
>
> Definitely. I meant the full control identifier (not just numid).
>
btw, have started any of the other API changes in use-case.c yet ?
I could make changes to the parser .....
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-08-25 10:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 16:17 [PATCH 0/3] alsa-lib: UCM - Use Case Manager Liam Girdwood
2010-08-23 16:17 ` [PATCH 1/3] ucm: header - ALSA " Liam Girdwood
2010-08-24 19:09 ` Chris Winter
2010-08-24 20:34 ` Liam Girdwood
2010-08-23 16:17 ` [PATCH 3/3] ucm: build - add build support for " Liam Girdwood
2010-08-23 17:47 ` [PATCH 0/3] alsa-lib: UCM - " Jaroslav Kysela
2010-08-23 17:50 ` Mark Brown
2010-08-23 17:51 ` Mark Brown
2010-08-24 9:09 ` Liam Girdwood
2010-08-25 8:28 ` Jaroslav Kysela
2010-08-25 9:26 ` Liam Girdwood
2010-08-25 9:35 ` Jaroslav Kysela
2010-08-25 10:43 ` Liam Girdwood [this message]
2010-08-25 16:34 ` Jaroslav Kysela
[not found] ` <1283864698.3048.26.camel@odin>
2010-09-07 14:42 ` Jaroslav Kysela
2010-09-07 15:53 ` Mark Brown
2010-09-07 18:17 ` Jaroslav Kysela
2010-09-07 18:53 ` Mark Brown
2010-09-08 7:54 ` Jaroslav Kysela
2010-09-08 9:47 ` Mark Brown
2010-09-08 8:19 ` Jaroslav Kysela
2010-09-09 12:16 ` Mark Brown
2010-09-07 20:02 ` Liam Girdwood
2010-09-07 22:43 ` Mark Brown
2010-09-20 16:26 ` Colin Guthrie
2010-09-21 17:13 ` Chris Winter
2010-09-21 17:40 ` Mark Brown
2010-09-21 18:11 ` Jaroslav Kysela
2010-09-22 11:47 ` Colin Guthrie
2010-09-22 13:20 ` Mark Brown
2010-09-22 14:06 ` Jaroslav Kysela
2010-09-22 15:14 ` Mark Brown
2010-09-22 18:05 ` Jaroslav Kysela
2010-09-22 18:48 ` Mark Brown
2010-09-23 7:18 ` Niels Mayer
2010-09-23 10:06 ` Mark Brown
2010-09-25 13:07 ` Colin Guthrie
2010-09-22 15:20 ` Liam Girdwood
2010-08-24 1:23 ` Raymond Yau
2010-08-24 9:41 ` 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=1282732983.2991.161.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--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 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).