Blackfin: don't support keypad wakeup from hibernate
authorMichael Hennerich <michael.hennerich@analog.com>
Thu, 25 Feb 2010 13:32:24 +0000 (13:32 +0000)
committerMike Frysinger <vapier@gentoo.org>
Tue, 9 Mar 2010 05:30:53 +0000 (00:30 -0500)
The on-chip keypad peripheral requires different registers to be setup
depending on the standby type (standby vs hibernation).  However, since
the power management framework doesn't differentiate between these types,
the driver doesn't know which registers to program and subsequently it
avoids doing so.

Always enabling the keyboard wakeup source causes misbehavior when the
pins are not assigned to the keypad.  If they happen to drive a certain
level, they'll trigger a wake up event which is not wanted.  So until
the aforementioned issue can be sorted out, drop support for the
wakeup source completely.

Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
arch/blackfin/mach-common/ints-priority.c

index 11c05f3e178b812123bd52d630e4a6b810a7a234..7ad8878bfa1815110a53220a1d96ab2c53df0476 100644 (file)
@@ -252,11 +252,6 @@ int bfin_internal_set_wake(unsigned int irq, unsigned int state)
        wakeup |= USBWE;
        break;
 #endif
-#ifdef IRQ_KEY
-       case IRQ_KEY:
-       wakeup |= KPADWE;
-       break;
-#endif
 #ifdef CONFIG_BF54x
        case IRQ_CNT:
        wakeup |= ROTWE;