From: Mark Brown <broonie(a)linaro.org>
It is reasonable for a driver using a GPIO to call set_debounce() on GPIOs
that don't provide this support in hardware since the driver can fall back
on a software debounce implementation or otherwise not depend on success
so downgrade the log message for this to a debug one.
Signed-off-by: Mark Brown <broonie(a)linaro.org>
---
drivers/gpio/gpiolib.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index b762718..374cf9e 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1779,8 +1779,8 @@ static int gpiod_set_debounce(struct gpio_desc *desc, unsigned debounce)
chip = desc->chip;
if (!chip->set || !chip->set_debounce) {
- pr_warn("%s: missing set() or set_debounce() operations\n",
- __func__);
+ pr_debug("%s: missing set() or set_debounce() operations\n",
+ __func__);
return -EIO;
}
--
1.8.4.rc3