Pavel Machek wrote: >>> Right now the states we have are On, Standby, and Suspend, and the CPU >>> runs only in the On state. But on some platforms there could be >>> multiple states in which the CPU is able to run, albeit with degraded >>> performance. >> I wouldn't call those system sleep states. For example, ACPI defines system >> sleep states as the states in which no instructions are executed by any CPUs >> and I think that's reasonable. > > Well, in some cases, we have 200MHz CPU running at 30kHz. ...that's so > slow that it is pretty similar to ACPI sleep state. > Pavel, let's do not mix the things. Rafael gave exact meaning of a sleep state -- "no instructions are executed by any CPUs", that, I assume, can be interpreted as "processor does not do any effective job". It does not mean if any clock frequency supplied or not. In some cases the frequency supplied to speed up the wakeup process, but, the processor can't operate on this frequency, so this is a sleep state. But, if the processor can do some job, even if a frequency very very slow, then this is an active mode. Regards, Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
