2008-01-17 00:51:08 -07:00
|
|
|
#
|
|
|
|
|
# Generic thermal sysfs drivers configuration
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menuconfig THERMAL
|
2008-04-21 02:07:13 -06:00
|
|
|
tristate "Generic Thermal sysfs driver"
|
2008-01-17 00:51:08 -07:00
|
|
|
help
|
|
|
|
|
Generic Thermal Sysfs driver offers a generic mechanism for
|
|
|
|
|
thermal management. Usually it's made up of one or more thermal
|
|
|
|
|
zone and cooling device.
|
2008-02-07 14:55:08 -07:00
|
|
|
Each thermal zone contains its own temperature, trip points,
|
2008-01-17 00:51:08 -07:00
|
|
|
cooling devices.
|
|
|
|
|
All platforms with ACPI thermal support can use this driver.
|
2008-04-21 02:07:13 -06:00
|
|
|
If you want this support, you should say Y or M here.
|
2008-06-24 11:38:56 -06:00
|
|
|
|
2012-11-14 18:16:20 -07:00
|
|
|
if THERMAL
|
|
|
|
|
|
2008-06-24 11:38:56 -06:00
|
|
|
config THERMAL_HWMON
|
2011-07-28 14:48:40 -06:00
|
|
|
bool
|
2008-06-24 11:38:56 -06:00
|
|
|
depends on HWMON=y || HWMON=THERMAL
|
2011-07-28 14:48:40 -06:00
|
|
|
default y
|
2012-03-21 13:55:03 -06:00
|
|
|
|
2012-11-14 18:16:20 -07:00
|
|
|
choice
|
|
|
|
|
prompt "Default Thermal governor"
|
|
|
|
|
default THERMAL_DEFAULT_GOV_STEP_WISE
|
|
|
|
|
help
|
|
|
|
|
This option sets which thermal governor shall be loaded at
|
|
|
|
|
startup. If in doubt, select 'step_wise'.
|
|
|
|
|
|
|
|
|
|
config THERMAL_DEFAULT_GOV_STEP_WISE
|
|
|
|
|
bool "step_wise"
|
|
|
|
|
select STEP_WISE
|
|
|
|
|
help
|
|
|
|
|
Use the step_wise governor as default. This throttles the
|
|
|
|
|
devices one step at a time.
|
|
|
|
|
|
|
|
|
|
config THERMAL_DEFAULT_GOV_FAIR_SHARE
|
|
|
|
|
bool "fair_share"
|
|
|
|
|
select FAIR_SHARE
|
|
|
|
|
help
|
|
|
|
|
Use the fair_share governor as default. This throttles the
|
|
|
|
|
devices based on their 'contribution' to a zone. The
|
|
|
|
|
contribution should be provided through platform data.
|
|
|
|
|
|
|
|
|
|
config THERMAL_DEFAULT_GOV_USER_SPACE
|
|
|
|
|
bool "user_space"
|
|
|
|
|
select USER_SPACE
|
|
|
|
|
help
|
|
|
|
|
Select this if you want to let the user space manage the
|
|
|
|
|
lpatform thermals.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config FAIR_SHARE
|
|
|
|
|
bool "Fair-share thermal governor"
|
|
|
|
|
help
|
|
|
|
|
Enable this to manage platform thermals using fair-share governor.
|
|
|
|
|
|
|
|
|
|
config STEP_WISE
|
|
|
|
|
bool "Step_wise thermal governor"
|
|
|
|
|
help
|
|
|
|
|
Enable this to manage platform thermals using a simple linear
|
|
|
|
|
|
|
|
|
|
config USER_SPACE
|
|
|
|
|
bool "User_space thermal governor"
|
|
|
|
|
help
|
|
|
|
|
Enable this to let the user space manage the platform thermals.
|
|
|
|
|
|
2012-08-16 05:41:40 -06:00
|
|
|
config CPU_THERMAL
|
2012-11-14 08:23:30 -07:00
|
|
|
tristate "generic cpu cooling support"
|
2012-11-14 18:16:20 -07:00
|
|
|
depends on CPU_FREQ
|
2012-10-15 14:40:15 -06:00
|
|
|
select CPU_FREQ_TABLE
|
2012-08-16 05:41:40 -06:00
|
|
|
help
|
|
|
|
|
This implements the generic cpu cooling mechanism through frequency
|
|
|
|
|
reduction, cpu hotplug and any other ways of reducing temperature. An
|
|
|
|
|
ACPI version of this already exists(drivers/acpi/processor_thermal.c).
|
|
|
|
|
This will be useful for platforms using the generic thermal interface
|
|
|
|
|
and not the ACPI interface.
|
|
|
|
|
If you want this support, you should say Y here.
|
|
|
|
|
|
2012-03-21 13:55:03 -06:00
|
|
|
config SPEAR_THERMAL
|
|
|
|
|
bool "SPEAr thermal sensor driver"
|
|
|
|
|
depends on PLAT_SPEAR
|
2012-05-29 12:18:51 -06:00
|
|
|
depends on OF
|
2012-03-21 13:55:03 -06:00
|
|
|
help
|
|
|
|
|
Enable this to plug the SPEAr thermal sensor driver into the Linux
|
|
|
|
|
thermal framework
|
2012-07-20 18:53:48 -06:00
|
|
|
|
|
|
|
|
config RCAR_THERMAL
|
|
|
|
|
tristate "Renesas R-Car thermal driver"
|
|
|
|
|
depends on ARCH_SHMOBILE
|
|
|
|
|
help
|
|
|
|
|
Enable this to plug the R-Car thermal sensor driver into the Linux
|
|
|
|
|
thermal framework
|
2012-08-16 05:41:41 -06:00
|
|
|
|
|
|
|
|
config EXYNOS_THERMAL
|
|
|
|
|
tristate "Temperature sensor on Samsung EXYNOS"
|
2012-11-14 18:16:20 -07:00
|
|
|
depends on (ARCH_EXYNOS4 || ARCH_EXYNOS5)
|
2012-11-14 23:51:05 -07:00
|
|
|
depends on CPU_THERMAL
|
2012-08-16 05:41:41 -06:00
|
|
|
help
|
2012-11-30 00:44:39 -07:00
|
|
|
If you say yes here you get support for TMU (Thermal Management
|
2012-08-16 05:41:41 -06:00
|
|
|
Unit) on SAMSUNG EXYNOS series of SoC.
|
2012-09-17 23:35:01 -06:00
|
|
|
|
2012-11-15 03:56:42 -07:00
|
|
|
config DB8500_THERMAL
|
|
|
|
|
bool "DB8500 thermal management"
|
|
|
|
|
depends on ARCH_U8500
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Adds DB8500 thermal management implementation according to the thermal
|
|
|
|
|
management framework. A thermal zone with several trip points will be
|
|
|
|
|
created. Cooling devices can be bound to the trip points to cool this
|
|
|
|
|
thermal zone if trip points reached.
|
|
|
|
|
|
|
|
|
|
config DB8500_CPUFREQ_COOLING
|
|
|
|
|
tristate "DB8500 cpufreq cooling"
|
|
|
|
|
depends on ARCH_U8500
|
|
|
|
|
depends on CPU_THERMAL
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Adds DB8500 cpufreq cooling devices, and these cooling devices can be
|
|
|
|
|
bound to thermal zone trip points. When a trip point reached, the
|
|
|
|
|
bound cpufreq cooling device turns active to set CPU frequency low to
|
|
|
|
|
cool down the CPU.
|
2012-09-21 03:02:24 -06:00
|
|
|
|
2012-11-14 18:16:20 -07:00
|
|
|
endif
|
