> One of the earlier examples of why to want debouncing (in the > original discussion, not this one) was for buttons (one signal > per button press) and the hardware designers don't necessarily > hook buttons up to only GPIOs with hardware debounce. So code > to kick in debounce there needed to be sensitive to whether or > not the capability was available ... and moreover, whether the > debounce scale was adequate to compensate the contact chatter. > When not, then software debounce was inescapable. And someone who needs it can contribute it. The proposed patch causes no problems in this area. Alan -- 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
