On Sun, Jun 17, 2012 at 04:17:58PM +0200, Linus Walleij wrote: > From: Naveen Kumar Gaddipati <naveen.gaddipati@xxxxxxxxxxxxxx> > > The keypad could cause multiple interrupts to be fired in succession > since we weren't waiting for the IRQs to clear properly in the > interrupt handler. We ait for a number of bus iterations (the > readl():s from the peripheral bus will stall, so these are quite > long) before giving up on getting keys ready to read, then we > sleep until the IRQ is deasserted (this is OK since the interrupt > is threaded). Also use the debounce platform data for another > hardcoded wait loop. > > Signed-off-by: Naveen Kumar Gaddipati <naveen.gaddipati@xxxxxxxxxxxxxx> > Reviewed-by: Rikard Olsson <rikard.p.olsson@xxxxxxxxxxxxxx> > Reviewed-by: Srinidhi Kasagar <srinidhi.kasagar@xxxxxxxxxxxxxx> > Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx> Applied, thank you. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
