Hi! > > > > > Not only. This also includes "standby". > > > > > > > > Whatever it includes - please tell it to the user in the prompt. > > > > > > > > Technical issues are important, but it's often forgotten how many > > > > problems people run into because the description of a kconfig option > > > > could have been better. > > > > > > Sure. Please see the updated patch I've just sent. :-) > > > > So are you guys using: > > > > "standby" = idle state, ~0.5 seconds > > "suspend" = sleep to ram, ~10 seconds > > "hibernate" = sleep to disk, ~30 seconds > > Something like this, but "suspend" is not reserved as a name of specific state. > > The second state is usually referred to as "suspend to RAM" or "STR" and is > denoted by "mem" in /sys/power/state, if implemented. Moreover, "standby" and > "mem" are both entered using the same code path, so they may generally be > referred to as "suspend" states. > > The times aren't strictly defined for "mem" and "standby", too. The general > rule is that the times for "mem" are greater then for "standby" and the power > drawn in "mem" is smaller than the power drawn in "standby", but the exact > values will always depend on the platform. Apart from this, if the platform > supports only one "suspend" state, it decides if that's "mem" or "standby". > > On ACPI systems "standby" and "mem" correspond to the S1 and S3 sleep states, > respectively. And I'd expect ~2seconds for both "standby" and "mem" on ACPI system. ACPI S1 is just "for windows ME compatibility, do not use" -- it draws too much power, and is not really faster. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
