[mirror_ubuntu-zesty-kernel.git] / drivers / thermal / Kconfig

#
# Generic thermal sysfs drivers configuration
#

menuconfig THERMAL
	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 ACPI thermal support can use this driver.
	  If you want this support, you should say Y or M here.

if THERMAL

config THERMAL_HWMON
	bool
	prompt "Expose thermal sensors as hwmon device"
	depends on HWMON=y || HWMON=THERMAL
	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 THERMAL_OF
	bool
	prompt "APIs to parse thermal data out of device tree"
	depends on OF
	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 THERMAL_WRITABLE_TRIPS
	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 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 THERMAL_GOV_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 THERMAL_GOV_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 THERMAL_GOV_USER_SPACE
	help
	  Select this if you want to let the user space manage the
	  platform thermals.

config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
	bool "power_allocator"
	select THERMAL_GOV_POWER_ALLOCATOR
	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 THERMAL_GOV_FAIR_SHARE
	bool "Fair-share thermal governor"
	help
	  Enable this to manage platform thermals using fair-share governor.

config THERMAL_GOV_STEP_WISE
	bool "Step_wise thermal governor"
	help
	  Enable this to manage platform thermals using a simple linear
	  governor.

config THERMAL_GOV_BANG_BANG
	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 THERMAL_GOV_USER_SPACE
	bool "User_space thermal governor"
	help
	  Enable this to let the user space manage the platform thermals.

config THERMAL_GOV_POWER_ALLOCATOR
	bool "Power allocator thermal governor"
	help
	  Enable this to manage platform thermals by dynamically
	  allocating and limiting power to devices.

config CPU_THERMAL
	bool "generic cpu cooling support"
	depends on CPU_FREQ
	depends on THERMAL_OF
	help
	  This implements the generic cpu cooling mechanism through frequency
	  reduction. 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.

config CLOCK_THERMAL
	bool "Generic clock cooling support"
	depends on COMMON_CLK
	depends on PM_OPP
	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 DEVFREQ_THERMAL
	bool "Generic device cooling support"
	depends on PM_DEVFREQ
	depends on PM_OPP
	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 THERMAL_EMULATION
	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 HISI_THERMAL
	tristate "Hisilicon thermal driver"
	depends on ARCH_HISI || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	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 IMX_THERMAL
	tristate "Temperature sensor driver for Freescale i.MX SoCs"
	depends on (ARCH_MXC && CPU_THERMAL) || COMPILE_TEST
	depends on MFD_SYSCON
	depends on OF
	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 MAX77620_THERMAL
	tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
	depends on MFD_MAX77620
	depends on OF
	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 QORIQ_THERMAL
	tristate "QorIQ Thermal Monitoring Unit"
	depends on THERMAL_OF
	depends on HAS_IOMEM
	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 SPEAR_THERMAL
	tristate "SPEAr thermal sensor driver"
	depends on PLAT_SPEAR || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	help
	  Enable this to plug the SPEAr thermal sensor driver into the Linux
	  thermal framework.

config ROCKCHIP_THERMAL
	tristate "Rockchip thermal driver"
	depends on ARCH_ROCKCHIP || COMPILE_TEST
	depends on RESET_CONTROLLER
	depends on HAS_IOMEM
	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 RCAR_THERMAL
	tristate "Renesas R-Car thermal driver"
	depends on ARCH_RENESAS || COMPILE_TEST
	depends on HAS_IOMEM
	help
	  Enable this to plug the R-Car thermal sensor driver into the Linux
	  thermal framework.

config KIRKWOOD_THERMAL
	tristate "Temperature sensor on Marvell Kirkwood SoCs"
	depends on MACH_KIRKWOOD || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	help
	  Support for the Kirkwood thermal sensor driver into the Linux thermal
	  framework. Only kirkwood 88F6282 and 88F6283 have this sensor.

config DOVE_THERMAL
	tristate "Temperature sensor on Marvell Dove SoCs"
	depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	help
	  Support for the Dove thermal sensor driver in the Linux thermal
	  framework.

