Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   1) # SPDX-License-Identifier: GPL-2.0-only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   2) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   3) # Generic thermal drivers configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   4) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   5) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   6) menuconfig THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   7) 	bool "Thermal drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   8) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   9) 	  Thermal drivers offer a generic mechanism for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  10) 	  thermal management. Usually it's made up of one or more thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  11) 	  zones and cooling devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  12) 	  Each thermal zone contains its own temperature, trip points,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  13) 	  and cooling devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  14) 	  All platforms with ACPI or Open Firmware thermal support can use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  15) 	  this driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  16) 	  If you want this support, you should say Y here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  17) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  18) if THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  19) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  20) config THERMAL_NETLINK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  21) 	bool "Thermal netlink management"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  22) 	depends on NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  23) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  24) 	  The thermal framework has a netlink interface to do thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  25) 	  zones discovery, temperature readings and events such as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  26) 	  trip point crossed, cooling device update or governor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  27) 	  change. It is recommended to enable the feature.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  28) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  29) config THERMAL_STATISTICS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  30) 	bool "Thermal state transition statistics"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  31) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  32) 	  Export thermal state transition statistics information through sysfs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  33) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  34) 	  If in doubt, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  35) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  36) config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  37) 	int "Emergency poweroff delay in milli-seconds"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  38) 	default 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  39) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  40) 	  Thermal subsystem will issue a graceful shutdown when
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  41) 	  critical temperatures are reached using orderly_poweroff(). In
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  42) 	  case of failure of an orderly_poweroff(), the thermal emergency
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  43) 	  poweroff kicks in after a delay has elapsed and shuts down the system.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  44) 	  This config is number of milliseconds to delay before emergency
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  45) 	  poweroff kicks in. Similarly to the critical trip point,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  46) 	  the delay should be carefully profiled so as to give adequate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  47) 	  time for orderly_poweroff() to finish on regular execution.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  48) 	  If set to 0 emergency poweroff will not be supported.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  49) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  50) 	  In doubt, leave as 0.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  51) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  52) config THERMAL_HWMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  53) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  54) 	prompt "Expose thermal sensors as hwmon device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  55) 	depends on HWMON=y || HWMON=THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  56) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  57) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  58) 	  In case a sensor is registered with the thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  59) 	  framework, this option will also register it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  60) 	  as a hwmon. The sensor will then have the common
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  61) 	  hwmon sysfs interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  62) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  63) 	  Say 'Y' here if you want all thermal sensors to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  64) 	  have hwmon sysfs interface too.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  65) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  66) config THERMAL_OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  67) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  68) 	prompt "APIs to parse thermal data out of device tree"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  69) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  70) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  71) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  72) 	  This options provides helpers to add the support to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  73) 	  read and parse thermal data definitions out of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  74) 	  device tree blob.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  75) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  76) 	  Say 'Y' here if you need to build thermal infrastructure
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  77) 	  based on device tree.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  78) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  79) config THERMAL_WRITABLE_TRIPS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  80) 	bool "Enable writable trip points"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  81) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  82) 	  This option allows the system integrator to choose whether
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  83) 	  trip temperatures can be changed from userspace. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  84) 	  writable trips need to be specified when setting up the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  85) 	  thermal zone but the choice here takes precedence.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  86) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  87) 	  Say 'Y' here if you would like to allow userspace tools to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  88) 	  change trip temperatures.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  89) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  90) choice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  91) 	prompt "Default Thermal governor"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  92) 	default THERMAL_DEFAULT_GOV_STEP_WISE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  93) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  94) 	  This option sets which thermal governor shall be loaded at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  95) 	  startup. If in doubt, select 'step_wise'.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  96) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  97) config THERMAL_DEFAULT_GOV_STEP_WISE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  98) 	bool "step_wise"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  99) 	select THERMAL_GOV_STEP_WISE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) 	  Use the step_wise governor as default. This throttles the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) 	  devices one step at a time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) config THERMAL_DEFAULT_GOV_FAIR_SHARE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) 	bool "fair_share"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) 	select THERMAL_GOV_FAIR_SHARE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) 	  Use the fair_share governor as default. This throttles the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) 	  devices based on their 'contribution' to a zone. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) 	  contribution should be provided through platform data.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) config THERMAL_DEFAULT_GOV_USER_SPACE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) 	bool "user_space"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) 	select THERMAL_GOV_USER_SPACE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) 	  Select this if you want to let the user space manage the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) 	  platform thermals.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) 	bool "power_allocator"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) 	depends on THERMAL_GOV_POWER_ALLOCATOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) 	  Select this if you want to control temperature based on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) 	  system and device power allocation. This governor can only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) 	  operate on cooling devices that implement the power API.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) endchoice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) config THERMAL_GOV_FAIR_SHARE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) 	bool "Fair-share thermal governor"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) 	  Enable this to manage platform thermals using fair-share governor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) config THERMAL_GOV_STEP_WISE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) 	bool "Step_wise thermal governor"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) 	  Enable this to manage platform thermals using a simple linear
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) 	  governor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) config THERMAL_GOV_BANG_BANG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) 	bool "Bang Bang thermal governor"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) 	default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) 	  Enable this to manage platform thermals using bang bang governor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) 	  Say 'Y' here if you want to use two point temperature regulation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) 	  used for fans without throttling.  Some fan drivers depend on this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) 	  governor to be enabled (e.g. acerhdf).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) config THERMAL_GOV_USER_SPACE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) 	bool "User_space thermal governor"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) 	  Enable this to let the user space manage the platform thermals.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) config THERMAL_GOV_POWER_ALLOCATOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) 	bool "Power allocator thermal governor"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) 	depends on ENERGY_MODEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) 	  Enable this to manage platform thermals by dynamically
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) 	  allocating and limiting power to devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) config CPU_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) 	bool "Generic cpu cooling support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) 	depends on THERMAL_OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) 	  Enable the CPU cooling features. If the system has no active
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) 	  cooling device available, this option allows to use the CPU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) 	  as a cooling device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) if CPU_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) config CPU_FREQ_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) 	bool "CPU frequency cooling device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) 	depends on CPU_FREQ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) 	  This implements the generic cpu cooling mechanism through frequency
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) 	  reduction. An ACPI version of this already exists
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) 	  (drivers/acpi/processor_thermal.c).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) 	  This will be useful for platforms using the generic thermal interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) 	  and not the ACPI interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) config CPU_IDLE_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) 	bool "CPU idle cooling device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) 	depends on IDLE_INJECT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) 	  This implements the CPU cooling mechanism through
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) 	  idle injection. This will throttle the CPU by injecting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) 	  idle cycle.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) endif
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) config DEVFREQ_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) 	bool "Generic device cooling support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) 	depends on PM_DEVFREQ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) 	depends on PM_OPP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) 	  This implements the generic devfreq cooling mechanism through
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) 	  frequency reduction for devices using devfreq.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) 	  This will throttle the device by limiting the maximum allowed DVFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) 	  frequency corresponding to the cooling level.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) 	  In order to use the power extensions of the cooling device,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) 	  devfreq should use the simple_ondemand governor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) 	  If you want this support, you should say Y here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) config THERMAL_EMULATION
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) 	bool "Thermal emulation mode support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) 	  Enable this option to make a emul_temp sysfs node in thermal zone
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) 	  directory to support temperature emulation. With emulation sysfs node,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) 	  user can manually input temperature and test the different trip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) 	  threshold behaviour for simulation purpose.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) 	  WARNING: Be careful while enabling this option on production systems,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) 	  because userland can easily disable the thermal policy by simply
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) 	  flooding this sysfs node with low temperature values.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) config THERMAL_MMIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) 	tristate "Generic Thermal MMIO driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) 	depends on OF || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) 	  This option enables the generic thermal MMIO driver that will use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) 	  memory-mapped reads to get the temperature.  Any HW/System that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) 	  allows temperature reading by a single memory-mapped reading, be it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) 	  register or shared memory, is a potential candidate to work with this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) 	  driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) config HISI_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) 	tristate "Hisilicon thermal driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) 	depends on ARCH_HISI || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) 	  Enable this to plug hisilicon's thermal sensor driver into the Linux
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) 	  thermal framework. cpufreq is used as the cooling device to throttle
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) 	  CPUs when the passive trip is crossed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) config IMX_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) 	tristate "Temperature sensor driver for Freescale i.MX SoCs"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) 	depends on ARCH_MXC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) 	depends on NVMEM || !NVMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) 	depends on MFD_SYSCON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) 	  Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) 	  It supports one critical trip point and one passive trip point.  The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) 	  cpufreq is used as the cooling device to throttle CPUs when the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) 	  passive trip is crossed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) config IMX_SC_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) 	tristate "Temperature sensor driver for NXP i.MX SoCs with System Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) 	depends on IMX_SCU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) 	  Support for Temperature Monitor (TEMPMON) found on NXP i.MX SoCs with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) 	  system controller inside, Linux kernel has to communicate with system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) 	  controller via MU (message unit) IPC to get temperature from thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) 	  sensor. It supports one critical trip point and one
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) 	  passive trip point for each thermal sensor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) config IMX8MM_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) 	tristate "Temperature sensor driver for Freescale i.MX8MM SoC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) 	depends on ARCH_MXC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) 	  Support for Thermal Monitoring Unit (TMU) found on Freescale i.MX8MM SoC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) 	  It supports one critical trip point and one passive trip point. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) 	  cpufreq is used as the cooling device to throttle CPUs when the passive
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273) 	  trip is crossed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) config K3_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) 	tristate "Texas Instruments K3 thermal support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) 	depends on ARCH_K3 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) 	  If you say yes here you get thermal support for the Texas Instruments
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) 	  K3 SoC family. The current chip supported is:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) 	  - AM654
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) 	  This includes temperature reading functionality.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) config MAX77620_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) 	tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) 	depends on MFD_MAX77620
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) 	  Support for die junction temperature warning alarm for Maxim
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291) 	  Semiconductor PMIC MAX77620 device. Device generates two alarm
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) 	  interrupts when PMIC die temperature cross the threshold of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293) 	  120 degC and 140 degC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) config QORIQ_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296) 	tristate "QorIQ Thermal Monitoring Unit"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) 	depends on THERMAL_OF && HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) 	depends on PPC_E500MC || SOC_LS1021A || ARCH_LAYERSCAPE || (ARCH_MXC && ARM64) || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299) 	select REGMAP_MMIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) 	  Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302) 	  It supports one critical trip point and one passive trip point. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303) 	  cpufreq is used as the cooling device to throttle CPUs when the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304) 	  passive trip is crossed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306) config SPEAR_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307) 	tristate "SPEAr thermal sensor driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) 	depends on PLAT_SPEAR || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) 	  Enable this to plug the SPEAr thermal sensor driver into the Linux
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) 	  thermal framework.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) config SUN8I_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) 	tristate "Allwinner sun8i thermal driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317) 	depends on ARCH_SUNXI || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) 	depends on NVMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321) 	depends on RESET_CONTROLLER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323) 	  Support for the sun8i thermal sensor driver into the Linux thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) 	  framework.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326) 	  To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) 	  module will be called sun8i-thermal.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) config ROCKCHIP_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) 	tristate "Rockchip thermal driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331) 	depends on ARCH_ROCKCHIP || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332) 	depends on RESET_CONTROLLER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335) 	  Rockchip thermal driver provides support for Temperature sensor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336) 	  ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337) 	  trip point. Cpufreq is used as the cooling device and will throttle
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338) 	  CPUs when the Temperature crosses the passive trip point.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340) config RCAR_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341) 	tristate "Renesas R-Car thermal driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342) 	depends on ARCH_RENESAS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345) 	  Enable this to plug the R-Car thermal sensor driver into the Linux
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346) 	  thermal framework.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) config RCAR_GEN3_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349) 	tristate "Renesas R-Car Gen3 and RZ/G2 thermal driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350) 	depends on ARCH_RENESAS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) 	  Enable this to plug the R-Car Gen3 or RZ/G2 thermal sensor driver into
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355) 	  the Linux thermal framework.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357) config KIRKWOOD_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358) 	tristate "Temperature sensor on Marvell Kirkwood SoCs"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359) 	depends on MACH_KIRKWOOD || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363) 	  Support for the Kirkwood thermal sensor driver into the Linux thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364) 	  framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366) config DOVE_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367) 	tristate "Temperature sensor on Marvell Dove SoCs"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368) 	depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372) 	  Support for the Dove thermal sensor driver in the Linux thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373) 	  framework.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375) config DB8500_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376) 	tristate "DB8500 thermal management"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377) 	depends on MFD_DB8500_PRCMU && OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380) 	  Adds DB8500 thermal management implementation according to the thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381) 	  management framework. A thermal zone with several trip points will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382) 	  created. Cooling devices can be bound to the trip points to cool this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383) 	  thermal zone if trip points reached.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385) config ARMADA_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386) 	tristate "Marvell EBU Armada SoCs thermal management"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387) 	depends on ARCH_MVEBU || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) 	  Enable this option if you want to have support for thermal management
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392) 	  controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394) config DA9062_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395) 	tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396) 	depends on MFD_DA9062 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397) 	depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399) 	  Enable this for the Dialog Semiconductor thermal sensor driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400) 	  This will report PMIC junction over-temperature for one thermal trip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401) 	  zone.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402) 	  Compatible with the DA9062 and DA9061 PMICs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404) config MTK_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405) 	tristate "Temperature sensor driver for mediatek SoCs"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406) 	depends on ARCH_MEDIATEK || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407) 	depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408) 	depends on NVMEM || NVMEM=n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409) 	depends on RESET_CONTROLLER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412) 	  Enable this option if you want to have support for thermal management
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413) 	  controller present in Mediatek SoCs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415) config AMLOGIC_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416) 	tristate "Amlogic Thermal Support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417) 	default ARCH_MESON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418) 	depends on OF && ARCH_MESON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420) 	  If you say yes here you get support for Amlogic Thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421) 	  for G12 SoC Family.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423) 	  This driver can also be built as a module. If so, the module will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424) 	  be called amlogic_thermal.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426) menu "Intel thermal drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427) depends on X86 || X86_INTEL_QUARK || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428) source "drivers/thermal/intel/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429) endmenu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431) menu "Broadcom thermal drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432) depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || ARCH_BCM_IPROC || \
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433) 		COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434) source "drivers/thermal/broadcom/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435) endmenu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) menu "Texas Instruments thermal drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438) depends on ARCH_HAS_BANDGAP || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 440) source "drivers/thermal/ti-soc-thermal/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 441) endmenu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 442) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 443) menu "Samsung thermal drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 444) depends on ARCH_EXYNOS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 445) source "drivers/thermal/samsung/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 446) endmenu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 447) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 448) menu "STMicroelectronics thermal drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 449) depends on (ARCH_STI || ARCH_STM32) && OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 450) source "drivers/thermal/st/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 451) endmenu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 452) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 453) config TANGO_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 454) 	tristate "Tango thermal management"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 455) 	depends on ARCH_TANGO || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 456) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 457) 	  Enable the Tango thermal driver, which supports the primitive
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 458) 	  temperature sensor embedded in Tango chips since the SMP8758.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 459) 	  This sensor only generates a 1-bit signal to indicate whether
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 460) 	  the die temperature exceeds a programmable threshold.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 461) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 462) source "drivers/thermal/tegra/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 463) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 464) config GENERIC_ADC_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 465) 	tristate "Generic ADC based thermal sensor"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 466) 	depends on IIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 467) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 468) 	  This enabled a thermal sysfs driver for the temperature sensor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 469) 	  which is connected to the General Purpose ADC. The ADC channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 470) 	  is read via IIO framework and the channel information is provided
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 471) 	  to this driver. This driver reports the temperature by reading ADC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 472) 	  channel and converts it to temperature based on lookup table.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 473) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 474) menu "Qualcomm thermal drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 475) depends on (ARCH_QCOM && OF) || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 476) source "drivers/thermal/qcom/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 477) endmenu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 478) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 479) config ZX2967_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 480) 	tristate "Thermal sensors on zx2967 SoC"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 481) 	depends on ARCH_ZX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 482) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 483) 	  Enable the zx2967 thermal sensors driver, which supports
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 484) 	  the primitive temperature sensor embedded in zx2967 SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 485) 	  This sensor generates the real time die temperature.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 486) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 487) config UNIPHIER_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 488) 	tristate "Socionext UniPhier thermal driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 489) 	depends on ARCH_UNIPHIER || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 490) 	depends on THERMAL_OF && MFD_SYSCON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 491) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 492) 	  Enable this to plug in UniPhier on-chip PVT thermal driver into the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 493) 	  thermal framework. The driver supports CPU thermal zone temperature
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 494) 	  reporting and a couple of trip points.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 495) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 496) config SPRD_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 497) 	tristate "Temperature sensor on Spreadtrum SoCs"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 498) 	depends on ARCH_SPRD || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 499) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 500) 	  Support for the Spreadtrum thermal sensor driver in the Linux thermal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 501) 	  framework.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 502) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 503) config KHADAS_MCU_FAN_THERMAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 504) 	tristate "Khadas MCU controller FAN cooling support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 505) 	depends on OF || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 506) 	depends on MFD_KHADAS_MCU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 507) 	select MFD_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 508) 	select REGMAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 509) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 510) 	  If you say yes here you get support for the FAN controlled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 511) 	  by the Microcontroller found on the Khadas VIM boards.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 512) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 513) endif