On Fri, Sep 9, 2011 at 11:57 PM, Kevin Hilman <khilman@xxxxxx> wrote: > Keshava Munegowda <keshava_mgowda@xxxxxx> writes: > >> From: Kishon Vijay Abraham <kishon@xxxxxx> >> >> For ehci and ohci hwmods, the omap4 I/O wakeup capablity is enabled. >> for ehci in phy mode, >> - the DAT0 and DIR I/O pad is set as wakeup capable >> for ohci in serial mode >> - usbb*_mm_rxdp is set as I/O wakeup for 6 pin serial mode >> - usbb*_mm_rxrcv is set as I/O wakeup for 4 pin serial mode >> - usbb*_mm_txen is set as I/O wakeup for 3 pin serial mode >> - usbb*_mm_txdat is set as I/O wakeup for 2 pin serial mode >> >> Signed-off-by: Kishon Vijay Abraham <kishon@xxxxxx> >> Signed-off-by: Keshava Munegowda <keshava_mgowda@xxxxxx> > > What if the end user doesn't want this device to be a wakeup source? > > Currently, the IO pad wakeup for these pins is enabled unconditionally. > While having it enabled as a wakeup source by default is fine, it should > not generate wakeups if the user has disable them by doing: > > $ echo disabled > /sys/devices/.../power/wakeup OK, I will do this. keshava -- 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
