On Wed, Apr 21, 2010 at 5:07 PM, Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> wrote: > Mike Chan <mike@xxxxxxxxxxx> writes: > >> IO events can also come from GPIO modules, which reside in the PER domain. >> It is possible for the PER to enter RET while CORE is still in ON. >> If GPIO 2-6 are enabled for IO-pad wakeups, the PER domain will not >> wakeup in this case, unless we enable it. >> >> Signed-off-by: Mike Chan <mike@xxxxxxxxxxx> > > Hi Mike, > > I'm a little puzzled on this one. My understanding is that the IO pad > is only armed when CORE is in RET or OFF. > The issue we are seeing is when the device is active but idle, if CORE is ON and PER is in RET and the omap is sitting in swfi. If the user presses a keypad button, IO pad doesn't wake us out of idle. Setting a wakeup if PER or CORE goes into RET solve this. > I need to dig a little more in the TRM on this one to clarify. > I was looking at 4.11.2.2 I/O Wake-Up Mechanism (pg 421) > If CORE is staying on, it might be that your GPIO module level wakeups > are not being configured correctly. Please check the 'Known Problems' > section of the OMAP PM wiki[1], search for 'GPIO module-level wakeups' > I will check to see if we have somethign mis-configured. -- Mike > Kevin > > [1] http://elinux.org/OMAP_Power_Management#Known_Problems > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
