#
# Generic thermal sysfs drivers configuration
#
menuconfig [31mCONFIG_THERMAL[0m
tristate "Generic Thermal sysfs driver"
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.
Each thermal zone contains its own temperature, trip points,
cooling devices.
All platforms with [31mCONFIG_ACPI[0m thermal support can use this driver.
If you want this support, you should say Y or [31mCONFIG_M[0m here.
if [31mCONFIG_THERMAL[0m
config [31mCONFIG_THERMAL_HWMON[0m
bool
prompt "Expose thermal sensors as hwmon device"
depends on [31mCONFIG_HWMON[0m=y || [31mCONFIG_HWMON[0m=[31mCONFIG_THERMAL[0m
default y
help
In case a sensor is registered with the thermal
framework, this option will also register it
as a hwmon. The sensor will then have the common
hwmon sysfs interface.
Say 'Y' here if you want all thermal sensors to
have hwmon sysfs interface too.
config [31mCONFIG_THERMAL_OF[0m
bool
prompt "APIs to parse thermal data out of device tree"
depends on [31mCONFIG_OF[0m
default y
help
This options provides helpers to add the support to
read and parse thermal data definitions out of the
device tree blob.
Say 'Y' here if you need to build thermal infrastructure
based on device tree.
config [31mCONFIG_THERMAL_WRITABLE_TRIPS[0m
bool "Enable writable trip points"
help
This option allows the system integrator to choose whether
trip temperatures can be changed from userspace. The
writable trips need to be specified when setting up the
thermal zone but the choice here takes precedence.
Say 'Y' here if you would like to allow userspace tools to
change trip temperatures.
choice
prompt "Default Thermal governor"
default [31mCONFIG_THERMAL_DEFAULT_GOV_STEP_WISE[0m
help
This option sets which thermal governor shall be loaded at
startup. If in doubt, select 'step_wise'.
config [31mCONFIG_THERMAL_DEFAULT_GOV_STEP_WISE[0m
bool "step_wise"
select [31mCONFIG_THERMAL_GOV_STEP_WISE[0m
help
Use the step_wise governor as default. This throttles the
devices one step at a time.
config [31mCONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE[0m
bool "fair_share"
select [31mCONFIG_THERMAL_GOV_FAIR_SHARE[0m
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 [31mCONFIG_THERMAL_DEFAULT_GOV_USER_SPACE[0m
bool "user_space"
select [31mCONFIG_THERMAL_GOV_USER_SPACE[0m
help
Select this if you want to let the user space manage the
platform thermals.
config [31mCONFIG_THERMAL_DEFAULT_GOV_POWER_ALLOCATOR[0m
bool "power_allocator"
select [31mCONFIG_THERMAL_GOV_POWER_ALLOCATOR[0m
help
Select this if you want to control temperature based on
system and device power allocation. This governor can only
operate on cooling devices that implement the power API.
endchoice
config [31mCONFIG_THERMAL_GOV_FAIR_SHARE[0m
bool "Fair-share thermal governor"
help
Enable this to manage platform thermals using fair-share governor.
config [31mCONFIG_THERMAL_GOV_STEP_WISE[0m
bool "Step_wise thermal governor"
help
Enable this to manage platform thermals using a simple linear
governor.
config [31mCONFIG_THERMAL_GOV_BANG_BANG[0m
bool "Bang Bang thermal governor"
default n
help
Enable this to manage platform thermals using bang bang governor.
Say 'Y' here if you want to use two point temperature regulation
used for fans without throttling. Some fan drivers depend on this
governor to be enabled (e.g. acerhdf).
config [31mCONFIG_THERMAL_GOV_USER_SPACE[0m
bool "User_space thermal governor"
help
Enable this to let the user space manage the platform thermals.
config [31mCONFIG_THERMAL_GOV_POWER_ALLOCATOR[0m
bool "Power allocator thermal governor"
help
Enable this to manage platform thermals by dynamically
allocating and limiting power to devices.
config [31mCONFIG_CPU_THERMAL[0m
bool "generic cpu cooling support"
depends on [31mCONFIG_CPU_FREQ[0m
depends on [31mCONFIG_THERMAL_OF[0m
help
This implements the generic cpu cooling mechanism through frequency
reduction. An [31mCONFIG_ACPI[0m version of this already exists
(drivers/acpi/processor_thermal.c).
This will be useful for platforms using the generic thermal interface
and not the [31mCONFIG_ACPI[0m interface.
If you want this support, you should say Y here.
config [31mCONFIG_CLOCK_THERMAL[0m
bool "Generic clock cooling support"
depends on [31mCONFIG_COMMON_CLK[0m
depends on [31mCONFIG_PM_OPP[0m
help
This entry implements the generic clock cooling mechanism through
frequency clipping. Typically used to cool off co-processors. The
device that is configured to use this cooling mechanism will be
controlled to reduce clock frequency whenever temperature is high.
config [31mCONFIG_DEVFREQ_THERMAL[0m
bool "Generic device cooling support"
depends on [31mCONFIG_PM_DEVFREQ[0m
depends on [31mCONFIG_PM_OPP[0m
help
This implements the generic devfreq cooling mechanism through
frequency reduction for devices using devfreq.
This will throttle the device by limiting the maximum allowed DVFS
frequency corresponding to the cooling level.
In order to use the power extensions of the cooling device,
devfreq should use the simple_ondemand governor.
If you want this support, you should say Y here.
config [31mCONFIG_THERMAL_EMULATION[0m
bool "Thermal emulation mode support"
help
Enable this option to make a emul_temp sysfs node in thermal zone
directory to support temperature emulation. With emulation sysfs node,
user can manually input temperature and test the different trip
threshold behaviour for simulation purpose.
WARNING: Be careful while enabling this option on production systems,
because userland can easily disable the thermal policy by simply
flooding this sysfs node with low temperature values.
config [31mCONFIG_HISI_THERMAL[0m
tristate "Hisilicon thermal driver"
depends on [31mCONFIG_ARCH_HISI[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_OF[0m
default y
help
Enable this to plug hisilicon's thermal sensor driver into the Linux
thermal framework. cpufreq is used as the cooling device to throttle
CPUs when the passive trip is crossed.
config [31mCONFIG_IMX_THERMAL[0m
tristate "Temperature sensor driver for Freescale i.MX SoCs"
depends on ([31mCONFIG_ARCH_MXC[0m && [31mCONFIG_CPU_THERMAL[0m) || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_MFD_SYSCON[0m
depends on [31mCONFIG_OF[0m
help
Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
It supports one critical trip point and one passive trip point. The
cpufreq is used as the cooling device to throttle CPUs when the
passive trip is crossed.
config [31mCONFIG_MAX77620_THERMAL[0m
tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
depends on [31mCONFIG_MFD_MAX77620[0m
depends on [31mCONFIG_OF[0m
help
Support for die junction temperature warning alarm for Maxim
Semiconductor PMIC MAX77620 device. Device generates two alarm
interrupts when PMIC die temperature cross the threshold of
120 degC and 140 degC.
config [31mCONFIG_QORIQ_THERMAL[0m
tristate "QorIQ Thermal Monitoring Unit"
depends on [31mCONFIG_THERMAL_OF[0m
depends on [31mCONFIG_HAS_IOMEM[0m
help
Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
It supports one critical trip point and one passive trip point. The
cpufreq is used as the cooling device to throttle CPUs when the
passive trip is crossed.
config [31mCONFIG_SPEAR_THERMAL[0m
tristate "SPEAr thermal sensor driver"
depends on [31mCONFIG_PLAT_SPEAR[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_OF[0m
help
Enable this to plug the SPEAr thermal sensor driver into the Linux
thermal framework.
config [31mCONFIG_ROCKCHIP_THERMAL[0m
tristate "Rockchip thermal driver"
depends on [31mCONFIG_ARCH_ROCKCHIP[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_RESET_CONTROLLER[0m
depends on [31mCONFIG_HAS_IOMEM[0m
help
Rockchip thermal driver provides support for Temperature sensor
ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
trip point. Cpufreq is used as the cooling device and will throttle
CPUs when the Temperature crosses the passive trip point.
config [31mCONFIG_RCAR_THERMAL[0m
tristate "Renesas R-Car thermal driver"
depends on [31mCONFIG_ARCH_RENESAS[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
help
Enable this to plug the R-Car thermal sensor driver into the Linux
thermal framework.
config [31mCONFIG_KIRKWOOD_THERMAL[0m
tristate "Temperature sensor on Marvell Kirkwood SoCs"
depends on [31mCONFIG_MACH_KIRKWOOD[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_OF[0m
help
Support for the Kirkwood thermal sensor driver into the Linux thermal
framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
config [31mCONFIG_DOVE_THERMAL[0m
tristate "Temperature sensor on Marvell Dove SoCs"
depends on [31mCONFIG_ARCH_DOVE[0m || [31mCONFIG_MACH_DOVE[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_OF[0m
help
Support for the Dove thermal sensor driver in the Linux thermal
framework.
config [31mCONFIG_DB8500_THERMAL[0m
tristate "DB8500 thermal management"
depends on [31mCONFIG_MFD_DB8500_PRCMU[0m
default y
help
Adds DB8500 thermal management implementation according to the thermal
management framework. [31mCONFIG_A[0m 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 [31mCONFIG_ARMADA_THERMAL[0m
tristate "Armada 370/XP thermal management"
depends on [31mCONFIG_ARCH_MVEBU[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_OF[0m
help
Enable this option if you want to have support for thermal management
controller present in Armada 370 and Armada XP SoC.
config [31mCONFIG_DB8500_CPUFREQ_COOLING[0m
tristate "DB8500 cpufreq cooling"
depends on [31mCONFIG_ARCH_U8500[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_CPU_THERMAL[0m
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.
config [31mCONFIG_INTEL_POWERCLAMP[0m
tristate "Intel PowerClamp idle injection driver"
depends on [31mCONFIG_THERMAL[0m
depends on [31mCONFIG_X86[0m
depends on [31mCONFIG_CPU_SUP_INTEL[0m
help
Enable this to enable Intel PowerClamp idle injection driver. This
enforce idle time which results in more package [31mCONFIG_C[0m-state residency. The
user interface is exposed via generic thermal framework.
config [31mCONFIG_X86_PKG_TEMP_THERMAL[0m
tristate "X86 package temperature thermal driver"
depends on [31mCONFIG_X86_THERMAL_VECTOR[0m
select [31mCONFIG_THERMAL_GOV_USER_SPACE[0m
select [31mCONFIG_THERMAL_WRITABLE_TRIPS[0m
default m
help
Enable this to register CPU digital sensor for package temperature as
thermal zone. Each package will have its own thermal zone. There are
two trip points which can be set by user to get notifications via thermal
notification methods.
config [31mCONFIG_INTEL_SOC_DTS_IOSF_CORE[0m
tristate
depends on [31mCONFIG_X86[0m
select [31mCONFIG_IOSF_MBI[0m
help
This is becoming a common feature for Intel SoCs to expose the additional
digital temperature sensors (DTSs) using side band interface (IOSF). This
implements the common set of helper functions to register, get temperature
and get/set thresholds on DTSs.
config [31mCONFIG_INTEL_SOC_DTS_THERMAL[0m
tristate "Intel SoCs DTS thermal driver"
depends on [31mCONFIG_X86[0m
select [31mCONFIG_INTEL_SOC_DTS_IOSF_CORE[0m
select [31mCONFIG_THERMAL_WRITABLE_TRIPS[0m
help
Enable this to register Intel SoCs (e.g. Bay Trail) platform digital
temperature sensor (DTS). These SoCs have two additional DTSs in
addition to DTSs on CPU cores. Each DTS will be registered as a
thermal zone. There are two trip points. One of the trip point can
be set by user mode programs to get notifications via Linux thermal
notification methods.The other trip is a critical trip point, which
was set by the driver based on the TJ MAX temperature.
config [31mCONFIG_INTEL_QUARK_DTS_THERMAL[0m
tristate "Intel Quark DTS thermal driver"
depends on [31mCONFIG_X86_INTEL_QUARK[0m
help
Enable this to register Intel Quark SoC (e.g. X1000) platform digital
temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
The DTS will be registered as a thermal zone. There are two trip points:
hot & critical. The critical trip point default value is set by
underlying BIOS/Firmware.
menu "ACPI INT340X thermal drivers"
source drivers/thermal/int340x_thermal/Kconfig
endmenu
config [31mCONFIG_INTEL_BXT_PMIC_THERMAL[0m
tristate "Intel Broxton PMIC thermal driver"
depends on [31mCONFIG_X86[0m && [31mCONFIG_INTEL_SOC_PMIC[0m && [31mCONFIG_REGMAP[0m
help
Select this driver for Intel Broxton PMIC with ADC channels monitoring
system temperature measurements and alerts.
This driver is used for monitoring the ADC channels of PMIC and handles
the alert trip point interrupts and notifies the thermal framework with
the trip point and temperature details of the zone.
config [31mCONFIG_INTEL_PCH_THERMAL[0m
tristate "Intel PCH Thermal Reporting Driver"
depends on [31mCONFIG_X86[0m && [31mCONFIG_PCI[0m
help
Enable this to support thermal reporting on certain intel PCHs.
Thermal reporting device will provide temperature reading,
programmable trip points and other information.
config [31mCONFIG_MTK_THERMAL[0m
tristate "Temperature sensor driver for mediatek SoCs"
depends on [31mCONFIG_ARCH_MEDIATEK[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_NVMEM[0m || [31mCONFIG_NVMEM[0m=n
depends on [31mCONFIG_RESET_CONTROLLER[0m
default y
help
Enable this option if you want to have support for thermal management
controller present in Mediatek SoCs
menu "Texas Instruments thermal drivers"
depends on [31mCONFIG_ARCH_HAS_BANDGAP[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
source "drivers/thermal/ti-soc-thermal/Kconfig"
endmenu
menu "Samsung thermal drivers"
depends on [31mCONFIG_ARCH_EXYNOS[0m || [31mCONFIG_COMPILE_TEST[0m
source "drivers/thermal/samsung/Kconfig"
endmenu
menu "STMicroelectronics thermal drivers"
depends on [31mCONFIG_ARCH_STI[0m && [31mCONFIG_OF[0m
source "drivers/thermal/st/Kconfig"
endmenu
config [31mCONFIG_TANGO_THERMAL[0m
tristate "Tango thermal management"
depends on [31mCONFIG_ARCH_TANGO[0m || [31mCONFIG_COMPILE_TEST[0m
help
Enable the Tango thermal driver, which supports the primitive
temperature sensor embedded in Tango chips since the SMP8758.
This sensor only generates a 1-bit signal to indicate whether
the die temperature exceeds a programmable threshold.
source "drivers/thermal/tegra/Kconfig"
config [31mCONFIG_QCOM_SPMI_TEMP_ALARM[0m
tristate "Qualcomm SPMI PMIC Temperature Alarm"
depends on [31mCONFIG_OF[0m && [31mCONFIG_SPMI[0m && [31mCONFIG_IIO[0m
select [31mCONFIG_REGMAP_SPMI[0m
help
This enables a thermal sysfs driver for Qualcomm plug-and-play (QPNP)
PMIC devices. It shows up in sysfs as a thermal sensor with multiple
trip points. The temperature reported by the thermal sensor reflects the
real time die temperature if an ADC is present or an estimate of the
temperature based upon the over temperature stage value.
config [31mCONFIG_GENERIC_ADC_THERMAL[0m
tristate "Generic ADC based thermal sensor"
depends on [31mCONFIG_IIO[0m
help
This enabled a thermal sysfs driver for the temperature sensor
which is connected to the General Purpose ADC. The ADC channel
is read via [31mCONFIG_IIO[0m framework and the channel information is provided
to this driver. This driver reports the temperature by reading ADC
channel and converts it to temperature based on lookup table.
menu "Qualcomm thermal drivers"
depends on ([31mCONFIG_ARCH_QCOM[0m && [31mCONFIG_OF[0m) || [31mCONFIG_COMPILE_TEST[0m
source "drivers/thermal/qcom/Kconfig"
endmenu
endif