Hi! > > You bring up a more interesting area to look at integrating > > sleep states and operating points. Can we add some hooks > > that allow us to define which operating point is selected at > > resume? Need to think about that a bit:) > --- > > It's an interesting question, and one we (Motorola) don't have hard > data to support, yet. Our current implementation remembers the OP > in use before sleeping and resumes at the same OP. The argument is > that this corresponds to an application that is doing work at a > steady-state level (say decoding video), but that has a brief pause > to wait for I/O or a timer (say, pausing until the next frame time); > then it makes sense that the level of effort required on resume will > be the same as before sleeping. We may have confusion here. On PC, it is definitely not possible to enter sleep state between frames of video... because video is powered off. On PC, sleep states are *system* sleep states. CPU sleep states exist, too, but that's in-kernel implementation detail. They are called C1..C4. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
