summaryrefslogtreecommitdiffstats
path: root/drivers/gpio/gpio-msm-v2.c
diff options
context:
space:
mode:
authorLinus Walleij <linus.walleij@linaro.org>2013-09-04 14:17:08 +0200
committerLinus Walleij <linus.walleij@linaro.org>2013-09-04 14:22:47 +0200
commit65d876564e989b63b0f769e0e06b9830db97b2d9 (patch)
tree2549b0ba6ad1aa90f049cdc35ebf75ddd50b6271 /drivers/gpio/gpio-msm-v2.c
parentbe1a4b13089b1e18da83a549d49163ccad3c19ba (diff)
downloadlinux-65d876564e989b63b0f769e0e06b9830db97b2d9.tar.bz2
gpio: return -ENOTSUPP if debounce cannot be set
It appears some drivers are using gpio_set_debounce() opportunistically, i.e. without knowing whether it works or not. (Example: input/keyboard/gpio_keys.c) to account for this use case, return -ENOTSUPP and do not print any warnings in this case. Took a round over the other gpio_set_debounce() consumers to make sure that none of them are relying on the returned error code to be something specific. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/gpio/gpio-msm-v2.c')
0 files changed, 0 insertions, 0 deletions