config DB8500_THERMAL
	tristate "DB8500 thermal management"
	depends on MFD_DB8500_PRCMU
	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 ARMADA_THERMAL
	tristate "Armada 370/XP thermal management"
	depends on ARCH_MVEBU || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	help
	  Enable this option if you want to have support for thermal management
	  controller present in Armada 370 and Armada XP SoC.

config DB8500_CPUFREQ_COOLING
	tristate "DB8500 cpufreq cooling"
	depends on ARCH_U8500 || COMPILE_TEST
	depends on HAS_IOMEM
	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.

config INTEL_POWERCLAMP
	tristate "Intel PowerClamp idle injection driver"
	depends on THERMAL
	depends on X86
	depends on CPU_SUP_INTEL
	help
	  Enable this to enable Intel PowerClamp idle injection driver. This
	  enforce idle time which results in more package C-state residency. The
	  user interface is exposed via generic thermal framework.

config THERMAL_BCM2835
	depends on RASPBERRYPI_FIRMWARE
	tristate "BCM2835 Thermal Driver"
	help
	  This will enable temperature monitoring for the Broadcom BCM2835
	  chip. If built as a module, it will be called 'bcm2835-thermal'.

config X86_PKG_TEMP_THERMAL
	tristate "X86 package temperature thermal driver"
	depends on X86_THERMAL_VECTOR
	select THERMAL_GOV_USER_SPACE
	select THERMAL_WRITABLE_TRIPS
	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 INTEL_SOC_DTS_IOSF_CORE
	tristate
	depends on X86
	select IOSF_MBI
	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 INTEL_SOC_DTS_THERMAL
	tristate "Intel SoCs DTS thermal driver"
	depends on X86
	select INTEL_SOC_DTS_IOSF_CORE
	select THERMAL_WRITABLE_TRIPS
	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 INTEL_QUARK_DTS_THERMAL
	tristate "Intel Quark DTS thermal driver"
	depends on X86_INTEL_QUARK
	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 INTEL_BXT_PMIC_THERMAL
	tristate "Intel Broxton PMIC thermal driver"
	depends on X86 && INTEL_SOC_PMIC && REGMAP
	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 INTEL_PCH_THERMAL
	tristate "Intel PCH Thermal Reporting Driver"
	depends on X86 && PCI
	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 MTK_THERMAL
	tristate "Temperature sensor driver for mediatek SoCs"
	depends on ARCH_MEDIATEK || COMPILE_TEST
	depends on HAS_IOMEM
	depends on NVMEM || NVMEM=n
	depends on RESET_CONTROLLER
	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 ARCH_HAS_BANDGAP || COMPILE_TEST
depends on HAS_IOMEM
source "drivers/thermal/ti-soc-thermal/Kconfig"
endmenu

menu "Samsung thermal drivers"
depends on ARCH_EXYNOS || COMPILE_TEST
source "drivers/thermal/samsung/Kconfig"
endmenu

menu "STMicroelectronics thermal drivers"
depends on ARCH_STI && OF
source "drivers/thermal/st/Kconfig"
endmenu

config TANGO_THERMAL
	tristate "Tango thermal management"
	depends on ARCH_TANGO || COMPILE_TEST
	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 QCOM_SPMI_TEMP_ALARM
	tristate "Qualcomm SPMI PMIC Temperature Alarm"
	depends on OF && SPMI && IIO
	select REGMAP_SPMI
	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 GENERIC_ADC_THERMAL
	tristate "Generic ADC based thermal sensor"
	depends on IIO
	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 IIO 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 (ARCH_QCOM && OF) || COMPILE_TEST
source "drivers/thermal/qcom/Kconfig"
endmenu

endif
Commit	Line	Data
203d3d4a ZR	1	#
	2	# Generic thermal sysfs drivers configuration
	3	#
	4
	5	menuconfig THERMAL
63c4ec90	6	tristate "Generic Thermal sysfs driver"
203d3d4a ZR	7	help
	8	Generic Thermal Sysfs driver offers a generic mechanism for
	9	thermal management. Usually it's made up of one or more thermal
	10	zone and cooling device.
