On Thu, Feb 17, 2011 at 10:41:52AM +0000, Lorenzo Pieralisi wrote: > When calling suspend from cpuidle, do you flush the stack (ie CPU > context) from L2 using outer_cache functions ? This has to be done when > one CPU is shut down with L2 enabled for the MMU off resume path to work > properly. > I think that on resume you invalidate L1 in the reset vector before > jumping to cpu_resume, correct ? Let's forget cpuidle using this code for the time being - the issues there appear to be more complex than the suspend-to-ram which this code is currently being used for. What I'm saying is that cpuidle using this is an enhancement over and above its current use. Once we have the S2R stuff working and tested, then we can go back to cpuidle stuff. I fear that trying to get this to work for cpuidle will result in the entire thing being thrown away. -- 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
