> > Not all GPIOs have hardware debounce though, so > offering this > > capability sort of begs the question of where/how to > provide a software debounce mechanism too... > > how about adding a flag for supported features and if that > hardware doesn't support we simply return, Presense of a debounce method would suffice when gpiolib is in use (vs direct implementation of the API provided by gpiolib). > or fallback to > software emulation if chosen by the user. ISTR that if you look back to the original discussion about GPIO debouncing, you will find such a software implementation; and maybe such an integration ... -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html