All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Stuart Longland <redhatter@gentoo.org>
Cc: tiwai@suse.de,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Justin Xu <justin.oxu@gmail.com>
Subject: Use Case Manager Test Drive [Was: Re: ASoC: Hiding unused CODEC mixer widgets in the machine driver]
Date: Fri, 06 Aug 2010 12:42:43 +0100	[thread overview]
Message-ID: <1281094963.3077.59.camel@odin> (raw)
In-Reply-To: <1281094453.3077.46.camel@odin>

On Fri, 2010-08-06 at 12:34 +0100, Liam Girdwood wrote:
> On Fri, 2010-08-06 at 12:19 +0100, Mark Brown wrote:
> > On Fri, Aug 06, 2010 at 10:18:45AM +1000, Stuart Longland wrote:
> > 
> > > Work has continued on the TLV320AIC3204 CODEC driver, and there have
> > > been a number of fixes since the last patch was published.  However,
> > > this CODEC is a rather complicated beast to drive, some may find the
> > > controls a little unweildy, and as such, I was wondering if the machine
> > > driver could be used to abstract this for a given target?
> > 
> > The machine driver shouldn't be doing this - it's too fragile in the
> > face of any changes in the drivers and means hard coding use cases into
> > the kernel which is really bad practice since it's much slower than
> > doing things from user space and much harder to change as new needs
> > arise.
> > 
> > Much of this should be being handled by use case management anyway, even
> > the controls that actually exist usefully on a given system are normally
> > way more detail than end applications should ever be seeing.  See
> > 
> > 	http://www.slimlogic.co.uk/?p=40
> > 
> > for the API which should deal with that.  
> > 
> 
> Please do give UCM (Use Case Manager) a test drive. We are in the late
> development / early testing phase before upstreaming (still one or two
> things todo).
> 
> You will need to checkout the use-case-verb branches of :-
> 
> git://git.slimlogic.co.uk/alsa-lib.git
> 
> git://git.slimlogic.co.uk/alsa-utils.git
> 
> There is a tool called alsaucm that allows changing the use case from
> the command line. Best to use it's interactive (-i) mode atm.
> 
> There is also an initial repository for UCM use case configuration files
> here :-
> 
> git://git.slimlogic.co.uk/alsa-ucm-conf.git
> 
> This will show the format required to describe use cases.
> 

Forgot to add that patches are most welcome.

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

  reply	other threads:[~2010-08-06 11:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06  0:18 ASoC: Hiding unused CODEC mixer widgets in the machine driver Stuart Longland
2010-08-06 11:19 ` Mark Brown
2010-08-06 11:34   ` Liam Girdwood
2010-08-06 11:42     ` Liam Girdwood [this message]
2010-08-07 23:07       ` Use Case Manager Test Drive [Was: Re: ASoC: Hiding unused CODEC mixer widgets in the machine driver] Stuart Longland
2010-08-08  9:25         ` Liam Girdwood

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=1281094963.3077.59.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=justin.oxu@gmail.com \
    --cc=redhatter@gentoo.org \
    --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 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.