From: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>,
James Courtier-Dutton <James@superbug.co.uk>
Subject: Re: [RFC] Extra info via the TLV interface
Date: Mon, 04 Sep 2006 14:30:19 +0100 [thread overview]
Message-ID: <1157376619.2772.74.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0609041455110.9339@tm8103.perex-int.cz>
On Mon, 2006-09-04 at 15:04 +0200, Jaroslav Kysela wrote:
> On Mon, 4 Sep 2006, James Courtier-Dutton wrote:
>
> > Hi,
> >
> > I would like to now pass extra info regarding the controls via the TLV
> > interface.
> > 1) Whether the control is Playback, Capture or Both.
> > 2) Whether the control is digital or analog.
> > 3) Some description of the routing of the control. i.e. how it links to
> > other controls.
> > 4) Both "short" and "long" mixer control names.
> > 5) Control grouping. I.e. to have mixer controls "Front" and "Surround"
> > next to each other.
>
> In my opinion, all these GUI hints should be elsewhere (userspace),
> otherwise we'll end up with drivers containing digital photos of
> sound chips in the TLV structure :-)
>
We've almost got a "digital photo" of each sound chip in ASoC atm. It's
good for a few things (including GUI hints) :-
o Power Management. Knowing when to enable/disable individual chip and
machine audio components (based on any active streams and current mixer
settings).
o Scenario setting. Allowing a route to be set from source to sink
within a machine. I'd like to eventually have some kind of scenario
description in the card conf file for each use case.
Atm, the audio map is within the driver code, but it could eventually be
moved into userspace. The only question is whether the PM will work well
in userspace.
Liam
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-09-04 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 12:48 [RFC] Extra info via the TLV interface James Courtier-Dutton
2006-09-04 13:04 ` Jaroslav Kysela
2006-09-04 13:30 ` Liam Girdwood [this message]
2006-09-04 13:14 ` Liam Girdwood
2006-09-04 14:13 ` Takashi Iwai
2006-09-04 15:31 ` James Courtier-Dutton
2006-09-04 15:42 ` Takashi Iwai
2006-09-05 6:30 ` Jaroslav Kysela
2006-09-05 10:44 ` Takashi Iwai
2006-09-05 15:32 ` Jaroslav Kysela
2006-09-05 15:37 ` Takashi Iwai
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=1157376619.2772.74.camel@localhost.localdomain \
--to=liam.girdwood@wolfsonmicro.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.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 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.