Kai Weber wrote: > Michael Biebl wrote: > >>> The 94cpufreq hook in version 0.99.2 is wrong. It does always set the >>> performance governor on suspend. A quick look into the last release of >>> pm-utils (0.99.4) seems to have fixed this error. >> Why is that wrong? Using the performance governor is the most sensible >> choice over any over governor. > > Two reasons: > > 1) The user's configuration and preferences should not be ignored. > pm-utils should respect the configured governor or else any > configuration option for the governor (like you can configure it > directly as an option in the kernel or with help of a package like > cpufrequtils) is useless.
Sure, but the configured governor is restored on resume. So what's the problem? > 2) When it comes to energy/battery saving the performance governor is > the last sensible option. We want to suspend/hibernate as quickly as possible. Running 30 secs at fullspeed instead of 60 secs in battery saving mode, is likely not making a difference in the total energy consumption. So I'm totally for hibernating as quickly as possible. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
