2011-05-20 06:51:07 +08:00
|
|
|
menu "CPU Frequency scaling"
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_FREQ
|
|
|
|
|
bool "CPU Frequency scaling"
|
|
|
|
|
help
|
|
|
|
|
CPU Frequency scaling allows you to change the clock speed of
|
|
|
|
|
CPUs on the fly. This is a nice method to save power, because
|
|
|
|
|
the lower the CPU clock speed, the less power the CPU consumes.
|
|
|
|
|
|
|
|
|
|
Note that this driver doesn't automatically change the CPU
|
|
|
|
|
clock speed, you need to either enable a dynamic cpufreq governor
|
|
|
|
|
(see below) after boot, or use a userspace tool.
|
|
|
|
|
|
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq>.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
|
|
|
|
if CPU_FREQ
|
|
|
|
|
|
2012-12-29 09:55:20 +08:00
|
|
|
config CPU_FREQ_GOV_COMMON
|
|
|
|
|
bool
|
|
|
|
|
|
2013-12-20 22:24:51 +08:00
|
|
|
config CPU_FREQ_BOOST_SW
|
|
|
|
|
bool
|
|
|
|
|
depends on THERMAL
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_FREQ_STAT
|
2007-04-19 04:18:13 +08:00
|
|
|
tristate "CPU frequency translation statistics"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This driver exports CPU frequency statistics information through sysfs
|
|
|
|
|
file system.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cpufreq_stats.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config CPU_FREQ_STAT_DETAILS
|
2007-04-19 04:18:13 +08:00
|
|
|
bool "CPU frequency translation statistics details"
|
|
|
|
|
depends on CPU_FREQ_STAT
|
|
|
|
|
help
|
|
|
|
|
This will show detail CPU frequency translation table in sysfs file
|
|
|
|
|
system.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Default CPUFreq governor"
|
2013-05-05 20:18:08 +08:00
|
|
|
default CPU_FREQ_DEFAULT_GOV_USERSPACE if ARM_SA1100_CPUFREQ || ARM_SA1110_CPUFREQ
|
2005-04-17 06:20:36 +08:00
|
|
|
default CPU_FREQ_DEFAULT_GOV_PERFORMANCE
|
|
|
|
|
help
|
|
|
|
|
This option sets which CPUFreq governor shall be loaded at
|
|
|
|
|
startup. If in doubt, select 'performance'.
|
|
|
|
|
|
|
|
|
|
config CPU_FREQ_DEFAULT_GOV_PERFORMANCE
|
|
|
|
|
bool "performance"
|
|
|
|
|
select CPU_FREQ_GOV_PERFORMANCE
|
|
|
|
|
help
|
|
|
|
|
Use the CPUFreq governor 'performance' as default. This sets
|
|
|
|
|
the frequency statically to the highest frequency supported by
|
|
|
|
|
the CPU.
|
|
|
|
|
|
2008-04-19 04:31:13 +08:00
|
|
|
config CPU_FREQ_DEFAULT_GOV_POWERSAVE
|
|
|
|
|
bool "powersave"
|
2011-01-21 06:44:16 +08:00
|
|
|
depends on EXPERT
|
2008-04-19 04:31:13 +08:00
|
|
|
select CPU_FREQ_GOV_POWERSAVE
|
|
|
|
|
help
|
|
|
|
|
Use the CPUFreq governor 'powersave' as default. This sets
|
|
|
|
|
the frequency statically to the lowest frequency supported by
|
|
|
|
|
the CPU.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config CPU_FREQ_DEFAULT_GOV_USERSPACE
|
|
|
|
|
bool "userspace"
|
|
|
|
|
select CPU_FREQ_GOV_USERSPACE
|
|
|
|
|
help
|
|
|
|
|
Use the CPUFreq governor 'userspace' as default. This allows
|
2008-12-30 05:14:56 +08:00
|
|
|
you to set the CPU frequency manually or when a userspace
|
2005-04-17 06:20:36 +08:00
|
|
|
program shall be able to set the CPU dynamically without having
|
|
|
|
|
to enable the userspace governor manually.
|
|
|
|
|
|
2007-10-03 04:28:12 +08:00
|
|
|
config CPU_FREQ_DEFAULT_GOV_ONDEMAND
|
|
|
|
|
bool "ondemand"
|
|
|
|
|
select CPU_FREQ_GOV_ONDEMAND
|
|
|
|
|
select CPU_FREQ_GOV_PERFORMANCE
|
|
|
|
|
help
|
|
|
|
|
Use the CPUFreq governor 'ondemand' as default. This allows
|
|
|
|
|
you to get a full dynamic frequency capable system by simply
|
|
|
|
|
loading your cpufreq low-level hardware driver.
|
|
|
|
|
Be aware that not all cpufreq drivers support the ondemand
|
|
|
|
|
governor. If unsure have a look at the help section of the
|
|
|
|
|
driver. Fallback governor will be the performance governor.
|
|
|
|
|
|
|
|
|
|
config CPU_FREQ_DEFAULT_GOV_CONSERVATIVE
|
|
|
|
|
bool "conservative"
|
|
|
|
|
select CPU_FREQ_GOV_CONSERVATIVE
|
|
|
|
|
select CPU_FREQ_GOV_PERFORMANCE
|
|
|
|
|
help
|
|
|
|
|
Use the CPUFreq governor 'conservative' as default. This allows
|
|
|
|
|
you to get a full dynamic frequency capable system by simply
|
|
|
|
|
loading your cpufreq low-level hardware driver.
|
|
|
|
|
Be aware that not all cpufreq drivers support the conservative
|
|
|
|
|
governor. If unsure have a look at the help section of the
|
|
|
|
|
driver. Fallback governor will be the performance governor.
|
2005-04-17 06:20:36 +08:00
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config CPU_FREQ_GOV_PERFORMANCE
|
2007-04-19 04:18:13 +08:00
|
|
|
tristate "'performance' governor"
|
|
|
|
|
help
|
2005-04-17 06:20:36 +08:00
|
|
|
This cpufreq governor sets the frequency statically to the
|
|
|
|
|
highest available CPU frequency.
|
|
|
|
|
|
2007-04-19 04:18:13 +08:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cpufreq_performance.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
If in doubt, say Y.
|
|
|
|
|
|
|
|
|
|
config CPU_FREQ_GOV_POWERSAVE
|
2007-04-19 04:18:13 +08:00
|
|
|
tristate "'powersave' governor"
|
|
|
|
|
help
|
2005-04-17 06:20:36 +08:00
|
|
|
This cpufreq governor sets the frequency statically to the
|
|
|
|
|
lowest available CPU frequency.
|
|
|
|
|
|
2007-04-19 04:18:13 +08:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cpufreq_powersave.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
If in doubt, say Y.
|
|
|
|
|
|
|
|
|
|
config CPU_FREQ_GOV_USERSPACE
|
2007-04-19 04:18:13 +08:00
|
|
|
tristate "'userspace' governor for userspace frequency scaling"
|
|
|
|
|
help
|
2005-04-17 06:20:36 +08:00
|
|
|
Enable this cpufreq governor when you either want to set the
|
2008-12-30 05:14:56 +08:00
|
|
|
CPU frequency manually or when a userspace program shall
|
2005-04-17 06:20:36 +08:00
|
|
|
be able to set the CPU dynamically, like on LART
|
2006-04-03 20:21:00 +08:00
|
|
|
<http://www.lartmaker.nl/>.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-04-19 04:18:13 +08:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cpufreq_userspace.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
For details, take a look at <file:Documentation/cpu-freq/>.
|
|
|
|
|
|
|
|
|
|
If in doubt, say Y.
|
|
|
|
|
|
|
|
|
|
config CPU_FREQ_GOV_ONDEMAND
|
|
|
|
|
tristate "'ondemand' cpufreq policy governor"
|
2012-12-29 09:55:20 +08:00
|
|
|
select CPU_FREQ_GOV_COMMON
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
'ondemand' - This driver adds a dynamic cpufreq policy governor.
|
|
|
|
|
The governor does a periodic polling and
|
|
|
|
|
changes frequency based on the CPU utilization.
|
|
|
|
|
The support for this governor depends on CPU capability to
|
|
|
|
|
do fast frequency switching (i.e, very low latency frequency
|
|
|
|
|
transitions).
|
|
|
|
|
|
2007-04-19 04:18:13 +08:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cpufreq_ondemand.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
For details, take a look at linux/Documentation/cpu-freq.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2005-06-01 10:03:47 +08:00
|
|
|
config CPU_FREQ_GOV_CONSERVATIVE
|
|
|
|
|
tristate "'conservative' cpufreq governor"
|
|
|
|
|
depends on CPU_FREQ
|
2012-12-29 09:55:20 +08:00
|
|
|
select CPU_FREQ_GOV_COMMON
|
2005-06-01 10:03:47 +08:00
|
|
|
help
|
|
|
|
|
'conservative' - this driver is rather similar to the 'ondemand'
|
|
|
|
|
governor both in its source code and its purpose, the difference is
|
|
|
|
|
its optimisation for better suitability in a battery powered
|
|
|
|
|
environment. The frequency is gracefully increased and decreased
|
|
|
|
|
rather than jumping to 100% when speed is required.
|
|
|
|
|
|
|
|
|
|
If you have a desktop machine then you should really be considering
|
|
|
|
|
the 'ondemand' governor instead, however if you are using a laptop,
|
|
|
|
|
PDA or even an AMD64 based computer (due to the unacceptable
|
|
|
|
|
step-by-step latency issues between the minimum and maximum frequency
|
|
|
|
|
transitions in the CPU) you will probably want to use this governor.
|
|
|
|
|
|
2007-04-19 04:18:13 +08:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cpufreq_conservative.
|
|
|
|
|
|
2005-06-01 10:03:47 +08:00
|
|
|
For details, take a look at linux/Documentation/cpu-freq.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2012-09-06 15:09:11 +08:00
|
|
|
config GENERIC_CPUFREQ_CPU0
|
2013-01-30 22:27:49 +08:00
|
|
|
tristate "Generic CPU0 cpufreq driver"
|
Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux
Pull thermal management updates from Zhang Rui:
"This time, the biggest change is the work of representing hardware
thermal properties in device tree infrastructure.
This work includes the introduction of a device tree bindings for
describing the hardware thermal behavior and limits, and also a parser
to read and interpret the data, and build thermal zones and thermal
binding parameters. It also contains three examples on how to use the
new representation on sensor devices, using three different drivers to
accomplish it. One driver is in thermal subsystem, the TI SoC
thermal, and the other two drivers are in hwmon subsystem.
Actually, this would be the first step of the complete work because we
still need to check other potential drivers to be converted and then
validate the proposed API. But the reason why I include it in this
pull request is that, first, this change does not hurt any others
without using this approach, second, the principle and concept of this
change would not break after converting the remaining drivers. BTW,
as you can see, there are several points in this change that do not
belong to thermal subsystem. Because it has been suggested by Guenter
R that in such cases, it is recommended to send the complete series
via one single subsystem.
Specifics:
- representing hardware thermal properties in device tree
infrastructure
- fix a regression that the imx thermal driver breaks system suspend.
- introduce ACPI INT3403 thermal driver to retrieve temperature data
from the INT3403 ACPI device object present on some systems.
- introduce debug statement for thermal core and step_wise governor.
- assorted fixes and cleanups for thermal core, cpu cooling, exynos
thrmal, intel powerclamp and imx thermal driver"
* 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux: (34 commits)
thermal: remove const flag from .ops of imx thermal
Thermal: update thermal zone device after setting emul_temp
intel_powerclamp: Fix cstate counter detection.
thermal: imx: add necessary clk operation
Thermal cpu cooling: return error if no valid cpu frequency entry
thermal: fix cpu_cooling max_level behavior
thermal: rcar-thermal: Enable driver compilation with COMPILE_TEST
thermal: debug: add debug statement for core and step_wise
thermal: imx_thermal: add module device table
drivers: thermal: Mark function as static in x86_pkg_temp_thermal.c
thermal:samsung: fix compilation warning
thermal: imx: correct suspend/resume flow
thermal: exynos: fix error return code
Thermal: ACPI INT3403 thermal driver
MAINTAINERS: add thermal bindings entry in thermal domain
arm: dts: make OMAP4460 bandgap node to belong to OCP
arm: dts: make OMAP443x bandgap node to belong to OCP
arm: dts: add cooling properties on omap5 cpu node
arm: dts: add omap5 thermal data
arm: dts: add omap5 CORE thermal data
...
2014-01-25 09:13:49 +08:00
|
|
|
depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL
|
2013-12-12 06:12:27 +08:00
|
|
|
select PM_OPP
|
2012-09-06 15:09:11 +08:00
|
|
|
help
|
|
|
|
|
This adds a generic cpufreq driver for CPU0 frequency management.
|
|
|
|
|
It supports both uniprocessor (UP) and symmetric multiprocessor (SMP)
|
|
|
|
|
systems which share clock and voltage across all CPUs.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2011-05-20 06:51:07 +08:00
|
|
|
menu "x86 CPU frequency scaling drivers"
|
|
|
|
|
depends on X86
|
|
|
|
|
source "drivers/cpufreq/Kconfig.x86"
|
|
|
|
|
endmenu
|
|
|
|
|
|
2011-06-02 05:18:22 +08:00
|
|
|
menu "ARM CPU frequency scaling drivers"
|
|
|
|
|
depends on ARM
|
|
|
|
|
source "drivers/cpufreq/Kconfig.arm"
|
|
|
|
|
endmenu
|
|
|
|
|
|
2013-04-04 20:54:17 +08:00
|
|
|
menu "AVR32 CPU frequency scaling drivers"
|
|
|
|
|
depends on AVR32
|
|
|
|
|
|
|
|
|
|
config AVR32_AT32AP_CPUFREQ
|
|
|
|
|
bool "CPU frequency driver for AT32AP"
|
|
|
|
|
depends on PLATFORM_AT32AP
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This enables the CPU frequency driver for AT32AP processors.
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
2013-04-04 20:54:20 +08:00
|
|
|
menu "CPUFreq processor drivers"
|
|
|
|
|
depends on IA64
|
|
|
|
|
|
|
|
|
|
config IA64_ACPI_CPUFREQ
|
|
|
|
|
tristate "ACPI Processor P-States driver"
|
|
|
|
|
depends on ACPI_PROCESSOR
|
|
|
|
|
help
|
|
|
|
|
This driver adds a CPUFreq driver which utilizes the ACPI
|
|
|
|
|
Processor Performance States.
|
|
|
|
|
|
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq/>.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
2013-04-04 20:54:21 +08:00
|
|
|
menu "MIPS CPUFreq processor drivers"
|
|
|
|
|
depends on MIPS
|
|
|
|
|
|
|
|
|
|
config LOONGSON2_CPUFREQ
|
|
|
|
|
tristate "Loongson2 CPUFreq Driver"
|
|
|
|
|
help
|
|
|
|
|
This option adds a CPUFreq driver for loongson processors which
|
|
|
|
|
support software configurable cpu frequency.
|
|
|
|
|
|
|
|
|
|
Loongson2F and it's successors support this feature.
|
|
|
|
|
|
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq/>.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
2011-06-29 13:07:56 +08:00
|
|
|
menu "PowerPC CPU frequency scaling drivers"
|
|
|
|
|
depends on PPC32 || PPC64
|
|
|
|
|
source "drivers/cpufreq/Kconfig.powerpc"
|
|
|
|
|
endmenu
|
|
|
|
|
|
2013-04-04 20:54:24 +08:00
|
|
|
menu "SPARC CPU frequency scaling drivers"
|
|
|
|
|
depends on SPARC64
|
|
|
|
|
config SPARC_US3_CPUFREQ
|
|
|
|
|
tristate "UltraSPARC-III CPU Frequency driver"
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for UltraSPARC-III processors.
|
|
|
|
|
|
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq>.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
|
|
|
|
config SPARC_US2E_CPUFREQ
|
|
|
|
|
tristate "UltraSPARC-IIe CPU Frequency driver"
|
|
|
|
|
help
|
|
|
|
|
This adds the CPUFreq driver for UltraSPARC-IIe processors.
|
|
|
|
|
|
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq>.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
endmenu
|
|
|
|
|
|
2013-04-04 20:54:22 +08:00
|
|
|
menu "SH CPU Frequency scaling"
|
|
|
|
|
depends on SUPERH
|
|
|
|
|
config SH_CPU_FREQ
|
|
|
|
|
tristate "SuperH CPU Frequency driver"
|
|
|
|
|
help
|
|
|
|
|
This adds the cpufreq driver for SuperH. Any CPU that supports
|
|
|
|
|
clock rate rounding through the clock framework can use this
|
|
|
|
|
driver. While it will make the kernel slightly larger, this is
|
|
|
|
|
harmless for CPUs that don't support rate rounding. The driver
|
|
|
|
|
will also generate a notice in the boot log before disabling
|
|
|
|
|
itself if the CPU in question is not capable of rate rounding.
|
|
|
|
|
|
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq>.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
endmenu
|
|
|
|
|
|
2011-05-20 06:51:07 +08:00
|
|
|
endif
|
|
|
|
|
endmenu
|