From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: UCM updates and fixes
Date: Tue, 11 Jan 2011 17:08:02 +0000 [thread overview]
Message-ID: <1294765682.3338.24.camel@odin> (raw)
In-Reply-To: <alpine.LNX.2.00.1101111743420.28150@eeebox2.perex-int.cz>
On Tue, 2011-01-11 at 17:46 +0100, Jaroslav Kysela wrote:
> On Tue, 11 Jan 2011, Liam Girdwood wrote:
>
> > On Tue, 2010-12-21 at 22:11 +0000, Liam Girdwood wrote:
> >> Jarolsav,
> >>
> >> This fixes the remaining issues I can currently see in the alsa-lib
> >> ucm branch. It also includes a patch to execute commands, although I
> >> dont know if this is what you had in mind for exec.
> >>
> >> I've also done quite a bit of testing now. What is your merge plan for
> >> UCM ? We really need UCM merged soon as there are many users who
> >> depend on it.
> >>
> >
> > Have you had a chance to look over this patch series yet ?
>
> Your patches are in my branch. Thank you. I'm actually thinking about more
> inline functions in use-case.h header file like snd_use_case_card_list() to help
> application developers. But I'm having mixed feelings about this right
> now. What do you think?
My feelings are we go for a release now and make the relevant functions
inline later. We currently have a lot of folks needing UCM upstream now
to delay much longer.
I have one more small fix pending from Samsung, will send shortly.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2011-01-11 17:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 22:11 UCM updates and fixes Liam Girdwood
2010-12-21 22:11 ` [PATCH 01/11] ucm: removed unused 'active' member in struct use_case_device Liam Girdwood
2010-12-21 22:11 ` [PATCH 02/11] ucm: modifiers names must be compound parse Liam Girdwood
2010-12-21 22:11 ` [PATCH 03/11] ucm: remove parse_device() and call parse_compound() directly Liam Girdwood
2010-12-21 22:11 ` [PATCH 04/11] ucm: implement basic script exec functionality Liam Girdwood
2010-12-21 22:11 ` [PATCH 05/11] ucm: make sure active modifier and device lists are initialised Liam Girdwood
2010-12-21 22:11 ` [PATCH 06/11] ucm: remove unused code Liam Girdwood
2010-12-21 22:11 ` [PATCH 07/11] ucm: check for valid value list before dereference Liam Girdwood
2010-12-21 22:11 ` [PATCH 08/11] ucm: check the correct return value for modifier Liam Girdwood
2010-12-21 22:11 ` [PATCH 09/11] ucm: only select modifier when supported device is enabled Liam Girdwood
2010-12-21 22:11 ` [PATCH 10/11] ucm: fix handling of cset with spaces in the control name Liam Girdwood
2010-12-21 22:12 ` [PATCH 11/11] ucm: ctlparse - always terminate cset buffer Liam Girdwood
2010-12-22 0:03 ` UCM updates and fixes Mark Brown
2011-01-11 16:43 ` Liam Girdwood
2011-01-11 16:46 ` Jaroslav Kysela
2011-01-11 17:08 ` Liam Girdwood [this message]
2011-01-11 17:12 ` Jaroslav Kysela
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=1294765682.3338.24.camel@odin \
--to=lrg@slimlogic.co.uk \
--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).