aboutsummaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2013-10-29 17:57:31 +0900
committerSimon Horman <horms+renesas@verge.net.au>2013-12-10 17:24:22 +0900
commit478e2f9ca5ac9862a5cac0798814ba7d6a5de002 (patch)
treed79d407f3510830bfc5f6d073b779bc8ba6af5b0 /arch
parentc9fd77d48a72d4210c992c4ee27ef8217a44da03 (diff)
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 <shinya.kuribayashi.px@renesas.com> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/mach-shmobile/board-koelsch.c3
1 files changed, 2 insertions, 1 deletions
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"),