On Thu, Jul 17, 2008 at 11:31:12AM +0100, Mark Brown wrote: > On Wed, Jul 16, 2008 at 12:36:06PM -0400, Dmitry Torokhov wrote: > > On Wed, Jul 16, 2008 at 01:50:53PM +0100, Mark Brown wrote: > > > > As well as detecting the presence of a connected device typical jack > > > detection implementations also support the implementation of at least > > > one button which would require an input device for at least some jacks > > > It really depends on what you can do with this button. If it is just a > > simple circuit breaker then it is not really an input device. However > > is you can remap it for different purposes or map a regular key on a > > keybaord to perform this function then I will agree with you. For example > > As far as the hardware is concerned it's just a button - if it's visible > to software then there's no fixed function for it and any action taken > will be application/system specific. There will normally be a side > effect in hardware muting the microphone but that's not intended to be > the main effect. Ok, let's add it to the input subsystem then. If we see lots of switch types sprnging up we cam talk about the new subsystem again. I added the switch definition to input.h and it shoudl hit the mainline when I ask Linus to pull early next week. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
