From: Simon Horman Date: Tue, 29 Oct 2013 08:57:31 +0000 (+0900) Subject: ARM: shmobile: koelsch: set .debounce_interval X-Git-Tag: firefly_0821_release~176^2~4587^2~5^2~17 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=478e2f9ca5ac9862a5cac0798814ba7d6a5de002;p=firefly-linux-kernel-4.4.55.git ARM: shmobile: koelsch: set .debounce_interval In R-Car GPIO hardware block, 'chattering removal' feature can be enabled on GPIO-n-[3:0] pins, but it's not supported on rest of pins GPIO-n-[31:4]. Set an appropriate debounce interval, instead. We could confirm that spurious/unnecessary GPIO interrupts are prevented by this settings. Based on work for the lager board by Shinya Kuribayashi. Cc: Shinya Kuribayashi Signed-off-by: Simon Horman --- diff --git a/arch/arm/mach-shmobile/board-koelsch.c b/arch/arm/mach-shmobile/board-koelsch.c index 59fa0b975473..5b81a343c5f9 100644 --- a/arch/arm/mach-shmobile/board-koelsch.c +++ b/arch/arm/mach-shmobile/board-koelsch.c @@ -56,7 +56,8 @@ static const struct gpio_led_platform_data koelsch_leds_pdata __initconst = { /* GPIO KEY */ #define GPIO_KEY(c, g, d, ...) \ - { .code = c, .gpio = g, .desc = d, .active_low = 1 } + { .code = c, .gpio = g, .desc = d, .active_low = 1, \ + .debounce_interval = 20 } static struct gpio_keys_button gpio_buttons[] = { GPIO_KEY(KEY_4, RCAR_GP_PIN(5, 3), "SW2-pin4"),