543a9561	11	Each thermal zone contains its own temperature, trip points,
203d3d4a ZR	12	cooling devices.
203d3d4a ZR	13	All platforms with ACPI thermal support can use this driver.
63c4ec90	14	If you want this support, you should say Y or M here.
16d75239	15
72e19897 ZR	16	if THERMAL
72e19897 ZR	17
16d75239	18	config THERMAL_HWMON
ab92402a	19	bool
0dd88793	20	prompt "Expose thermal sensors as hwmon device"
16d75239	21	depends on HWMON=y \|\| HWMON=THERMAL
ab92402a	22	default y
0dd88793 EV	23	help
	24	In case a sensor is registered with the thermal
	25	framework, this option will also register it
	26	as a hwmon. The sensor will then have the common
	27	hwmon sysfs interface.
	28
	29	Say 'Y' here if you want all thermal sensors to
	30	have hwmon sysfs interface too.
6a92c366	31
4e5e4705 EV	32	config THERMAL_OF
	33	bool
	34	prompt "APIs to parse thermal data out of device tree"
	35	depends on OF
	36	default y
	37	help
	38	This options provides helpers to add the support to
	39	read and parse thermal data definitions out of the
	40	device tree blob.
	41
	42	Say 'Y' here if you need to build thermal infrastructure
	43	based on device tree.
	44
35e94644 PA	45	config THERMAL_WRITABLE_TRIPS
	46	bool "Enable writable trip points"
	47	help
	48	This option allows the system integrator to choose whether
	49	trip temperatures can be changed from userspace. The
	50	writable trips need to be specified when setting up the
	51	thermal zone but the choice here takes precedence.
	52
	53	Say 'Y' here if you would like to allow userspace tools to
	54	change trip temperatures.
	55
72e19897 ZR	56	choice
	57	prompt "Default Thermal governor"
	58	default THERMAL_DEFAULT_GOV_STEP_WISE
	59	help
	60	This option sets which thermal governor shall be loaded at
	61	startup. If in doubt, select 'step_wise'.
	62
	63	config THERMAL_DEFAULT_GOV_STEP_WISE
	64	bool "step_wise"
9d185d04	65	select THERMAL_GOV_STEP_WISE
72e19897 ZR	66	help
	67	Use the step_wise governor as default. This throttles the
	68	devices one step at a time.
	69
	70	config THERMAL_DEFAULT_GOV_FAIR_SHARE
	71	bool "fair_share"
9d185d04	72	select THERMAL_GOV_FAIR_SHARE
72e19897 ZR	73	help
	74	Use the fair_share governor as default. This throttles the
	75	devices based on their 'contribution' to a zone. The
	76	contribution should be provided through platform data.
	77
	78	config THERMAL_DEFAULT_GOV_USER_SPACE
	79	bool "user_space"
9d185d04	80	select THERMAL_GOV_USER_SPACE
72e19897 ZR	81	help
72e19897 ZR	82	Select this if you want to let the user space manage the
ece238fe	83	platform thermals.
72e19897	84
6b775e87 JM	85	config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
	86	bool "power_allocator"
	87	select THERMAL_GOV_POWER_ALLOCATOR
	88	help
	89	Select this if you want to control temperature based on
	90	system and device power allocation. This governor can only
	91	operate on cooling devices that implement the power API.
	92
72e19897 ZR	93	endchoice
72e19897 ZR	94
9d185d04	95	config THERMAL_GOV_FAIR_SHARE
72e19897 ZR	96	bool "Fair-share thermal governor"
	97	help
	98	Enable this to manage platform thermals using fair-share governor.
	99
9d185d04	100	config THERMAL_GOV_STEP_WISE
72e19897 ZR	101	bool "Step_wise thermal governor"
	102	help
	103	Enable this to manage platform thermals using a simple linear
a8227948	104	governor.
72e19897	105
e4dbf98f PF	106	config THERMAL_GOV_BANG_BANG
	107	bool "Bang Bang thermal governor"
	108	default n
	109	help
	110	Enable this to manage platform thermals using bang bang governor.
	111
	112	Say 'Y' here if you want to use two point temperature regulation
	113	used for fans without throttling. Some fan drivers depend on this
	114	governor to be enabled (e.g. acerhdf).
	115
