ARM: OMAP2/3: GPIO: do not attempt to wake-enable
authorKevin Hilman <khilman@deeprootsystems.com>
Thu, 23 Apr 2009 18:10:49 +0000 (11:10 -0700)
committerTony Lindgren <tony@atomide.com>
Thu, 23 Apr 2009 18:10:49 +0000 (11:10 -0700)
commitb3bb4f688c225d9455bbd59e98f634f98c1074d0
treec5ee29d52785791fbba001dbe65e65f524fb3619
parentd94a2eddf50c4aa1553acf3025f45d03704a1f97
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>
arch/arm/plat-omap/gpio.c