>Do you have any guesses what is wrong in Rajendras cpuidle >code? Is it that dma save/restore? At least I couldn't figure >it out from your patches.
Not sure, one possible cause is that cpuidle code is calling pwrdm_set_next_pwrst(), I recall having some issues if I tried calling this function within idle loop. Rest of the PM code is calling set_pwrdm_state(). I haven't really tried cpuidle too much, I just wanted to get suspend + dynamic idle work as the code in those is simpler => easier to get chip off state to work. -Tero -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
