summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/board-rx51.c
diff options
context:
space:
mode:
authorKevin Hilman <khilman@deeprootsystems.com>2009-04-23 11:10:49 -0700
committerTony Lindgren <tony@atomide.com>2009-04-23 11:10:49 -0700
commitb3bb4f688c225d9455bbd59e98f634f98c1074d0 (patch)
treec5ee29d52785791fbba001dbe65e65f524fb3619 /arch/arm/mach-omap2/board-rx51.c
parentd94a2eddf50c4aa1553acf3025f45d03704a1f97 (diff)
downloadop-kernel-dev-b3bb4f688c225d9455bbd59e98f634f98c1074d0.zip
op-kernel-dev-b3bb4f688c225d9455bbd59e98f634f98c1074d0.tar.gz
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>
Diffstat (limited to 'arch/arm/mach-omap2/board-rx51.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud