On Wednesday 16 July 2014 06:02 PM, Tony Lindgren wrote: > * Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> [140716 05:14]: >> On 07/11/2014 08:41 AM, Tony Lindgren wrote: >>> >>> If the RX pin does not wake it up, you need to configure the >>> pinctrl-single entry for it, and configure that pin as a wake-up >>> interrupt. See the interrupts-extended entry in omap3-beagle-xm.dts. >> >> This does not help. Checking the manual, there is not something like >> PIN_OFF_WAKEUPENABLE for am33xx. There is just INPUT/OUTPUT, pull >> up/down + enabled/disabled and the mux_mode. For the interrupt, the HW >> referenced as omap3_pmx_core touches some bits in the pinmux register >> which do not exists on am33xx. > > Right, on am33xx there's no IO chain wake-up path. AFAIK the only way > to provide wake events on am33xx would be to mux the RX pin temporarily > to a GPIO input. And sounds like that may work only if the GPIO is > in the first GPIO bank that's always on. I don't know if the other > GPIO banks on am33xx can provide wake up events. No, they cannot. Thanks, Sekhar -- 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
