Re: RFC: Jack-detection control elements on HD-audio

[Lennart Poettering <mznyfn@0pointer.de>]

On Fri, 19.06.09 10:54, Jaroslav Kysela (perex@perex.cz) wrote:

Heya,

> > yet another thing I've worked recently on is a bit more generalized
> > framework for jack-sense reporting for HD-audio.  This supersedes the
> > existing jack-sense reporting via the input layer.  In addition, it
> > gives the corresponding control elements.
> >
> > For example, you'll have "Jack HP-Out" (or a bit more verbose like
> > "Jack HP-Out at Ext Rear") control via control API as well as other
> > mixer controls.  This can notify when a jack is plugged/unplugged.
> > But, another big win is that you can read the current pin sense just
> > by reading this element.
> 
> Before definining such extension, I would really see to define standard 
> control names in Documentation/ControlNames.txt file. It seems to me that 
> most new drivers does not follow suggested naming. The document should be 
> reviewed, of course.

Oh yes, please!

I have recently reworked PA to control the mixer a bit more
comprehensively, including doing input source selection stuff and
suchlike. For that I made a little survey on all current drivers how
they name things. Was a bit disappointing, for example for "Input
Source"/"Capture Source" we have at least
options by these names:

Analog
Analog Inputs
AOUT
Aux
AUX
Aux0
Aux1
Aux2
Aux3
Aux In
AUX IN
Cam Mic
Digital Mic
Digital Mic 1
Digital Mic 2
D-Mic
Docking-Station
Dock Mic
e-Mic
E-Mic
ExtMic
Ext Mic
FM
Front Mic
Front Microphone
iMic
i-Mic
Input1
Input2
Int DMic
Internal Mic
Internal Microphone
IntMic
Int Mic
Line
LineIn
Line In
Line-In
Line/Mic
Mic
Mic1
Mic2
Mic/Line
Microphone
Rear Mic
TV Tuner
Unknown1
Unknown2
Video

Shouldn't be too difficult to agree on standard names for most of
these.

I'll post abit more about my findings later.

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4