9d185d04	116	config THERMAL_GOV_USER_SPACE
72e19897 ZR	117	bool "User_space thermal governor"
	118	help
	119	Enable this to let the user space manage the platform thermals.
	120
6b775e87 JM	121	config THERMAL_GOV_POWER_ALLOCATOR
6b775e87 JM	122	bool "Power allocator thermal governor"
6b775e87 JM	123	help
	124	Enable this to manage platform thermals by dynamically
	125	allocating and limiting power to devices.
	126
02361418	127	config CPU_THERMAL
bbf7fc88	128	bool "generic cpu cooling support"
72e19897	129	depends on CPU_FREQ
39d99cff	130	depends on THERMAL_OF
02361418 ADK	131	help
02361418 ADK	132	This implements the generic cpu cooling mechanism through frequency
f7188b3d EV	133	reduction. An ACPI version of this already exists
f7188b3d EV	134	(drivers/acpi/processor_thermal.c).
02361418 ADK	135	This will be useful for platforms using the generic thermal interface
02361418 ADK	136	and not the ACPI interface.
f7188b3d	137
02361418 ADK	138	If you want this support, you should say Y here.
02361418 ADK	139
f9df89d8 EV	140	config CLOCK_THERMAL
	141	bool "Generic clock cooling support"
	142	depends on COMMON_CLK
	143	depends on PM_OPP
	144	help
	145	This entry implements the generic clock cooling mechanism through
	146	frequency clipping. Typically used to cool off co-processors. The
	147	device that is configured to use this cooling mechanism will be
	148	controlled to reduce clock frequency whenever temperature is high.
	149
a76caf55 ØE	150	config DEVFREQ_THERMAL
	151	bool "Generic device cooling support"
	152	depends on PM_DEVFREQ
	153	depends on PM_OPP
	154	help
	155	This implements the generic devfreq cooling mechanism through
	156	frequency reduction for devices using devfreq.
	157
	158	This will throttle the device by limiting the maximum allowed DVFS
	159	frequency corresponding to the cooling level.
	160
	161	In order to use the power extensions of the cooling device,
	162	devfreq should use the simple_ondemand governor.
	163
f9df89d8 EV	164	If you want this support, you should say Y here.
f9df89d8 EV	165
e6e238c3 ADK	166	config THERMAL_EMULATION
	167	bool "Thermal emulation mode support"
	168	help
	169	Enable this option to make a emul_temp sysfs node in thermal zone
	170	directory to support temperature emulation. With emulation sysfs node,
	171	user can manually input temperature and test the different trip
	172	threshold behaviour for simulation purpose.
	173
8837295a EV	174	WARNING: Be careful while enabling this option on production systems,
	175	because userland can easily disable the thermal policy by simply
	176	flooding this sysfs node with low temperature values.
	177
9a5238a9	178	config HISI_THERMAL
9a5238a9	179	tristate "Hisilicon thermal driver"
f05f4821	180	depends on ARCH_HISI \|\| COMPILE_TEST
bf82c350	181	depends on HAS_IOMEM
f05f4821 LY	182	depends on OF
f05f4821 LY	183	default y
9a5238a9	184	help
	185	Enable this to plug hisilicon's thermal sensor driver into the Linux
	186	thermal framework. cpufreq is used as the cooling device to throttle
	187	CPUs when the passive trip is crossed.
	188
ca3de46b SG	189	config IMX_THERMAL
ca3de46b SG	190	tristate "Temperature sensor driver for Freescale i.MX SoCs"
eea6a364	191	depends on (ARCH_MXC && CPU_THERMAL) \|\| COMPILE_TEST
ca3de46b SG	192	depends on MFD_SYSCON
	193	depends on OF
	194	help
	195	Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
	196	It supports one critical trip point and one passive trip point. The
	197	cpufreq is used as the cooling device to throttle CPUs when the
	198	passive trip is crossed.
	199
