On 04.04.2016 17:17, Linus Walleij wrote: > On Fri, Apr 1, 2016 at 1:00 PM, Cristina Ciocan > <cristina.ciocan@xxxxxxxxx> wrote: > >> Make debounce setting and getting functionality available when >> configurating a certain pin. >> >> Signed-off-by: Cristina Ciocan <cristina.ciocan@xxxxxxxxx> > > Patch applied. > > And as this is another case where GPIO has a debounce > setting call: gpiod_set_debounce() this is another case for > my suggested pinctrl_gpio_set_config() as that call is > currently not implemented in your corresponding .set_debounce() > callback for the GPIO chip, but could easily be handled > by calling back into the pinctrl back-end, right? > Yes, it can be easily handled by calling back byt_pin_config_set. I will look into what other options are often used and would make sense to be exported in the gpio layer as well and come back with a more detailed answer. Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html