1# 2# Generic thermal sysfs drivers configuration 3# 4 5menuconfig THERMAL 6 tristate "Generic Thermal sysfs driver" 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. 11 Each thermal zone contains its own temperature, trip points, 12 cooling devices. 13 All platforms with ACPI thermal support can use this driver. 14 If you want this support, you should say Y or M here. 15 16if THERMAL 17 18config THERMAL_HWMON 19 bool 20 prompt "Expose thermal sensors as hwmon device" 21 depends on HWMON=y || HWMON=THERMAL 22 default y 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. 31 32config 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 45choice 46 prompt "Default Thermal governor" 47 default THERMAL_DEFAULT_GOV_STEP_WISE 48 help 49 This option sets which thermal governor shall be loaded at 50 startup. If in doubt, select 'step_wise'. 51 52config THERMAL_DEFAULT_GOV_STEP_WISE 53 bool "step_wise" 54 select THERMAL_GOV_STEP_WISE 55 help 56 Use the step_wise governor as default. This throttles the 57 devices one step at a time. 58 59config THERMAL_DEFAULT_GOV_FAIR_SHARE 60 bool "fair_share" 61 select THERMAL_GOV_FAIR_SHARE 62 help 63 Use the fair_share governor as default. This throttles the 64 devices based on their 'contribution' to a zone. The 65 contribution should be provided through platform data. 66 67config THERMAL_DEFAULT_GOV_USER_SPACE 68 bool "user_space" 69 select THERMAL_GOV_USER_SPACE 70 help 71 Select this if you want to let the user space manage the 72 platform thermals. 73 74endchoice 75 76config THERMAL_GOV_FAIR_SHARE 77 bool "Fair-share thermal governor" 78 help 79 Enable this to manage platform thermals using fair-share governor. 80 81config THERMAL_GOV_STEP_WISE 82 bool "Step_wise thermal governor" 83 help 84 Enable this to manage platform thermals using a simple linear 85 governor. 86 87config THERMAL_GOV_BANG_BANG 88 bool "Bang Bang thermal governor" 89 default n 90 help 91 Enable this to manage platform thermals using bang bang governor. 92 93 Say 'Y' here if you want to use two point temperature regulation 94 used for fans without throttling. Some fan drivers depend on this 95 governor to be enabled (e.g. acerhdf). 96 97config THERMAL_GOV_USER_SPACE 98 bool "User_space thermal governor" 99 help 100 Enable this to let the user space manage the platform thermals. 101 102config CPU_THERMAL 103 bool "generic cpu cooling support" 104 depends on CPU_FREQ 105 depends on THERMAL_OF 106 help 107 This implements the generic cpu cooling mechanism through frequency 108 reduction. An ACPI version of this already exists 109 (drivers/acpi/processor_thermal.c). 110 This will be useful for platforms using the generic thermal interface 111 and not the ACPI interface. 112 113 If you want this support, you should say Y here. 114 115config THERMAL_EMULATION 116 bool "Thermal emulation mode support" 117 help 118 Enable this option to make a emul_temp sysfs node in thermal zone 119 directory to support temperature emulation. With emulation sysfs node, 120 user can manually input temperature and test the different trip 121 threshold behaviour for simulation purpose. 122 123 WARNING: Be careful while enabling this option on production systems, 124 because userland can easily disable the thermal policy by simply 125 flooding this sysfs node with low temperature values. 126 127config IMX_THERMAL 128 tristate "Temperature sensor driver for Freescale i.MX SoCs" 129 depends on CPU_THERMAL 130 depends on MFD_SYSCON 131 depends on OF 132 help 133 Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs. 134 It supports one critical trip point and one passive trip point. The 135 cpufreq is used as the cooling device to throttle CPUs when the 136 passive trip is crossed. 137 138config SPEAR_THERMAL 139 bool "SPEAr thermal sensor driver" 140 depends on PLAT_SPEAR 141 depends on OF 142 help 143 Enable this to plug the SPEAr thermal sensor driver into the Linux 144 thermal framework. 145 146config RCAR_THERMAL 147 tristate "Renesas R-Car thermal driver" 148 depends on ARCH_SHMOBILE || COMPILE_TEST 149 depends on HAS_IOMEM 150 help 151 Enable this to plug the R-Car thermal sensor driver into the Linux 152 thermal framework. 153 154config KIRKWOOD_THERMAL 155 tristate "Temperature sensor on Marvell Kirkwood SoCs" 156 depends on MACH_KIRKWOOD 157 depends on OF 158 help 159 Support for the Kirkwood thermal sensor driver into the Linux thermal 160 framework. Only kirkwood 88F6282 and 88F6283 have this sensor. 161 162config DOVE_THERMAL 163 tristate "Temperature sensor on Marvell Dove SoCs" 164 depends on ARCH_DOVE || MACH_DOVE 165 depends on OF 166 help 167 Support for the Dove thermal sensor driver in the Linux thermal 168 framework. 169 170config DB8500_THERMAL 171 bool "DB8500 thermal management" 172 depends on ARCH_U8500 173 default y 174 help 175 Adds DB8500 thermal management implementation according to the thermal 176 management framework. A thermal zone with several trip points will be 177 created. Cooling devices can be bound to the trip points to cool this 178 thermal zone if trip points reached. 179 180config ARMADA_THERMAL 181 tristate "Armada 370/XP thermal management" 182 depends on ARCH_MVEBU 183 depends on OF 184 help 185 Enable this option if you want to have support for thermal management 186 controller present in Armada 370 and Armada XP SoC. 187 188config DB8500_CPUFREQ_COOLING 189 tristate "DB8500 cpufreq cooling" 190 depends on ARCH_U8500 191 depends on CPU_THERMAL 192 default y 193 help 194 Adds DB8500 cpufreq cooling devices, and these cooling devices can be 195 bound to thermal zone trip points. When a trip point reached, the 196 bound cpufreq cooling device turns active to set CPU frequency low to 197 cool down the CPU. 198 199config INTEL_POWERCLAMP 200 tristate "Intel PowerClamp idle injection driver" 201 depends on THERMAL 202 depends on X86 203 depends on CPU_SUP_INTEL 204 help 205 Enable this to enable Intel PowerClamp idle injection driver. This 206 enforce idle time which results in more package C-state residency. The 207 user interface is exposed via generic thermal framework. 208 209config X86_PKG_TEMP_THERMAL 210 tristate "X86 package temperature thermal driver" 211 depends on X86_THERMAL_VECTOR 212 select THERMAL_GOV_USER_SPACE 213 default m 214 help 215 Enable this to register CPU digital sensor for package temperature as 216 thermal zone. Each package will have its own thermal zone. There are 217 two trip points which can be set by user to get notifications via thermal 218 notification methods. 219 220config INTEL_SOC_DTS_THERMAL 221 tristate "Intel SoCs DTS thermal driver" 222 depends on X86 && IOSF_MBI 223 help 224 Enable this to register Intel SoCs (e.g. Bay Trail) platform digital 225 temperature sensor (DTS). These SoCs have two additional DTSs in 226 addition to DTSs on CPU cores. Each DTS will be registered as a 227 thermal zone. There are two trip points. One of the trip point can 228 be set by user mode programs to get notifications via Linux thermal 229 notification methods.The other trip is a critical trip point, which 230 was set by the driver based on the TJ MAX temperature. 231 232config INT340X_THERMAL 233 tristate "ACPI INT340X thermal drivers" 234 depends on X86 && ACPI 235 select THERMAL_GOV_USER_SPACE 236 select ACPI_THERMAL_REL 237 select ACPI_FAN 238 help 239 Newer laptops and tablets that use ACPI may have thermal sensors and 240 other devices with thermal control capabilities outside the core 241 CPU/SOC, for thermal safety reasons. 242 They are exposed for the OS to use via the INT3400 ACPI device object 243 as the master, and INT3401~INT340B ACPI device objects as the slaves. 244 Enable this to expose the temperature information and cooling ability 245 from these objects to userspace via the normal thermal framework. 246 This means that a wide range of applications and GUI widgets can show 247 the information to the user or use this information for making 248 decisions. For example, the Intel Thermal Daemon can use this 249 information to allow the user to select his laptop to run without 250 turning on the fans. 251 252config ACPI_THERMAL_REL 253 tristate 254 depends on ACPI 255 256menu "Texas Instruments thermal drivers" 257source "drivers/thermal/ti-soc-thermal/Kconfig" 258endmenu 259 260menu "Samsung thermal drivers" 261depends on ARCH_EXYNOS 262source "drivers/thermal/samsung/Kconfig" 263endmenu 264 265menu "STMicroelectronics thermal drivers" 266depends on ARCH_STI && OF 267source "drivers/thermal/st/Kconfig" 268endmenu 269 270endif 271