ec4664b3 LD	200	config MAX77620_THERMAL
	201	tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
	202	depends on MFD_MAX77620
	203	depends on OF
	204	help
	205	Support for die junction temperature warning alarm for Maxim
	206	Semiconductor PMIC MAX77620 device. Device generates two alarm
	207	interrupts when PMIC die temperature cross the threshold of
	208	120 degC and 140 degC.
	209
43528445 JH	210	config QORIQ_THERMAL
	211	tristate "QorIQ Thermal Monitoring Unit"
	212	depends on THERMAL_OF
	213	depends on HAS_IOMEM
	214	help
	215	Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
	216	It supports one critical trip point and one passive trip point. The
	217	cpufreq is used as the cooling device to throttle CPUs when the
	218	passive trip is crossed.
	219
6a92c366	220	config SPEAR_THERMAL
4d2f1794	221	tristate "SPEAr thermal sensor driver"
aa2937b7	222	depends on PLAT_SPEAR \|\| COMPILE_TEST
bf82c350	223	depends on HAS_IOMEM
b9c7aff4	224	depends on OF
6a92c366 VF	225	help
6a92c366 VF	226	Enable this to plug the SPEAr thermal sensor driver into the Linux
a8227948	227	thermal framework.
1e426ffd	228
cbac8f63 CW	229	config ROCKCHIP_THERMAL
cbac8f63 CW	230	tristate "Rockchip thermal driver"
444f9b00	231	depends on ARCH_ROCKCHIP \|\| COMPILE_TEST
cbac8f63	232	depends on RESET_CONTROLLER
bf82c350	233	depends on HAS_IOMEM
cbac8f63 CW	234	help
	235	Rockchip thermal driver provides support for Temperature sensor
	236	ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
	237	trip point. Cpufreq is used as the cooling device and will throttle
	238	CPUs when the Temperature crosses the passive trip point.
	239
1e426ffd KM	240	config RCAR_THERMAL
1e426ffd KM	241	tristate "Renesas R-Car thermal driver"
8255e4e2	242	depends on ARCH_RENESAS \|\| COMPILE_TEST
d1c8b041	243	depends on HAS_IOMEM
1e426ffd KM	244	help
1e426ffd KM	245	Enable this to plug the R-Car thermal sensor driver into the Linux
a8227948	246	thermal framework.
c48cbba6	247
7060aa36 NI	248	config KIRKWOOD_THERMAL
7060aa36 NI	249	tristate "Temperature sensor on Marvell Kirkwood SoCs"
9c8aa959	250	depends on MACH_KIRKWOOD \|\| COMPILE_TEST
bf82c350	251	depends on HAS_IOMEM
7060aa36 NI	252	depends on OF
	253	help
	254	Support for the Kirkwood thermal sensor driver into the Linux thermal
	255	framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
	256
74ffa64c AL	257	config DOVE_THERMAL
74ffa64c AL	258	tristate "Temperature sensor on Marvell Dove SoCs"
07fffd5c	259	depends on ARCH_DOVE \|\| MACH_DOVE \|\| COMPILE_TEST
bf82c350	260	depends on HAS_IOMEM
74ffa64c AL	261	depends on OF
	262	help
	263	Support for the Dove thermal sensor driver in the Linux thermal
	264	framework.
	265
aa1acb04	266	config DB8500_THERMAL
26716ce1 AB	267	tristate "DB8500 thermal management"
26716ce1 AB	268	depends on MFD_DB8500_PRCMU
aa1acb04	269	default y
	270	help
	271	Adds DB8500 thermal management implementation according to the thermal
	272	management framework. A thermal zone with several trip points will be
	273	created. Cooling devices can be bound to the trip points to cool this
	274	thermal zone if trip points reached.
	275
fa0d654c EG	276	config ARMADA_THERMAL
fa0d654c EG	277	tristate "Armada 370/XP thermal management"
1b158267	278	depends on ARCH_MVEBU \|\| COMPILE_TEST
bf82c350	279	depends on HAS_IOMEM
fa0d654c EG	280	depends on OF
	281	help
	282	Enable this option if you want to have support for thermal management
	283	controller present in Armada 370 and Armada XP SoC.
	284
