From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org, abraham duenas <aduejazz@gmail.com>,
broonie@opensource.wolfsonmicro.com
Subject: Re: ALSA UCM
Date: Fri, 12 Nov 2010 15:41:20 +0000 [thread overview]
Message-ID: <1289576480.3480.101.camel@odin> (raw)
In-Reply-To: <alpine.LNX.2.00.1011101608250.29422@eeebox2.perex-int.cz>
On Wed, 2010-11-10 at 16:11 +0100, Jaroslav Kysela wrote:
> On Tue, 9 Nov 2010, abraham duenas wrote:
>
> > I'm getting the expected error ONLY for the last element: listed in
> > the EnableSequence field:
> > e.g:
> > ALSA lib main.c:137:(execute_sequence) cset not yet implemented:
> > 'name='DL2 Media Playback Volume' 90'
> > ALSA lib main.c:137:(execute_sequence) cset not yet implemented:
> > 'name='MUX_UL10' 10'
> >
> > i'll keep on digging as time permits :)
>
> I fixed the sequence parser. It should work now ok. So the only missing
> part is to add the 'snd_ctl_*' backend for cset commands. The parsing
> functions for ctl strings are available in my ucm branch now:
Is it the intention to reuse the cset functionality from amixer here ?
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-11-12 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 20:38 ALSA UCM abraham duenas
2010-11-04 10:09 ` Liam Girdwood
2010-11-04 12:57 ` abraham duenas
2010-11-04 17:09 ` Liam Girdwood
2010-11-04 18:31 ` Jaroslav Kysela
2010-11-04 18:34 ` Jaroslav Kysela
2010-11-04 18:47 ` Liam Girdwood
2010-11-04 18:52 ` Jaroslav Kysela
2010-11-04 19:07 ` Liam Girdwood
2010-11-05 21:23 ` abraham duenas
2010-11-06 12:26 ` Liam Girdwood
2010-11-09 16:54 ` abraham duenas
2010-11-10 15:11 ` Jaroslav Kysela
2010-11-12 15:41 ` Liam Girdwood [this message]
2010-11-12 16:25 ` Jaroslav Kysela
2010-11-12 16:42 ` Liam Girdwood
2010-11-12 16:55 ` Jaroslav Kysela
2010-11-12 17:28 ` 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=1289576480.3480.101.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=aduejazz@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
/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).