From: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [RFC] Extra info via the TLV interface
Date: Mon, 04 Sep 2006 14:14:13 +0100 [thread overview]
Message-ID: <1157375653.2772.61.camel@localhost.localdomain> (raw)
In-Reply-To: <44FC20B0.4060501@superbug.co.uk>
On Mon, 2006-09-04 at 13:48 +0100, 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.
Agreed, it would also be nice to know about sidetone/bypass.
> 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.
Fwiw, I've created a patch for ASoC that uses the audio routing map
(includes how controls are linked to other controls) within ASoC to
enable easy scenario setting. This allows a route to be be automatically
created (and powered) by specifing the source and sink e.g.
"Left DAC" --> "Left Headphone"
It wouldn't be difficult to add code here that could also specify the
active controls for that route. i.e. active route controls could be
highlighted to make using the mixer tools easier.
If anyone is interested, patch is here:-
http://www.rpsys.net/openzaurus/patches/alsa/asoc-scenario-v0.3.patch
Atm, it's ASoC only as it requires a map of the machine audio subsystem.
> 4) Both "short" and "long" mixer control names.
> 5) Control grouping. I.e. to have mixer controls "Front" and "Surround"
> next to each other.
>
> I know (1) sort of works just by adding playback or capture to the
> control name, but it seems to fail in some ambiguous cases. E.g.
> "Capture feedback", "Mic Boost", "HD Source", "HD Channel"
>
> Any comments?
>
I'd also like to pass in log time values for ALC/AGC.
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:14 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
2006-09-04 13:14 ` Liam Girdwood [this message]
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=1157375653.2772.61.camel@localhost.localdomain \
--to=liam.girdwood@wolfsonmicro.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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.