>>> Also, why a special class? Why not use the input layer for stuff like >>> this? >> >> In the particular case of headset detection, I originally considered >> using ALSA Jack mechanism (and Soc Jack wrapper), which uses input >> layer. You probably know about that already. >> >> - Generic ALSA Jack mechanism >> http://git.kernel.org/?p=linux/kernel/git/broonie/sound-2.6.git;a=blob;f=sound/core/jack.c;h=dd4a12dc09aa44f4c50c5b60f2cf5584c5635589;hb=632087748c3795a54d5631e640df65592774e045 >> >> - Wrapper for ALSA SoC drivers >> http://git.kernel.org/?p=linux/kernel/git/broonie/sound-2.6.git;a=blob;f=sound/soc/soc-jack.c;h=28346fb2e70c08033158920f4ae7a35032239762;hb=632087748c3795a54d5631e640df65592774e045 > > Yes, I do know of that, so why ignore it?
The only reason I chose the Android's Switch Class/Gpio driver is because it fully matches what HeadsetObserver expects in the uevent. I'll use ASoC mechanism instead, and modify HeadsetObserver accordingly. Thanks, -Misa --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
