So I was looking at drivers/cpufreq/Kconfig, and wondering... Is there a specific reason why we have a 'choice' clause that allows selecting 'performance' or 'userspace' as the default governor, and no obvious way to select powersave, ondemand, or conservative as a default? Or was this an oversight I should cook up a patch for? Looks like the Kconfig and a bit of cut-n-paste in include/linux/cpufreq.h is all that's needed?
Attachment:
pgpfKyWOOzSeA.pgp
Description: PGP signature
- Follow-Ups:
- Re: cpufreq 'choice' Kconfig oddness in 2.6.22-rc6-mm1..
- From: Mattia Dongili <[email protected]>
- Re: cpufreq 'choice' Kconfig oddness in 2.6.22-rc6-mm1..
- Prev by Date: [2.6.22 regression fix] DLM must depend on SYSFS
- Next by Date: Re: state of stack patches
- Previous by thread: [2.6.22 regression fix] DLM must depend on SYSFS
- Next by thread: Re: cpufreq 'choice' Kconfig oddness in 2.6.22-rc6-mm1..
- Index(es):
 |