On Fri, 19.06.09 10:04, Takashi Iwai (tiwai@xxxxxxx) wrote: > Hi, > > 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. > > I think this is a sort of feature Lennart wanted for PA. > Lennart, does it make sense? Yes. I think it would. Also, if we can use the name of a control to find the jack sensing control for it this would be great. I.e. if we have a control "Headphone" and the Jack sensing control for it would then be called "Headphone Jack" or so, this would be great! Right now the only way to identify the purpose of a mixer element is by knowing it and going by the name. Would be good if that would be made easy for jack sensing controls. This also relieves us a bit from the little ugliness of having to manage permissions for those input devices differently from other input devices. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
