Vishwanath BS <vishwanath.bs@xxxxxx> writes: > As IO Daisy chain sequence is triggered via hwmod mux, there is no need to > control it from cpuidle path for OMAP3. > > Also as omap3_disable_io_chain is no longer being used, just remove the function. > > Signed-off-by: Vishwanath BS <vishwanath.bs@xxxxxx> > Tested-by: Govindraj.R <govindraj.raja@xxxxxx> In the TRM (4460 public TRM vM) it says: "The software must enable the I/O wakeup prior entering a low-power mode and disable it following a wake-up event." but after this series, once it's enabled, it is never disabled. What am I missing? Kevin -- 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
