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

[Mark Brown <broonie@opensource.wolfsonmicro.com>]

On Fri, Jun 19, 2009 at 12:08:49PM +0200, Takashi Iwai wrote:

> Sorry, my wording was unclear.  Let me clarify: the input jack API is
> there and used as is now.  What I meant as "supersedes" is that the
> code to create and handle the input jack instances in HD-audio driver
> is generalized to one and used together with the control API.

Ah, OK - in that case it sounds like a great idea.  Normally superceding
something implies replacing it (so ALSA supercedes OSS).

> > > 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.

> > Including the colours (where reported) is often very helpful for
> > figuring out what's what.  The pictures manufacturers seem fond of using
> > for describing the jack functions aren't always models of clarity to the
> > general user.

> Yes, HD-audio spec gives such information, too.

It was HDA that I was thinking about.

> However, the verbose information like a color doesn't fit into the id
> string.  A better option would be through the additional TLV like dB
> scale.  I just considered but didn't write up yet.

Yeah, so long as the information is there it doesn't really matter how
it gets there.