| commit | ce2bcd529b1db26edf51c611ef9288e9fd5166e6 | |
| author | Kevin Hilman <khilman@deeprootsystems.com> | |
| Wed, 15 Apr 2009 17:44:52 +0000 (15 10:44 -0700) | ||
| committer | Tony Lindgren <tony@atomide.com> | |
| Wed, 15 Apr 2009 17:44:52 +0000 (15 10:44 -0700) | ||
| tree | f3f50f2b650d499c1ae0e1a04d411b6d8f6b6188 | treesnapshot (tar.gz zip) |
| parent | c094ba34b8f780885d029ce3c2715a194b780e5d | commitdiff |
ARM: 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 |