aa1acb04	285	config DB8500_CPUFREQ_COOLING
aa1acb04	286	tristate "DB8500 cpufreq cooling"
527860fe	287	depends on ARCH_U8500 \|\| COMPILE_TEST
bf82c350	288	depends on HAS_IOMEM
aa1acb04	289	depends on CPU_THERMAL
	290	default y
	291	help
	292	Adds DB8500 cpufreq cooling devices, and these cooling devices can be
	293	bound to thermal zone trip points. When a trip point reached, the
	294	bound cpufreq cooling device turns active to set CPU frequency low to
	295	cool down the CPU.
a56757af	296
d6d71ee4 JP	297	config INTEL_POWERCLAMP
	298	tristate "Intel PowerClamp idle injection driver"
	299	depends on THERMAL
	300	depends on X86
	301	depends on CPU_SUP_INTEL
	302	help
	303	Enable this to enable Intel PowerClamp idle injection driver. This
	304	enforce idle time which results in more package C-state residency. The
	305	user interface is exposed via generic thermal framework.
	306
6e07a28c	307	config THERMAL_BCM2835
	308	depends on RASPBERRYPI_FIRMWARE
	309	tristate "BCM2835 Thermal Driver"
	310	help
	311	This will enable temperature monitoring for the Broadcom BCM2835
	312	chip. If built as a module, it will be called 'bcm2835-thermal'.
	313
f1a18a10 SP	314	config X86_PKG_TEMP_THERMAL
f1a18a10 SP	315	tristate "X86 package temperature thermal driver"
b3ba0206	316	depends on X86_THERMAL_VECTOR
f1a18a10	317	select THERMAL_GOV_USER_SPACE
98cadf25	318	select THERMAL_WRITABLE_TRIPS
f1a18a10 SP	319	default m
	320	help
	321	Enable this to register CPU digital sensor for package temperature as
	322	thermal zone. Each package will have its own thermal zone. There are
	323	two trip points which can be set by user to get notifications via thermal
	324	notification methods.
	325
ee073604 SP	326	config INTEL_SOC_DTS_IOSF_CORE
	327	tristate
	328	depends on X86
	329	select IOSF_MBI
	330	help
	331	This is becoming a common feature for Intel SoCs to expose the additional
	332	digital temperature sensors (DTSs) using side band interface (IOSF). This
	333	implements the common set of helper functions to register, get temperature
	334	and get/set thresholds on DTSs.
	335
bc40b5e3 SP	336	config INTEL_SOC_DTS_THERMAL
bc40b5e3 SP	337	tristate "Intel SoCs DTS thermal driver"
3a2419f8 SP	338	depends on X86
3a2419f8 SP	339	select INTEL_SOC_DTS_IOSF_CORE
98cadf25	340	select THERMAL_WRITABLE_TRIPS
bc40b5e3 SP	341	help
	342	Enable this to register Intel SoCs (e.g. Bay Trail) platform digital
	343	temperature sensor (DTS). These SoCs have two additional DTSs in
	344	addition to DTSs on CPU cores. Each DTS will be registered as a
	345	thermal zone. There are two trip points. One of the trip point can
	346	be set by user mode programs to get notifications via Linux thermal
	347	notification methods.The other trip is a critical trip point, which
	348	was set by the driver based on the TJ MAX temperature.
	349
8c187693 OBL	350	config INTEL_QUARK_DTS_THERMAL
	351	tristate "Intel Quark DTS thermal driver"
	352	depends on X86_INTEL_QUARK
	353	help
	354	Enable this to register Intel Quark SoC (e.g. X1000) platform digital
	355	temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
	356	The DTS will be registered as a thermal zone. There are two trip points:
	357	hot & critical. The critical trip point default value is set by
	358	underlying BIOS/Firmware.
	359
a3c89334 AL	360	menu "ACPI INT340X thermal drivers"
	361	source drivers/thermal/int340x_thermal/Kconfig
	362	endmenu
