On Thu, Dec 6, 2012 at 7:32 AM, Guenter Roeck <[email protected]> wrote:
> Create a 'debounce' attribute if debounce is supported by the gpio > chip and a gpio pin is exported. > > Signed-off-by: Guenter Roeck <[email protected]> Can you describe the usecase for this? I have this problem when working as a back-up GPIO maintainer that I don't really understand the userspace apps doing this. I would guess something like a userspace app reading a GPIO switch and needing to set this to avoid key bounces, but it'd be nice to know if this is really the case. If this is the usecase I am slightly concerned why these are not used: drivers/input/keyboard/gpio_keys_polled.c drivers/input/keyboard/gpio_keys.c The latter even uses the in-kernel debounce interface. I'd agree if this is not user input at all but something like a switch in a factory production line. So please help me understand this. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
