| commit | 49c2b52334a8cd6a62229d0ccdb3214f3bec33c3 | |
| author | Kevin Hilman <khilman@deeprootsystems.com> | |
| Tue, 7 Apr 2009 22:27:39 +0000 (7 15:27 -0700) | ||
| committer | Tony Lindgren <tony@atomide.com> | |
| Tue, 7 Apr 2009 22:27:39 +0000 (7 15:27 -0700) | ||
| tree | 66434460dd979e10a28ddd8d06d253fd09740900 | treesnapshot (tar.gz zip) |
| parent | e7aa1abdaf070f144ac11352ea9b6b2da91dac38 | commitdiff |
OMAP2/3: GPIO: do not attempt to wake-enable
The GPIO IRQ enable/disable path attempts to also enable IRQ wake
support for the parent GPIO bank IRQ as well. However, since there is
no 'set_wake' hook for the bank IRQs, these calls will always fail.
Also, since the enable will fail on the suspend path, the disable on
the resume path will trigger unbalanced enable/disable warnings.
This was discovered in the suspend/resume path on OMAP3/Beagle using
the gpio-keys driver which disables/re-enables GPIO IRQ wakeups in the
suspend/resume path.
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
The GPIO IRQ enable/disable path attempts to also enable IRQ wake
support for the parent GPIO bank IRQ as well. However, since there is
no 'set_wake' hook for the bank IRQs, these calls will always fail.
Also, since the enable will fail on the suspend path, the disable on
the resume path will trigger unbalanced enable/disable warnings.
This was discovered in the suspend/resume path on OMAP3/Beagle using
the gpio-keys driver which disables/re-enables GPIO IRQ wakeups in the
suspend/resume path.
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
| arch/arm/plat-omap/gpio.c | diffblobblamehistory |