52b1c69d	363
b474303f BG	364	config INTEL_BXT_PMIC_THERMAL
	365	tristate "Intel Broxton PMIC thermal driver"
	366	depends on X86 && INTEL_SOC_PMIC && REGMAP
	367	help
	368	Select this driver for Intel Broxton PMIC with ADC channels monitoring
	369	system temperature measurements and alerts.
	370	This driver is used for monitoring the ADC channels of PMIC and handles
	371	the alert trip point interrupts and notifies the thermal framework with
	372	the trip point and temperature details of the zone.
	373
d0a12625 TD	374	config INTEL_PCH_THERMAL
	375	tristate "Intel PCH Thermal Reporting Driver"
	376	depends on X86 && PCI
	377	help
	378	Enable this to support thermal reporting on certain intel PCHs.
	379	Thermal reporting device will provide temperature reading,
	380	programmable trip points and other information.
	381
a92db1c8 SH	382	config MTK_THERMAL
	383	tristate "Temperature sensor driver for mediatek SoCs"
	384	depends on ARCH_MEDIATEK \|\| COMPILE_TEST
74e5053c	385	depends on HAS_IOMEM
62e14f6f	386	depends on NVMEM \|\| NVMEM=n
a6f4850d	387	depends on RESET_CONTROLLER
a92db1c8 SH	388	default y
	389	help
	390	Enable this option if you want to have support for thermal management
	391	controller present in Mediatek SoCs
	392
eb982001	393	menu "Texas Instruments thermal drivers"
ec2feb47	394	depends on ARCH_HAS_BANDGAP \|\| COMPILE_TEST
bf82c350	395	depends on HAS_IOMEM
eb982001 EV	396	source "drivers/thermal/ti-soc-thermal/Kconfig"
eb982001 EV	397	endmenu
f157f596	398
c6821378	399	menu "Samsung thermal drivers"
2bf42735	400	depends on ARCH_EXYNOS \|\| COMPILE_TEST
c6821378 ADK	401	source "drivers/thermal/samsung/Kconfig"
	402	endmenu
	403
60aef7ce LJ	404	menu "STMicroelectronics thermal drivers"
	405	depends on ARCH_STI && OF
	406	source "drivers/thermal/st/Kconfig"
	407	endmenu
	408
0b58c08b MG	409	config TANGO_THERMAL
	410	tristate "Tango thermal management"
	411	depends on ARCH_TANGO \|\| COMPILE_TEST
	412	help
	413	Enable the Tango thermal driver, which supports the primitive
	414	temperature sensor embedded in Tango chips since the SMP8758.
	415	This sensor only generates a 1-bit signal to indicate whether
	416	the die temperature exceeds a programmable threshold.
	417
a4dff94f WN	418	source "drivers/thermal/tegra/Kconfig"
a4dff94f WN	419
c610afaa II	420	config QCOM_SPMI_TEMP_ALARM
c610afaa II	421	tristate "Qualcomm SPMI PMIC Temperature Alarm"
e4217468	422	depends on OF && SPMI && IIO
c610afaa II	423	select REGMAP_SPMI
	424	help
	425	This enables a thermal sysfs driver for Qualcomm plug-and-play (QPNP)
	426	PMIC devices. It shows up in sysfs as a thermal sensor with multiple
	427	trip points. The temperature reported by the thermal sensor reflects the
	428	real time die temperature if an ADC is present or an estimate of the
	429	temperature based upon the over temperature stage value.
	430
b3aef78f LD	431	config GENERIC_ADC_THERMAL
	432	tristate "Generic ADC based thermal sensor"
	433	depends on IIO
	434	help
	435	This enabled a thermal sysfs driver for the temperature sensor
	436	which is connected to the General Purpose ADC. The ADC channel
	437	is read via IIO framework and the channel information is provided
	438	to this driver. This driver reports the temperature by reading ADC
	439	channel and converts it to temperature based on lookup table.
	440
9066073c RN	441	menu "Qualcomm thermal drivers"
	442	depends on (ARCH_QCOM && OF) \|\| COMPILE_TEST
	443	source "drivers/thermal/qcom/Kconfig"
	444	endmenu
	445
72e19897	446	endif