gpio/omap4: Fix missing interrupts during device wakeup due to IOPAD.
If gpio pins from bank[2-5] are marked as wakeup enable and if the wake is through gpio IO pad wakeup, then that wakeup gpio interrupt is lost. In the current implementation, GPIO driver stores the context of DATAIN of all the gpio in the bank. During GPIO resuming, it checks DATAIN with wakeup enabled pins of gpio bank. If there is status change, then manually toggle GPIO_LEVELDETECT to generate pseudo interrupt. Reported-by: Philippe Mazet <p-mazet@ti.com> Tested-by: Philippe Mazet <p-mazet@ti.com> Signed-off-by: Ambresh K <ambresh@ti.com> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
This commit is contained in:
parent
2c53b436a3
commit
55b220cafa
|
@ -469,8 +469,9 @@ static inline void set_24xx_gpio_triggering(struct gpio_bank *bank, int gpio,
|
|||
+ OMAP24XX_GPIO_CLEARWKUENA);
|
||||
}
|
||||
}
|
||||
/* This part needs to be executed always for OMAP34xx */
|
||||
if (cpu_is_omap34xx() || (bank->non_wakeup_gpios & gpio_bit)) {
|
||||
/* This part needs to be executed always for OMAP{34xx, 44xx} */
|
||||
if (cpu_is_omap34xx() || cpu_is_omap44xx() ||
|
||||
(bank->non_wakeup_gpios & gpio_bit)) {
|
||||
/*
|
||||
* Log the edge gpio and manually trigger the IRQ
|
||||
* after resume if the input level changes
|
||||
|
|
Loading…
Reference in a new issue