| 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | # |
| 3 | # Hardware monitoring chip drivers configuration |
| 4 | # |
| 5 | |
| 6 | menuconfig HWMON |
| 7 | tristate "Hardware Monitoring support" |
| 8 | depends on HAS_IOMEM |
| 9 | default y |
| 10 | help |
| 11 | Hardware monitoring devices let you monitor the hardware health |
| 12 | of a system. Most modern motherboards include such a device. It |
| 13 | can include temperature sensors, voltage sensors, fan speed |
| 14 | sensors and various additional features such as the ability to |
| 15 | control the speed of the fans. If you want this support you |
| 16 | should say Y here and also to the specific driver(s) for your |
| 17 | sensors chip(s) below. |
| 18 | |
| 19 | To find out which specific driver(s) you need, use the |
| 20 | sensors-detect script from the lm_sensors package. Read |
| 21 | <file:Documentation/hwmon/userspace-tools.rst> for details. |
| 22 | |
| 23 | This support can also be built as a module. If so, the module |
| 24 | will be called hwmon. |
| 25 | |
| 26 | if HWMON |
| 27 | |
| 28 | config HWMON_VID |
| 29 | tristate |
| 30 | |
| 31 | config HWMON_DEBUG_CHIP |
| 32 | bool "Hardware Monitoring Chip debugging messages" |
| 33 | help |
| 34 | Say Y here if you want the I2C chip drivers to produce a bunch of |
| 35 | debug messages to the system log. Select this if you are having |
| 36 | a problem with I2C support and want to see more of what is going |
| 37 | on. |
| 38 | |
| 39 | comment "Native drivers" |
| 40 | |
| 41 | config SENSORS_ABITUGURU |
| 42 | tristate "Abit uGuru (rev 1 & 2)" |
| 43 | depends on (X86 && DMI) || COMPILE_TEST && HAS_IOPORT |
| 44 | help |
| 45 | If you say yes here you get support for the sensor part of the first |
| 46 | and second revision of the Abit uGuru chip. The voltage and frequency |
| 47 | control parts of the Abit uGuru are not supported. The Abit uGuru |
| 48 | chip can be found on Abit uGuru featuring motherboards (most modern |
| 49 | Abit motherboards from before end 2005). For more info and a list |
| 50 | of which motherboards have which revision see |
| 51 | Documentation/hwmon/abituguru.rst |
| 52 | |
| 53 | This driver can also be built as a module. If so, the module |
| 54 | will be called abituguru. |
| 55 | |
| 56 | config SENSORS_ABITUGURU3 |
| 57 | tristate "Abit uGuru (rev 3)" |
| 58 | depends on (X86 && DMI) || COMPILE_TEST && HAS_IOPORT |
| 59 | help |
| 60 | If you say yes here you get support for the sensor part of the |
| 61 | third revision of the Abit uGuru chip. Only reading the sensors |
| 62 | and their settings is supported. The third revision of the Abit |
| 63 | uGuru chip can be found on recent Abit motherboards (since end |
| 64 | 2005). For more info and a list of which motherboards have which |
| 65 | revision see Documentation/hwmon/abituguru3.rst |
| 66 | |
| 67 | This driver can also be built as a module. If so, the module |
| 68 | will be called abituguru3. |
| 69 | |
| 70 | config SENSORS_SMPRO |
| 71 | tristate "Ampere's Altra SMpro hardware monitoring driver" |
| 72 | depends on MFD_SMPRO |
| 73 | help |
| 74 | If you say yes here you get support for the thermal, voltage, |
| 75 | current and power sensors of Ampere's Altra processor family SoC |
| 76 | with SMpro co-processor. |
| 77 | |
| 78 | config SENSORS_AD7314 |
| 79 | tristate "Analog Devices AD7314 and compatibles" |
| 80 | depends on SPI |
| 81 | help |
| 82 | If you say yes here you get support for the Analog Devices |
| 83 | AD7314, ADT7301 and ADT7302 temperature sensors. |
| 84 | |
| 85 | This driver can also be built as a module. If so, the module |
| 86 | will be called ad7314. |
| 87 | |
| 88 | config SENSORS_AD7414 |
| 89 | tristate "Analog Devices AD7414" |
| 90 | depends on I2C |
| 91 | help |
| 92 | If you say yes here you get support for the Analog Devices |
| 93 | AD7414 temperature monitoring chip. |
| 94 | |
| 95 | This driver can also be built as a module. If so, the module |
| 96 | will be called ad7414. |
| 97 | |
| 98 | config SENSORS_AD7418 |
| 99 | tristate "Analog Devices AD7416, AD7417 and AD7418" |
| 100 | depends on I2C |
| 101 | help |
| 102 | If you say yes here you get support for the Analog Devices |
| 103 | AD7416, AD7417 and AD7418 temperature monitoring chips. |
| 104 | |
| 105 | This driver can also be built as a module. If so, the module |
| 106 | will be called ad7418. |
| 107 | |
| 108 | config SENSORS_ADM1025 |
| 109 | tristate "Analog Devices ADM1025 and compatibles" |
| 110 | depends on I2C |
| 111 | select HWMON_VID |
| 112 | help |
| 113 | If you say yes here you get support for Analog Devices ADM1025 |
| 114 | and Philips NE1619 sensor chips. |
| 115 | |
| 116 | This driver can also be built as a module. If so, the module |
| 117 | will be called adm1025. |
| 118 | |
| 119 | config SENSORS_ADM1026 |
| 120 | tristate "Analog Devices ADM1026 and compatibles" |
| 121 | depends on I2C |
| 122 | select HWMON_VID |
| 123 | help |
| 124 | If you say yes here you get support for Analog Devices ADM1026 |
| 125 | sensor chip. |
| 126 | |
| 127 | This driver can also be built as a module. If so, the module |
| 128 | will be called adm1026. |
| 129 | |
| 130 | config SENSORS_ADM1029 |
| 131 | tristate "Analog Devices ADM1029" |
| 132 | depends on I2C |
| 133 | help |
| 134 | If you say yes here you get support for Analog Devices ADM1029 |
| 135 | sensor chip. |
| 136 | Very rare chip, please let us know you use it. |
| 137 | |
| 138 | This driver can also be built as a module. If so, the module |
| 139 | will be called adm1029. |
| 140 | |
| 141 | config SENSORS_ADM1031 |
| 142 | tristate "Analog Devices ADM1031 and compatibles" |
| 143 | depends on I2C |
| 144 | help |
| 145 | If you say yes here you get support for Analog Devices ADM1031 |
| 146 | and ADM1030 sensor chips. |
| 147 | |
| 148 | This driver can also be built as a module. If so, the module |
| 149 | will be called adm1031. |
| 150 | |
| 151 | config SENSORS_ADM1177 |
| 152 | tristate "Analog Devices ADM1177 and compatibles" |
| 153 | depends on I2C |
| 154 | help |
| 155 | If you say yes here you get support for Analog Devices ADM1177 |
| 156 | sensor chips. |
| 157 | |
| 158 | This driver can also be built as a module. If so, the module |
| 159 | will be called adm1177. |
| 160 | |
| 161 | config SENSORS_ADM9240 |
| 162 | tristate "Analog Devices ADM9240 and compatibles" |
| 163 | depends on I2C |
| 164 | select HWMON_VID |
| 165 | select REGMAP_I2C |
| 166 | help |
| 167 | If you say yes here you get support for Analog Devices ADM9240, |
| 168 | Dallas DS1780, National Semiconductor LM81 sensor chips. |
| 169 | |
| 170 | This driver can also be built as a module. If so, the module |
| 171 | will be called adm9240. |
| 172 | |
| 173 | config SENSORS_ADT7X10 |
| 174 | tristate |
| 175 | select REGMAP |
| 176 | help |
| 177 | This module contains common code shared by the ADT7310/ADT7320 and |
| 178 | ADT7410/ADT7420/ADT7422 temperature monitoring chip drivers. |
| 179 | |
| 180 | If built as a module, the module will be called adt7x10. |
| 181 | |
| 182 | config SENSORS_ADT7310 |
| 183 | tristate "Analog Devices ADT7310/ADT7320" |
| 184 | depends on SPI_MASTER |
| 185 | select SENSORS_ADT7X10 |
| 186 | help |
| 187 | If you say yes here you get support for the Analog Devices |
| 188 | ADT7310 and ADT7320 temperature monitoring chips. |
| 189 | |
| 190 | This driver can also be built as a module. If so, the module |
| 191 | will be called adt7310. |
| 192 | |
| 193 | config SENSORS_ADT7410 |
| 194 | tristate "Analog Devices ADT7410/ADT7420/ADT7422" |
| 195 | depends on I2C |
| 196 | select SENSORS_ADT7X10 |
| 197 | help |
| 198 | If you say yes here you get support for the Analog Devices |
| 199 | ADT7410, ADT7420 and ADT7422 temperature monitoring chips. |
| 200 | |
| 201 | This driver can also be built as a module. If so, the module |
| 202 | will be called adt7410. |
| 203 | |
| 204 | config SENSORS_ADT7411 |
| 205 | tristate "Analog Devices ADT7411" |
| 206 | depends on I2C |
| 207 | help |
| 208 | If you say yes here you get support for the Analog Devices |
| 209 | ADT7411 voltage and temperature monitoring chip. |
| 210 | |
| 211 | This driver can also be built as a module. If so, the module |
| 212 | will be called adt7411. |
| 213 | |
| 214 | config SENSORS_ADT7462 |
| 215 | tristate "Analog Devices ADT7462" |
| 216 | depends on I2C |
| 217 | help |
| 218 | If you say yes here you get support for the Analog Devices |
| 219 | ADT7462 temperature monitoring chips. |
| 220 | |
| 221 | This driver can also be built as a module. If so, the module |
| 222 | will be called adt7462. |
| 223 | |
| 224 | config SENSORS_ADT7470 |
| 225 | tristate "Analog Devices ADT7470" |
| 226 | depends on I2C |
| 227 | depends on PWM || PWM=n |
| 228 | select REGMAP_I2C |
| 229 | help |
| 230 | If you say yes here you get support for the Analog Devices |
| 231 | ADT7470 temperature monitoring chips. |
| 232 | |
| 233 | This driver can also be built as a module. If so, the module |
| 234 | will be called adt7470. |
| 235 | |
| 236 | config SENSORS_ADT7475 |
| 237 | tristate "Analog Devices ADT7473, ADT7475, ADT7476 and ADT7490" |
| 238 | depends on I2C |
| 239 | select HWMON_VID |
| 240 | help |
| 241 | If you say yes here you get support for the Analog Devices |
| 242 | ADT7473, ADT7475, ADT7476 and ADT7490 hardware monitoring |
| 243 | chips. |
| 244 | |
| 245 | This driver can also be built as a module. If so, the module |
| 246 | will be called adt7475. |
| 247 | |
| 248 | config SENSORS_AHT10 |
| 249 | tristate "Aosong AHT10, AHT20, DHT20" |
| 250 | depends on I2C |
| 251 | select CRC8 |
| 252 | help |
| 253 | If you say yes here, you get support for the Aosong AHT10, AHT20 and |
| 254 | DHT20 temperature and humidity sensors |
| 255 | |
| 256 | This driver can also be built as a module. If so, the module |
| 257 | will be called aht10. |
| 258 | |
| 259 | config SENSORS_AQUACOMPUTER_D5NEXT |
| 260 | tristate "Aquacomputer D5 Next, Octo, Quadro, Farbwerk, Farbwerk 360, High Flow Next" |
| 261 | depends on USB_HID |
| 262 | select CRC16 |
| 263 | help |
| 264 | If you say yes here you get support for sensors and fans of |
| 265 | the Aquacomputer D5 Next watercooling pump, Octo and Quadro fan |
| 266 | controllers, Farbwerk and Farbwerk 360 RGB controllers, High Flow |
| 267 | Next sensor, where available. |
| 268 | |
| 269 | This driver can also be built as a module. If so, the module |
| 270 | will be called aquacomputer_d5next. |
| 271 | |
| 272 | config SENSORS_AS370 |
| 273 | tristate "Synaptics AS370 SoC hardware monitoring driver" |
| 274 | help |
| 275 | If you say yes here you get support for the PVT sensors of |
| 276 | the Synaptics AS370 SoC |
| 277 | |
| 278 | This driver can also be built as a module. If so, the module |
| 279 | will be called as370-hwmon. |
| 280 | |
| 281 | |
| 282 | config SENSORS_ASC7621 |
| 283 | tristate "Andigilog aSC7621" |
| 284 | depends on I2C |
| 285 | help |
| 286 | If you say yes here you get support for the aSC7621 |
| 287 | family of SMBus sensors chip found on most Intel X38, X48, X58, |
| 288 | 945, 965 and 975 desktop boards. Currently supported chips: |
| 289 | aSC7621 |
| 290 | aSC7621a |
| 291 | |
| 292 | This driver can also be built as a module. If so, the module |
| 293 | will be called asc7621. |
| 294 | |
| 295 | config SENSORS_ASUS_ROG_RYUJIN |
| 296 | tristate "ASUS ROG RYUJIN hardware monitoring driver" |
| 297 | depends on HID |
| 298 | help |
| 299 | If you say yes here you get support for the fans and sensors of |
| 300 | supported ASUS ROG RYUJIN II and III AIO CPU liquid coolers. |
| 301 | |
| 302 | This driver can also be built as a module. If so, the module |
| 303 | will be called asus_rog_ryujin. |
| 304 | |
| 305 | config SENSORS_AXI_FAN_CONTROL |
| 306 | tristate "Analog Devices FAN Control HDL Core driver" |
| 307 | help |
| 308 | If you say yes here you get support for the Analog Devices |
| 309 | AXI HDL FAN monitoring core. |
| 310 | |
| 311 | This driver can also be built as a module. If so, the module |
| 312 | will be called axi-fan-control |
| 313 | |
| 314 | config SENSORS_K8TEMP |
| 315 | tristate "AMD Athlon64/FX or Opteron temperature sensor" |
| 316 | depends on X86 && PCI |
| 317 | help |
| 318 | If you say yes here you get support for the temperature |
| 319 | sensor(s) inside your CPU. Supported is whole AMD K8 |
| 320 | microarchitecture. Please note that you will need at least |
| 321 | lm-sensors 2.10.1 for proper userspace support. |
| 322 | |
| 323 | This driver can also be built as a module. If so, the module |
| 324 | will be called k8temp. |
| 325 | |
| 326 | config SENSORS_K10TEMP |
| 327 | tristate "AMD Family 10h+ temperature sensor" |
| 328 | depends on X86 && PCI && AMD_NODE |
| 329 | help |
| 330 | If you say yes here you get support for the temperature |
| 331 | sensor(s) inside your CPU. Supported are later revisions of |
| 332 | the AMD Family 10h and all revisions of the AMD Family 11h, |
| 333 | 12h (Llano), 14h (Brazos), 15h (Bulldozer/Trinity/Kaveri/Carrizo) |
| 334 | and 16h (Kabini/Mullins) microarchitectures. |
| 335 | |
| 336 | This driver can also be built as a module. If so, the module |
| 337 | will be called k10temp. |
| 338 | |
| 339 | config SENSORS_KB9002 |
| 340 | tristate "Kandou KB9002 PCIe retimer" |
| 341 | depends on I2C |
| 342 | help |
| 343 | If you say yes here you get support for the integrated |
| 344 | temperature sensor and firmware version readout on Kandou |
| 345 | KB9002 PCIe 5.0 retimers, accessed over SMBus. |
| 346 | |
| 347 | This driver can also be built as a module. If so, the module |
| 348 | will be called kb9002. |
| 349 | |
| 350 | config SENSORS_KBATT |
| 351 | tristate "KEBA battery controller support" |
| 352 | depends on KEBA_CP500 |
| 353 | help |
| 354 | This driver supports the battery monitoring controller found in |
| 355 | KEBA system FPGA devices. |
| 356 | |
| 357 | This driver can also be built as a module. If so, the module |
| 358 | will be called kbatt. |
| 359 | |
| 360 | config SENSORS_KFAN |
| 361 | tristate "KEBA fan controller support" |
| 362 | depends on KEBA_CP500 |
| 363 | help |
| 364 | This driver supports the fan controller found in KEBA system |
| 365 | FPGA devices. |
| 366 | |
| 367 | This driver can also be built as a module. If so, the module |
| 368 | will be called kfan. |
| 369 | |
| 370 | config SENSORS_FAM15H_POWER |
| 371 | tristate "AMD Family 15h processor power" |
| 372 | depends on X86 && PCI && CPU_SUP_AMD |
| 373 | help |
| 374 | If you say yes here you get support for processor power |
| 375 | information of your AMD family 15h CPU. |
| 376 | |
| 377 | This driver can also be built as a module. If so, the module |
| 378 | will be called fam15h_power. |
| 379 | |
| 380 | config SENSORS_APPLESMC |
| 381 | tristate "Apple SMC (Motion sensor, light sensor, keyboard backlight)" |
| 382 | depends on INPUT && X86 |
| 383 | select NEW_LEDS |
| 384 | select LEDS_CLASS |
| 385 | help |
| 386 | This driver provides support for the Apple System Management |
| 387 | Controller, which provides an accelerometer (Apple Sudden Motion |
| 388 | Sensor), light sensors, temperature sensors, keyboard backlight |
| 389 | control and fan control. |
| 390 | |
| 391 | Only Intel-based Apple's computers are supported (MacBook Pro, |
| 392 | MacBook, MacMini). |
| 393 | |
| 394 | Data from the different sensors, keyboard backlight control and fan |
| 395 | control are accessible via sysfs. |
| 396 | |
| 397 | This driver also provides an absolute input class device, allowing |
| 398 | the laptop to act as a pinball machine-esque joystick. |
| 399 | |
| 400 | Say Y here if you have an applicable laptop and want to experience |
| 401 | the awesome power of applesmc. |
| 402 | |
| 403 | config SENSORS_ARCTIC_FAN_CONTROLLER |
| 404 | tristate "ARCTIC Fan Controller" |
| 405 | depends on USB_HID |
| 406 | help |
| 407 | If you say yes here you get support for the ARCTIC Fan Controller, |
| 408 | a USB HID device (VID 0x3904, PID 0xF001) with 10 fan channels. |
| 409 | The driver exposes fan speed (RPM) and PWM control via the hwmon |
| 410 | sysfs interface. |
| 411 | |
| 412 | This driver can also be built as a module. If so, the module |
| 413 | will be called arctic_fan_controller. |
| 414 | |
| 415 | config SENSORS_ARM_SCMI |
| 416 | tristate "ARM SCMI Sensors" |
| 417 | depends on ARM_SCMI_PROTOCOL |
| 418 | help |
| 419 | This driver provides support for temperature, voltage, current |
| 420 | and power sensors available on SCMI based platforms. The actual |
| 421 | number and type of sensors exported depend on the platform. |
| 422 | |
| 423 | This driver can also be built as a module. If so, the module |
| 424 | will be called scmi-hwmon. |
| 425 | |
| 426 | config SENSORS_ARM_SCPI |
| 427 | tristate "ARM SCPI Sensors" |
| 428 | depends on ARM_SCPI_PROTOCOL |
| 429 | help |
| 430 | This driver provides support for temperature, voltage, current |
| 431 | and power sensors available on ARM Ltd's SCP based platforms. The |
| 432 | actual number and type of sensors exported depend on the platform. |
| 433 | |
| 434 | config SENSORS_ASB100 |
| 435 | tristate "Asus ASB100 Bach" |
| 436 | depends on (X86 || COMPILE_TEST) && I2C |
| 437 | select HWMON_VID |
| 438 | help |
| 439 | If you say yes here you get support for the ASB100 Bach sensor |
| 440 | chip found on some Asus mainboards. |
| 441 | |
| 442 | This driver can also be built as a module. If so, the module |
| 443 | will be called asb100. |
| 444 | |
| 445 | config SENSORS_ASPEED |
| 446 | tristate "ASPEED AST2400/AST2500 PWM and Fan tach driver" |
| 447 | depends on ARCH_ASPEED || COMPILE_TEST |
| 448 | select REGMAP |
| 449 | help |
| 450 | This driver provides support for ASPEED AST2400/AST2500 PWM |
| 451 | and Fan Tacho controllers. |
| 452 | |
| 453 | This driver can also be built as a module. If so, the module |
| 454 | will be called aspeed_pwm_tacho. |
| 455 | |
| 456 | config SENSORS_ASPEED_G6 |
| 457 | tristate "ASPEED G6 PWM and Fan tach driver" |
| 458 | depends on ARCH_ASPEED || COMPILE_TEST |
| 459 | depends on PWM |
| 460 | help |
| 461 | This driver provides support for ASPEED G6 PWM and Fan Tach |
| 462 | controllers. |
| 463 | |
| 464 | This driver can also be built as a module. If so, the module |
| 465 | will be called aspeed_g6_pwm_tach. |
| 466 | |
| 467 | config SENSORS_ATXP1 |
| 468 | tristate "Attansic ATXP1 VID controller" |
| 469 | depends on I2C |
| 470 | select HWMON_VID |
| 471 | help |
| 472 | If you say yes here you get support for the Attansic ATXP1 VID |
| 473 | controller. |
| 474 | |
| 475 | If your board have such a chip, you are able to control your CPU |
| 476 | core and other voltages. |
| 477 | |
| 478 | This driver can also be built as a module. If so, the module |
| 479 | will be called atxp1. |
| 480 | |
| 481 | config SENSORS_CGBC |
| 482 | tristate "Congatec Board Controller Sensors" |
| 483 | depends on MFD_CGBC |
| 484 | help |
| 485 | Enable sensors support for the Congatec Board Controller. It has |
| 486 | temperature, voltage, current and fan sensors. |
| 487 | |
| 488 | This driver can also be built as a module. If so, the module will be |
| 489 | called cgbc-hwmon. |
| 490 | |
| 491 | config SENSORS_CHIPCAP2 |
| 492 | tristate "Amphenol ChipCap 2 relative humidity and temperature sensor" |
| 493 | depends on I2C |
| 494 | help |
| 495 | Say yes here to build support for the Amphenol ChipCap 2 |
| 496 | relative humidity and temperature sensor. |
| 497 | |
| 498 | To compile this driver as a module, choose M here: the module |
| 499 | will be called chipcap2. |
| 500 | |
| 501 | config SENSORS_CORSAIR_CPRO |
| 502 | tristate "Corsair Commander Pro controller" |
| 503 | depends on HID |
| 504 | help |
| 505 | If you say yes here you get support for the Corsair Commander Pro |
| 506 | controller. |
| 507 | |
| 508 | This driver can also be built as a module. If so, the module |
| 509 | will be called corsair-cpro. |
| 510 | |
| 511 | config SENSORS_CORSAIR_PSU |
| 512 | tristate "Corsair PSU HID controller" |
| 513 | depends on HID |
| 514 | help |
| 515 | If you say yes here you get support for Corsair PSUs with a HID |
| 516 | interface. |
| 517 | Currently this driver supports the (RM/HX)550i, (RM/HX)650i, |
| 518 | (RM/HX)750i, (RM/HX)850i, (RM/HX)1000i, HX1200i and HX1500i power |
| 519 | supplies by Corsair. |
| 520 | |
| 521 | This driver can also be built as a module. If so, the module |
| 522 | will be called corsair-psu. |
| 523 | |
| 524 | config SENSORS_CROS_EC |
| 525 | tristate "ChromeOS Embedded Controller sensors" |
| 526 | depends on MFD_CROS_EC_DEV |
| 527 | default MFD_CROS_EC_DEV |
| 528 | help |
| 529 | If you say yes here you get support for ChromeOS Embedded Controller |
| 530 | sensors. |
| 531 | |
| 532 | This driver can also be built as a module. If so, the module |
| 533 | will be called cros_ec_hwmon. |
| 534 | |
| 535 | config SENSORS_DRIVETEMP |
| 536 | tristate "Hard disk drives with temperature sensors" |
| 537 | depends on SCSI && ATA |
| 538 | help |
| 539 | If you say yes you get support for the temperature sensor on |
| 540 | hard disk drives. |
| 541 | |
| 542 | This driver can also be built as a module. If so, the module |
| 543 | will be called drivetemp. |
| 544 | |
| 545 | config SENSORS_DS620 |
| 546 | tristate "Dallas Semiconductor DS620" |
| 547 | depends on I2C |
| 548 | help |
| 549 | If you say yes here you get support for Dallas Semiconductor |
| 550 | DS620 sensor chip. |
| 551 | |
| 552 | This driver can also be built as a module. If so, the module |
| 553 | will be called ds620. |
| 554 | |
| 555 | config SENSORS_DS1621 |
| 556 | tristate "Dallas Semiconductor DS1621 and compatibles" |
| 557 | depends on I2C |
| 558 | help |
| 559 | If you say yes here you get support for Dallas Semiconductor/Maxim |
| 560 | Integrated DS1621 sensor chips and compatible models including: |
| 561 | |
| 562 | - Dallas Semiconductor DS1625 |
| 563 | - Maxim Integrated DS1631 |
| 564 | - Maxim Integrated DS1721 |
| 565 | - Maxim Integrated DS1731 |
| 566 | |
| 567 | This driver can also be built as a module. If so, the module |
| 568 | will be called ds1621. |
| 569 | |
| 570 | config SENSORS_DELL_SMM |
| 571 | tristate "Dell laptop SMM BIOS hwmon driver" |
| 572 | depends on ACPI_WMI |
| 573 | depends on X86 |
| 574 | imply THERMAL |
| 575 | help |
| 576 | This hwmon driver adds support for reporting temperature of different |
| 577 | sensors and controls the fans on Dell laptops via System Management |
| 578 | Mode provided by Dell BIOS. |
| 579 | |
| 580 | When option I8K is also enabled this driver provides legacy /proc/i8k |
| 581 | userspace interface for i8kutils package. |
| 582 | |
| 583 | config I8K |
| 584 | bool "Legacy /proc/i8k interface of Dell laptop SMM BIOS hwmon driver" |
| 585 | depends on SENSORS_DELL_SMM |
| 586 | depends on PROC_FS |
| 587 | help |
| 588 | This option enables the legacy /proc/i8k userspace interface of the |
| 589 | dell-smm-hwmon driver. The character file /proc/i8k exposes the BIOS |
| 590 | version, temperatures and allows control of fan speeds of some Dell |
| 591 | laptops. Sometimes it also reports power and hotkey status. |
| 592 | |
| 593 | This interface is required to run programs from the i8kutils package. |
| 594 | |
| 595 | Say Y if you intend to run userspace programs that use this interface. |
| 596 | Say N otherwise. |
| 597 | |
| 598 | config SENSORS_DA9052_ADC |
| 599 | tristate "Dialog DA9052/DA9053 ADC" |
| 600 | depends on PMIC_DA9052 |
| 601 | help |
| 602 | Say y here to support the ADC found on Dialog Semiconductor |
| 603 | DA9052-BC and DA9053-AA/Bx PMICs. |
| 604 | |
| 605 | This driver can also be built as module. If so, the module |
| 606 | will be called da9052-hwmon. |
| 607 | |
| 608 | config SENSORS_DA9055 |
| 609 | tristate "Dialog Semiconductor DA9055 ADC" |
| 610 | depends on MFD_DA9055 |
| 611 | help |
| 612 | If you say yes here you get support for ADC on the Dialog |
| 613 | Semiconductor DA9055 PMIC. |
| 614 | |
| 615 | This driver can also be built as a module. If so, the module |
| 616 | will be called da9055-hwmon. |
| 617 | |
| 618 | config SENSORS_I5K_AMB |
| 619 | tristate "FB-DIMM AMB temperature sensor on Intel 5000 series chipsets" |
| 620 | depends on PCI |
| 621 | help |
| 622 | If you say yes here you get support for FB-DIMM AMB temperature |
| 623 | monitoring chips on systems with the Intel 5000 series chipset. |
| 624 | |
| 625 | This driver can also be built as a module. If so, the module |
| 626 | will be called i5k_amb. |
| 627 | |
| 628 | config SENSORS_SPARX5 |
| 629 | tristate "Sparx5 SoC temperature sensor" |
| 630 | depends on ARCH_SPARX5 || ARCH_LAN969X || COMPILE_TEST |
| 631 | help |
| 632 | If you say yes here you get support for temperature monitoring |
| 633 | with the Microchip Sparx5 SoC. |
| 634 | |
| 635 | This driver can also be built as a module. If so, the module |
| 636 | will be called sparx5-temp. |
| 637 | |
| 638 | config SENSORS_F71805F |
| 639 | tristate "Fintek F71805F/FG, F71806F/FG and F71872F/FG" |
| 640 | depends on HAS_IOPORT |
| 641 | depends on !PPC |
| 642 | help |
| 643 | If you say yes here you get support for hardware monitoring |
| 644 | features of the Fintek F71805F/FG, F71806F/FG and F71872F/FG |
| 645 | Super-I/O chips. |
| 646 | |
| 647 | This driver can also be built as a module. If so, the module |
| 648 | will be called f71805f. |
| 649 | |
| 650 | config SENSORS_F71882FG |
| 651 | tristate "Fintek F71882FG and compatibles" |
| 652 | depends on HAS_IOPORT |
| 653 | depends on !PPC |
| 654 | help |
| 655 | If you say yes here you get support for hardware monitoring |
| 656 | features of many Fintek Super-I/O (LPC) chips. The currently |
| 657 | supported chips are: |
| 658 | F71808E/A |
| 659 | F71858FG |
| 660 | F71862FG |
| 661 | F71863FG |
| 662 | F71869F/E/A |
| 663 | F71882FG |
| 664 | F71883FG |
| 665 | F71889FG/ED/A |
| 666 | F8000 |
| 667 | F81801U |
| 668 | F81865F |
| 669 | |
| 670 | This driver can also be built as a module. If so, the module |
| 671 | will be called f71882fg. |
| 672 | |
| 673 | config SENSORS_F75375S |
| 674 | tristate "Fintek F75375S/SP, F75373 and F75387" |
| 675 | depends on I2C |
| 676 | help |
| 677 | If you say yes here you get support for hardware monitoring |
| 678 | features of the Fintek F75375S/SP, F75373 and F75387 |
| 679 | |
| 680 | This driver can also be built as a module. If so, the module |
| 681 | will be called f75375s. |
| 682 | |
| 683 | config SENSORS_GSC |
| 684 | tristate "Gateworks System Controller ADC" |
| 685 | depends on MFD_GATEWORKS_GSC |
| 686 | help |
| 687 | Support for the Gateworks System Controller A/D converters. |
| 688 | |
| 689 | To compile this driver as a module, choose M here: |
| 690 | the module will be called gsc-hwmon. |
| 691 | |
| 692 | config SENSORS_MC13783_ADC |
| 693 | tristate "Freescale MC13783/MC13892 ADC" |
| 694 | depends on MFD_MC13XXX |
| 695 | help |
| 696 | Support for the A/D converter on MC13783 and MC13892 PMIC. |
| 697 | |
| 698 | config SENSORS_MC33XS2410 |
| 699 | tristate "MC33XS2410 HWMON support" |
| 700 | depends on PWM_MC33XS2410 |
| 701 | help |
| 702 | If you say yes here you get hardware monitoring support for |
| 703 | MC33XS2410. |
| 704 | |
| 705 | This driver can also be built as a module. If so, the module |
| 706 | will be called mc33xs2410_hwmon. |
| 707 | |
| 708 | config SENSORS_FSCHMD |
| 709 | tristate "Fujitsu Siemens Computers sensor chips" |
| 710 | depends on (X86 || COMPILE_TEST) && I2C |
| 711 | help |
| 712 | If you say yes here you get support for the following Fujitsu |
| 713 | Siemens Computers (FSC) sensor chips: Poseidon, Scylla, Hermes, |
| 714 | Heimdall, Heracles, Hades and Syleus including support for the |
| 715 | integrated watchdog. |
| 716 | |
| 717 | This is a merged driver for FSC sensor chips replacing the fscpos, |
| 718 | fscscy and fscher drivers and adding support for several other FSC |
| 719 | sensor chips. |
| 720 | |
| 721 | This driver can also be built as a module. If so, the module |
| 722 | will be called fschmd. |
| 723 | |
| 724 | config SENSORS_FTSTEUTATES |
| 725 | tristate "Fujitsu Technology Solutions sensor chip Teutates" |
| 726 | depends on I2C && WATCHDOG |
| 727 | select WATCHDOG_CORE |
| 728 | help |
| 729 | If you say yes here you get support for the Fujitsu Technology |
| 730 | Solutions (FTS) sensor chip "Teutates" including support for |
| 731 | the integrated watchdog. |
| 732 | |
| 733 | This driver can also be built as a module. If so, the module |
| 734 | will be called ftsteutates. |
| 735 | |
| 736 | config SENSORS_GIGABYTE_WATERFORCE |
| 737 | tristate "Gigabyte Waterforce X240/X280/X360 AIO CPU coolers" |
| 738 | depends on USB_HID |
| 739 | help |
| 740 | If you say yes here you get support for hardware monitoring for the |
| 741 | Gigabyte Waterforce X240/X280/X360 all-in-one CPU liquid coolers. |
| 742 | |
| 743 | This driver can also be built as a module. If so, the module |
| 744 | will be called gigabyte_waterforce. |
| 745 | |
| 746 | config SENSORS_GL518SM |
| 747 | tristate "Genesys Logic GL518SM" |
| 748 | depends on I2C |
| 749 | help |
| 750 | If you say yes here you get support for Genesys Logic GL518SM |
| 751 | sensor chips. |
| 752 | |
| 753 | This driver can also be built as a module. If so, the module |
| 754 | will be called gl518sm. |
| 755 | |
| 756 | config SENSORS_GL520SM |
| 757 | tristate "Genesys Logic GL520SM" |
| 758 | depends on I2C |
| 759 | select HWMON_VID |
| 760 | help |
| 761 | If you say yes here you get support for Genesys Logic GL520SM |
| 762 | sensor chips. |
| 763 | |
| 764 | This driver can also be built as a module. If so, the module |
| 765 | will be called gl520sm. |
| 766 | |
| 767 | config SENSORS_GPD |
| 768 | tristate "GPD handhelds" |
| 769 | depends on X86 && DMI && HAS_IOPORT |
| 770 | help |
| 771 | If you say yes here you get support for fan readings and |
| 772 | control over GPD handheld devices. |
| 773 | |
| 774 | Can also be built as a module. In that case it will be |
| 775 | called gpd-fan. |
| 776 | |
| 777 | config SENSORS_G760A |
| 778 | tristate "GMT G760A" |
| 779 | depends on I2C |
| 780 | help |
| 781 | If you say yes here you get support for Global Mixed-mode |
| 782 | Technology Inc G760A fan speed PWM controller chips. |
| 783 | |
| 784 | This driver can also be built as a module. If so, the module |
| 785 | will be called g760a. |
| 786 | |
| 787 | config SENSORS_G762 |
| 788 | tristate "GMT G762 and G763" |
| 789 | depends on I2C |
| 790 | help |
| 791 | If you say yes here you get support for Global Mixed-mode |
| 792 | Technology Inc G762 and G763 fan speed PWM controller chips. |
| 793 | |
| 794 | This driver can also be built as a module. If so, the module |
| 795 | will be called g762. |
| 796 | |
| 797 | config SENSORS_GPIO_FAN |
| 798 | tristate "GPIO fan" |
| 799 | depends on GPIOLIB || COMPILE_TEST |
| 800 | help |
| 801 | If you say yes here you get support for fans connected to GPIO lines. |
| 802 | |
| 803 | This driver can also be built as a module. If so, the module |
| 804 | will be called gpio-fan. |
| 805 | |
| 806 | config SENSORS_GXP_FAN_CTRL |
| 807 | tristate "HPE GXP fan controller" |
| 808 | depends on ARCH_HPE_GXP || COMPILE_TEST |
| 809 | help |
| 810 | If you say yes here you get support for GXP fan control functionality. |
| 811 | |
| 812 | The GXP controls fan function via the CPLD through the use of PWM |
| 813 | registers. This driver enables pwm setting of the fans. |
| 814 | |
| 815 | config SENSORS_HIH6130 |
| 816 | tristate "Honeywell Humidicon HIH-6130 humidity/temperature sensor" |
| 817 | depends on I2C |
| 818 | help |
| 819 | If you say yes here you get support for Honeywell Humidicon |
| 820 | HIH-6130 and HIH-6131 Humidicon humidity sensors. |
| 821 | |
| 822 | This driver can also be built as a module. If so, the module |
| 823 | will be called hih6130. |
| 824 | |
| 825 | config SENSORS_HS3001 |
| 826 | tristate "Renesas HS3001 humidity and temperature sensors" |
| 827 | depends on I2C |
| 828 | help |
| 829 | If you say yes here you get support for the Renesas HS3001, |
| 830 | to HS3004 humidity and temperature sensors. |
| 831 | |
| 832 | This driver can also be built as a module. If so, the module |
| 833 | will be called hs3001. |
| 834 | |
| 835 | config SENSORS_HTU31 |
| 836 | tristate "Measurement Specialties HTU31 humidity and temperature sensor" |
| 837 | depends on I2C |
| 838 | select CRC8 |
| 839 | help |
| 840 | If you say yes here you get support for the HTU31 humidity |
| 841 | and temperature sensors. |
| 842 | |
| 843 | This driver can also be built as a module. If so, the module |
| 844 | will be called htu31. |
| 845 | |
| 846 | config SENSORS_IBMAEM |
| 847 | tristate "IBM Active Energy Manager temperature/power sensors and control" |
| 848 | select IPMI_SI |
| 849 | depends on IPMI_HANDLER |
| 850 | help |
| 851 | If you say yes here you get support for the temperature and |
| 852 | power sensors and capping hardware in various IBM System X |
| 853 | servers that support Active Energy Manager. This includes |
| 854 | the x3350, x3550, x3650, x3655, x3755, x3850 M2, x3950 M2, |
| 855 | and certain HC10/HS2x/LS2x/QS2x blades. |
| 856 | |
| 857 | This driver can also be built as a module. If so, the module |
| 858 | will be called ibmaem. |
| 859 | |
| 860 | config SENSORS_IBMPEX |
| 861 | tristate "IBM PowerExecutive temperature/power sensors" |
| 862 | select IPMI_SI |
| 863 | depends on IPMI_HANDLER |
| 864 | help |
| 865 | If you say yes here you get support for the temperature and |
| 866 | power sensors in various IBM System X servers that support |
| 867 | PowerExecutive. So far this includes the x3350, x3550, x3650, |
| 868 | x3655, and x3755; the x3800, x3850, and x3950 models that have |
| 869 | PCI Express; and some of the HS2x, LS2x, and QS2x blades. |
| 870 | |
| 871 | This driver can also be built as a module. If so, the module |
| 872 | will be called ibmpex. |
| 873 | |
| 874 | config SENSORS_IBMPOWERNV |
| 875 | tristate "IBM POWERNV platform sensors" |
| 876 | depends on PPC_POWERNV |
| 877 | default y |
| 878 | help |
| 879 | If you say yes here you get support for the temperature/fan/power |
| 880 | sensors on your PowerNV platform. |
| 881 | |
| 882 | This driver can also be built as a module. If so, the module |
| 883 | will be called ibmpowernv. |
| 884 | |
| 885 | config SENSORS_IIO_HWMON |
| 886 | tristate "Hwmon driver that uses channels specified via iio maps" |
| 887 | depends on IIO |
| 888 | help |
| 889 | This is a platform driver that in combination with a suitable |
| 890 | map allows IIO devices to provide basic hwmon functionality |
| 891 | for those channels specified in the map. This map can be provided |
| 892 | either via platform data or the device tree bindings. |
| 893 | |
| 894 | config SENSORS_I5500 |
| 895 | tristate "Intel 5500/5520/X58 temperature sensor" |
| 896 | depends on X86 && PCI |
| 897 | help |
| 898 | If you say yes here you get support for the temperature |
| 899 | sensor inside the Intel 5500, 5520 and X58 chipsets. |
| 900 | |
| 901 | This driver can also be built as a module. If so, the module |
| 902 | will be called i5500_temp. |
| 903 | |
| 904 | config SENSORS_CORETEMP |
| 905 | tristate "Intel Core/Core2/Atom temperature sensor" |
| 906 | depends on X86 |
| 907 | help |
| 908 | If you say yes here you get support for the temperature |
| 909 | sensor inside your CPU. Most of the family 6 CPUs |
| 910 | are supported. Check Documentation/hwmon/coretemp.rst for details. |
| 911 | |
| 912 | config SENSORS_ISL28022 |
| 913 | tristate "Renesas ISL28022" |
| 914 | depends on I2C |
| 915 | select REGMAP_I2C |
| 916 | help |
| 917 | If you say yes here you get support for ISL28022 power monitor. |
| 918 | Check Documentation/hwmon/isl28022.rst for details. |
| 919 | |
| 920 | This driver can also be built as a module. If so, the module |
| 921 | will be called isl28022. |
| 922 | |
| 923 | config SENSORS_IT87 |
| 924 | tristate "ITE IT87xx and compatibles" |
| 925 | depends on HAS_IOPORT |
| 926 | depends on !PPC |
| 927 | select HWMON_VID |
| 928 | help |
| 929 | If you say yes here you get support for ITE IT8705F, IT8712F, IT8716F, |
| 930 | IT8718F, IT8720F, IT8721F, IT8726F, IT8728F, IT8732F, IT8758E, |
| 931 | IT8771E, IT8772E, IT8781F, IT8782F, IT8783E/F, IT8786E, IT8790E, |
| 932 | IT8603E, IT8620E, IT8623E, IT8628E, and IT8689E sensor chips, and |
| 933 | the SiS950 clone. |
| 934 | |
| 935 | This driver can also be built as a module. If so, the module |
| 936 | will be called it87. |
| 937 | |
| 938 | config SENSORS_JC42 |
| 939 | tristate "JEDEC JC42.4 compliant memory module temperature sensors" |
| 940 | depends on I2C |
| 941 | select REGMAP_I2C |
| 942 | help |
| 943 | If you say yes here, you get support for JEDEC JC42.4 compliant |
| 944 | temperature sensors, which are used on many DDR3 memory modules for |
| 945 | mobile devices and servers. Support will include, but not be limited |
| 946 | to, ADT7408, AT30TS00, CAT34TS02, CAT6095, MAX6604, MCP9804, MCP9805, |
| 947 | MCP9808, MCP98242, MCP98243, MCP98244, MCP9843, SE97, SE98, |
| 948 | STTS424(E), STTS2002, STTS3000, TSE2002, TSE2004, TS3000, and TS3001. |
| 949 | |
| 950 | This driver can also be built as a module. If so, the module |
| 951 | will be called jc42. |
| 952 | |
| 953 | config SENSORS_POLARFIRE_SOC_TVS |
| 954 | tristate "PolarFire SoC (MPFS) temperature and voltage sensor" |
| 955 | depends on POLARFIRE_SOC_SYSCONS || COMPILE_TEST |
| 956 | depends on MFD_SYSCON |
| 957 | help |
| 958 | This driver adds support for the PolarFire SoC (MPFS) Temperature and |
| 959 | Voltage Sensor. |
| 960 | |
| 961 | To compile this driver as a module, choose M here. the |
| 962 | module will be called tvs-mpfs. |
| 963 | |
| 964 | If unsure, say N. |
| 965 | |
| 966 | config SENSORS_POWERZ |
| 967 | tristate "ChargerLAB POWER-Z USB-C tester" |
| 968 | depends on USB |
| 969 | help |
| 970 | If you say yes here you get support for ChargerLAB POWER-Z series of |
| 971 | USB-C charging testers. |
| 972 | |
| 973 | This driver can also be built as a module. If so, the module |
| 974 | will be called powerz. |
| 975 | |
| 976 | config SENSORS_POWR1220 |
| 977 | tristate "Lattice POWR1220 Power Monitoring" |
| 978 | depends on I2C |
| 979 | help |
| 980 | If you say yes here you get access to the hardware monitoring |
| 981 | functions of the Lattice POWR1220 isp Power Supply Monitoring, |
| 982 | Sequencing and Margining Controller. |
| 983 | |
| 984 | This driver can also be built as a module. If so, the module |
| 985 | will be called powr1220. |
| 986 | |
| 987 | config SENSORS_PROM21_XHCI |
| 988 | tristate "AMD Promontory 21 xHCI temperature sensor" |
| 989 | depends on USB_XHCI_PCI |
| 990 | help |
| 991 | If you say yes here you get support for the AMD Promontory 21 |
| 992 | (PROM21) xHCI temperature sensor. |
| 993 | |
| 994 | This driver can also be built as a module. If so, the module |
| 995 | will be called prom21-xhci. |
| 996 | |
| 997 | config SENSORS_LAN966X |
| 998 | tristate "Microchip LAN966x Hardware Monitoring" |
| 999 | depends on SOC_LAN966 || COMPILE_TEST |
| 1000 | select REGMAP |
| 1001 | select POLYNOMIAL |
| 1002 | help |
| 1003 | If you say yes here you get support for temperature monitoring |
| 1004 | on the Microchip LAN966x SoC. |
| 1005 | |
| 1006 | This driver can also be built as a module. If so, the module |
| 1007 | will be called lan966x-hwmon. |
| 1008 | |
| 1009 | config SENSORS_LATTEPANDA_SIGMA_EC |
| 1010 | tristate "LattePanda Sigma EC hardware monitoring" |
| 1011 | depends on X86 |
| 1012 | depends on DMI |
| 1013 | depends on HAS_IOPORT |
| 1014 | help |
| 1015 | If you say yes here you get support for the hardware monitoring |
| 1016 | features of the Embedded Controller on LattePanda Sigma |
| 1017 | single-board computers, including CPU fan speed (RPM) and |
| 1018 | board and CPU temperatures. |
| 1019 | |
| 1020 | The driver reads the EC directly via ACPI EC I/O ports and |
| 1021 | uses DMI matching to ensure it only loads on supported hardware. |
| 1022 | |
| 1023 | This driver can also be built as a module. If so, the module |
| 1024 | will be called lattepanda-sigma-ec. |
| 1025 | |
| 1026 | config SENSORS_LENOVO_EC |
| 1027 | tristate "Sensor reader for Lenovo ThinkStations" |
| 1028 | depends on X86 |
| 1029 | help |
| 1030 | If you say yes here you get support for LENOVO |
| 1031 | EC Sensor data on newer ThinkStation systems |
| 1032 | |
| 1033 | This driver can also be built as a module. If so, the module |
| 1034 | will be called lenovo_ec_sensors. |
| 1035 | |
| 1036 | config SENSORS_LINEAGE |
| 1037 | tristate "Lineage Compact Power Line Power Entry Module" |
| 1038 | depends on I2C |
| 1039 | help |
| 1040 | If you say yes here you get support for the Lineage Compact Power Line |
| 1041 | series of DC/DC and AC/DC converters such as CP1800, CP2000AC, |
| 1042 | CP2000DC, CP2725, and others. |
| 1043 | |
| 1044 | This driver can also be built as a module. If so, the module |
| 1045 | will be called lineage-pem. |
| 1046 | |
| 1047 | config SENSORS_LOCHNAGAR |
| 1048 | tristate "Lochnagar Hardware Monitor" |
| 1049 | depends on MFD_LOCHNAGAR |
| 1050 | help |
| 1051 | If you say yes here you get support for Lochnagar 2 temperature, |
| 1052 | voltage and current sensors abilities. |
| 1053 | |
| 1054 | This driver can also be built as a module. If so, the module |
| 1055 | will be called lochnagar-hwmon. |
| 1056 | |
| 1057 | config SENSORS_LTC2945 |
| 1058 | tristate "Linear Technology LTC2945" |
| 1059 | depends on I2C |
| 1060 | select REGMAP_I2C |
| 1061 | help |
| 1062 | If you say yes here you get support for Linear Technology LTC2945 |
| 1063 | I2C System Monitor. |
| 1064 | |
| 1065 | This driver can also be built as a module. If so, the module will |
| 1066 | be called ltc2945. |
| 1067 | |
| 1068 | config SENSORS_LTC2947 |
| 1069 | tristate |
| 1070 | |
| 1071 | config SENSORS_LTC2947_I2C |
| 1072 | tristate "Analog Devices LTC2947 High Precision Power and Energy Monitor over I2C" |
| 1073 | depends on I2C |
| 1074 | select REGMAP_I2C |
| 1075 | select SENSORS_LTC2947 |
| 1076 | help |
| 1077 | If you say yes here you get support for Linear Technology LTC2947 |
| 1078 | I2C High Precision Power and Energy Monitor |
| 1079 | |
| 1080 | This driver can also be built as a module. If so, the module will |
| 1081 | be called ltc2947-i2c. |
| 1082 | |
| 1083 | config SENSORS_LTC2947_SPI |
| 1084 | tristate "Analog Devices LTC2947 High Precision Power and Energy Monitor over SPI" |
| 1085 | depends on SPI_MASTER |
| 1086 | select REGMAP_SPI |
| 1087 | select SENSORS_LTC2947 |
| 1088 | help |
| 1089 | If you say yes here you get support for Linear Technology LTC2947 |
| 1090 | SPI High Precision Power and Energy Monitor |
| 1091 | |
| 1092 | This driver can also be built as a module. If so, the module will |
| 1093 | be called ltc2947-spi. |
| 1094 | |
| 1095 | config SENSORS_LTC2990 |
| 1096 | tristate "Linear Technology LTC2990" |
| 1097 | depends on I2C |
| 1098 | help |
| 1099 | If you say yes here you get support for Linear Technology LTC2990 |
| 1100 | I2C System Monitor. The LTC2990 supports a combination of voltage, |
| 1101 | current and temperature monitoring. |
| 1102 | |
| 1103 | This driver can also be built as a module. If so, the module will |
| 1104 | be called ltc2990. |
| 1105 | |
| 1106 | config SENSORS_LTC2991 |
| 1107 | tristate "Analog Devices LTC2991" |
| 1108 | depends on I2C |
| 1109 | select REGMAP_I2C |
| 1110 | help |
| 1111 | If you say yes here you get support for Analog Devices LTC2991 |
| 1112 | Octal I2C Voltage, Current, and Temperature Monitor. The LTC2991 |
| 1113 | supports a combination of voltage, current and temperature monitoring. |
| 1114 | |
| 1115 | This driver can also be built as a module. If so, the module will |
| 1116 | be called ltc2991. |
| 1117 | |
| 1118 | config SENSORS_LTC2992 |
| 1119 | tristate "Linear Technology LTC2992" |
| 1120 | depends on I2C |
| 1121 | depends on GPIOLIB |
| 1122 | select REGMAP_I2C |
| 1123 | help |
| 1124 | If you say yes here you get support for Linear Technology LTC2992 |
| 1125 | I2C System Monitor. The LTC2992 measures current, voltage, and |
| 1126 | power of two supplies. |
| 1127 | |
| 1128 | This driver can also be built as a module. If so, the module will |
| 1129 | be called ltc2992. |
| 1130 | |
| 1131 | config SENSORS_LTC4151 |
| 1132 | tristate "Linear Technology LTC4151" |
| 1133 | depends on I2C |
| 1134 | help |
| 1135 | If you say yes here you get support for Linear Technology LTC4151 |
| 1136 | High Voltage I2C Current and Voltage Monitor interface. |
| 1137 | |
| 1138 | This driver can also be built as a module. If so, the module will |
| 1139 | be called ltc4151. |
| 1140 | |
| 1141 | config SENSORS_LTC4215 |
| 1142 | tristate "Linear Technology LTC4215" |
| 1143 | depends on I2C |
| 1144 | help |
| 1145 | If you say yes here you get support for Linear Technology LTC4215 |
| 1146 | Hot Swap Controller I2C interface. |
| 1147 | |
| 1148 | This driver can also be built as a module. If so, the module will |
| 1149 | be called ltc4215. |
| 1150 | |
| 1151 | config SENSORS_LTC4222 |
| 1152 | tristate "Linear Technology LTC4222" |
| 1153 | depends on I2C |
| 1154 | select REGMAP_I2C |
| 1155 | help |
| 1156 | If you say yes here you get support for Linear Technology LTC4222 |
| 1157 | Dual Hot Swap Controller I2C interface. |
| 1158 | |
| 1159 | This driver can also be built as a module. If so, the module will |
| 1160 | be called ltc4222. |
| 1161 | |
| 1162 | config SENSORS_LTC4245 |
| 1163 | tristate "Linear Technology LTC4245" |
| 1164 | depends on I2C |
| 1165 | help |
| 1166 | If you say yes here you get support for Linear Technology LTC4245 |
| 1167 | Multiple Supply Hot Swap Controller I2C interface. |
| 1168 | |
| 1169 | This driver can also be built as a module. If so, the module will |
| 1170 | be called ltc4245. |
| 1171 | |
| 1172 | config SENSORS_LTC4260 |
| 1173 | tristate "Linear Technology LTC4260" |
| 1174 | depends on I2C |
| 1175 | select REGMAP_I2C |
| 1176 | help |
| 1177 | If you say yes here you get support for Linear Technology LTC4260 |
| 1178 | Positive Voltage Hot Swap Controller I2C interface. |
| 1179 | |
| 1180 | This driver can also be built as a module. If so, the module will |
| 1181 | be called ltc4260. |
| 1182 | |
| 1183 | config SENSORS_LTC4261 |
| 1184 | tristate "Linear Technology LTC4261" |
| 1185 | depends on I2C |
| 1186 | help |
| 1187 | If you say yes here you get support for Linear Technology LTC4261 |
| 1188 | Negative Voltage Hot Swap Controller I2C interface. |
| 1189 | |
| 1190 | This driver can also be built as a module. If so, the module will |
| 1191 | be called ltc4261. |
| 1192 | |
| 1193 | config SENSORS_LTC4282 |
| 1194 | tristate "Analog Devices LTC4282" |
| 1195 | depends on I2C |
| 1196 | select REGMAP_I2C |
| 1197 | help |
| 1198 | If you say yes here you get support for Analog Devices LTC4282 |
| 1199 | High Current Hot Swap Controller I2C interface. |
| 1200 | |
| 1201 | This driver can also be built as a module. If so, the module will |
| 1202 | be called ltc4282. |
| 1203 | |
| 1204 | config SENSORS_LTC4283 |
| 1205 | tristate "Analog Devices LTC4283" |
| 1206 | depends on I2C |
| 1207 | select REGMAP_I2C |
| 1208 | select AUXILIARY_BUS |
| 1209 | help |
| 1210 | If you say yes here you get support for Analog Devices LTC4283 |
| 1211 | Negative Voltage Hot Swap Controller I2C interface. |
| 1212 | |
| 1213 | This driver can also be built as a module. If so, the module will |
| 1214 | be called ltc4283. |
| 1215 | |
| 1216 | config SENSORS_LTQ_CPUTEMP |
| 1217 | bool "Lantiq cpu temperature sensor driver" |
| 1218 | depends on SOC_XWAY |
| 1219 | help |
| 1220 | If you say yes here you get support for the temperature |
| 1221 | sensor inside your CPU. |
| 1222 | |
| 1223 | config SENSORS_MACSMC_HWMON |
| 1224 | tristate "Apple SMC (Apple Silicon)" |
| 1225 | depends on MFD_MACSMC && OF |
| 1226 | help |
| 1227 | This driver enables hwmon support for current, power, temperature, |
| 1228 | and voltage sensors, as well as fan speed reporting and control |
| 1229 | on Apple Silicon devices. Say Y here if you have an Apple Silicon |
| 1230 | device. |
| 1231 | |
| 1232 | This driver can also be built as a module. If so, the module will |
| 1233 | be called macsmc-hwmon. |
| 1234 | |
| 1235 | config SENSORS_MAX1111 |
| 1236 | tristate "Maxim MAX1111 Serial 8-bit ADC chip and compatibles" |
| 1237 | depends on SPI_MASTER |
| 1238 | help |
| 1239 | Say y here to support Maxim's MAX1110, MAX1111, MAX1112, and MAX1113 |
| 1240 | ADC chips. |
| 1241 | |
| 1242 | This driver can also be built as a module. If so, the module |
| 1243 | will be called max1111. |
| 1244 | |
| 1245 | config SENSORS_MAX127 |
| 1246 | tristate "Maxim MAX127 12-bit 8-channel Data Acquisition System" |
| 1247 | depends on I2C |
| 1248 | help |
| 1249 | Say y here to support Maxim's MAX127 DAS chips. |
| 1250 | |
| 1251 | This driver can also be built as a module. If so, the module |
| 1252 | will be called max127. |
| 1253 | |
| 1254 | config SENSORS_MAX16065 |
| 1255 | tristate "Maxim MAX16065 System Manager and compatibles" |
| 1256 | depends on I2C |
| 1257 | help |
| 1258 | If you say yes here you get support for hardware monitoring |
| 1259 | capabilities of the following Maxim System Manager chips. |
| 1260 | MAX16065 |
| 1261 | MAX16066 |
| 1262 | MAX16067 |
| 1263 | MAX16068 |
| 1264 | MAX16070 |
| 1265 | MAX16071 |
| 1266 | |
| 1267 | This driver can also be built as a module. If so, the module |
| 1268 | will be called max16065. |
| 1269 | |
| 1270 | config SENSORS_MAX1619 |
| 1271 | tristate "Maxim MAX1619 sensor chip" |
| 1272 | depends on I2C |
| 1273 | select REGMAP |
| 1274 | help |
| 1275 | If you say yes here you get support for MAX1619 sensor chip. |
| 1276 | |
| 1277 | This driver can also be built as a module. If so, the module |
| 1278 | will be called max1619. |
| 1279 | |
| 1280 | config SENSORS_MAX1668 |
| 1281 | tristate "Maxim MAX1668 and compatibles" |
| 1282 | depends on I2C |
| 1283 | select REGMAP_I2C |
| 1284 | help |
| 1285 | If you say yes here you get support for MAX1668, MAX1989 and |
| 1286 | MAX1805 chips. |
| 1287 | |
| 1288 | This driver can also be built as a module. If so, the module |
| 1289 | will be called max1668. |
| 1290 | |
| 1291 | config SENSORS_MAX197 |
| 1292 | tristate "Maxim MAX197 and compatibles" |
| 1293 | help |
| 1294 | Support for the Maxim MAX197 A/D converter. |
| 1295 | Support will include, but not be limited to, MAX197, and MAX199. |
| 1296 | |
| 1297 | This driver can also be built as a module. If so, the module |
| 1298 | will be called max197. |
| 1299 | |
| 1300 | config SENSORS_MAX31722 |
| 1301 | tristate "MAX31722 temperature sensor" |
| 1302 | depends on SPI |
| 1303 | help |
| 1304 | Support for the Maxim Integrated MAX31722/MAX31723 digital |
| 1305 | thermometers/thermostats operating over an SPI interface. |
| 1306 | |
| 1307 | This driver can also be built as a module. If so, the module |
| 1308 | will be called max31722. |
| 1309 | |
| 1310 | config SENSORS_MAX31730 |
| 1311 | tristate "MAX31730 temperature sensor" |
| 1312 | depends on I2C |
| 1313 | help |
| 1314 | Support for the Maxim Integrated MAX31730 3-Channel Remote |
| 1315 | Temperature Sensor. |
| 1316 | |
| 1317 | This driver can also be built as a module. If so, the module |
| 1318 | will be called max31730. |
| 1319 | |
| 1320 | config SENSORS_MAX31760 |
| 1321 | tristate "MAX31760 fan speed controller" |
| 1322 | depends on I2C |
| 1323 | select REGMAP_I2C |
| 1324 | help |
| 1325 | Support for the Analog Devices MAX31760 Precision Fan-Speed |
| 1326 | Controller. MAX31760 integrates temperature sensing along with |
| 1327 | precision PWM fan control. |
| 1328 | |
| 1329 | This driver can also be built as a module. If so, the module |
| 1330 | will be called max31760. |
| 1331 | |
| 1332 | config MAX31827 |
| 1333 | tristate "MAX31827 low-power temperature switch and similar devices" |
| 1334 | depends on I2C |
| 1335 | select REGMAP_I2C |
| 1336 | help |
| 1337 | If you say yes here you get support for MAX31827, MAX31828 and |
| 1338 | MAX31829 low-power temperature switches and sensors connected with I2C. |
| 1339 | |
| 1340 | This driver can also be built as a module. If so, the module |
| 1341 | will be called max31827. |
| 1342 | |
| 1343 | config SENSORS_MAX6620 |
| 1344 | tristate "Maxim MAX6620 fan controller" |
| 1345 | depends on I2C |
| 1346 | help |
| 1347 | If you say yes here you get support for the MAX6620 |
| 1348 | fan controller. |
| 1349 | |
| 1350 | This driver can also be built as a module. If so, the module |
| 1351 | will be called max6620. |
| 1352 | |
| 1353 | config SENSORS_MAX6621 |
| 1354 | tristate "Maxim MAX6621 sensor chip" |
| 1355 | depends on I2C |
| 1356 | select REGMAP_I2C |
| 1357 | help |
| 1358 | If you say yes here you get support for MAX6621 sensor chip. |
| 1359 | MAX6621 is a PECI-to-I2C translator provides an efficient, |
| 1360 | low-cost solution for PECI-to-SMBus/I2C protocol conversion. |
| 1361 | It allows reading the temperature from the PECI-compliant |
| 1362 | host directly from up to four PECI-enabled CPUs. |
| 1363 | |
| 1364 | This driver can also be built as a module. If so, the module |
| 1365 | will be called max6621. |
| 1366 | |
| 1367 | config SENSORS_MAX6639 |
| 1368 | tristate "Maxim MAX6639 sensor chip" |
| 1369 | depends on I2C |
| 1370 | select REGMAP_I2C |
| 1371 | help |
| 1372 | If you say yes here you get support for the MAX6639 |
| 1373 | sensor chips. |
| 1374 | |
| 1375 | This driver can also be built as a module. If so, the module |
| 1376 | will be called max6639. |
| 1377 | |
| 1378 | config SENSORS_MAX6650 |
| 1379 | tristate "Maxim MAX6650 sensor chip" |
| 1380 | depends on I2C |
| 1381 | help |
| 1382 | If you say yes here you get support for the MAX6650 / MAX6651 |
| 1383 | sensor chips. |
| 1384 | |
| 1385 | This driver can also be built as a module. If so, the module |
| 1386 | will be called max6650. |
| 1387 | |
| 1388 | config SENSORS_MAX6697 |
| 1389 | tristate "Maxim MAX6697 and compatibles" |
| 1390 | depends on I2C |
| 1391 | select REGMAP_I2C |
| 1392 | help |
| 1393 | If you say yes here you get support for MAX6581, MAX6602, MAX6622, |
| 1394 | MAX6636, MAX6689, MAX6693, MAX6694, MAX6697, MAX6698, and MAX6699 |
| 1395 | temperature sensor chips. |
| 1396 | |
| 1397 | This driver can also be built as a module. If so, the module |
| 1398 | will be called max6697. |
| 1399 | |
| 1400 | config SENSORS_MAX31790 |
| 1401 | tristate "Maxim MAX31790 sensor chip" |
| 1402 | depends on I2C |
| 1403 | help |
| 1404 | If you say yes here you get support for 6-Channel PWM-Output |
| 1405 | Fan RPM Controller. |
| 1406 | |
| 1407 | This driver can also be built as a module. If so, the module |
| 1408 | will be called max31790. |
| 1409 | |
| 1410 | config SENSORS_MAX77705 |
| 1411 | tristate "MAX77705 current and voltage sensor" |
| 1412 | depends on MFD_MAX77705 |
| 1413 | help |
| 1414 | If you say yes here you get support for MAX77705 sensors connected with I2C. |
| 1415 | |
| 1416 | This driver can also be built as a module. If so, the module |
| 1417 | will be called max77705-hwmon. |
| 1418 | |
| 1419 | config SENSORS_MC34VR500 |
| 1420 | tristate "NXP MC34VR500 hardware monitoring driver" |
| 1421 | depends on I2C |
| 1422 | select REGMAP_I2C |
| 1423 | help |
| 1424 | If you say yes here you get support for the temperature and input |
| 1425 | voltage sensors of the NXP MC34VR500. |
| 1426 | |
| 1427 | config SENSORS_MCP3021 |
| 1428 | tristate "Microchip MCP3021 and compatibles" |
| 1429 | depends on I2C |
| 1430 | help |
| 1431 | If you say yes here you get support for MCP3021 and MCP3221. |
| 1432 | The MCP3021 is a A/D converter (ADC) with 10-bit and the MCP3221 |
| 1433 | with 12-bit resolution. |
| 1434 | |
| 1435 | This driver can also be built as a module. If so, the module |
| 1436 | will be called mcp3021. |
| 1437 | |
| 1438 | config SENSORS_MCP9982 |
| 1439 | tristate "Microchip Technology MCP9982 driver" |
| 1440 | depends on I2C |
| 1441 | select REGMAP_I2C |
| 1442 | help |
| 1443 | Say yes here to include support for Microchip Technology's MCP998X/33 |
| 1444 | and MCP998XD/33D Multichannel Automotive Temperature Monitor Family. |
| 1445 | |
| 1446 | This driver can also be built as a module. If so, the module |
| 1447 | will be called mcp9982. |
| 1448 | |
| 1449 | config SENSORS_MLXREG_FAN |
| 1450 | tristate "Mellanox FAN driver" |
| 1451 | depends on MELLANOX_PLATFORM |
| 1452 | imply THERMAL |
| 1453 | select REGMAP |
| 1454 | help |
| 1455 | This option enables support for the FAN control on the Mellanox |
| 1456 | Ethernet and InfiniBand switches. The driver can be activated by the |
| 1457 | platform device add call. Say Y to enable these. To compile this |
| 1458 | driver as a module, choose 'M' here: the module will be called |
| 1459 | mlxreg-fan. |
| 1460 | |
| 1461 | config SENSORS_TC654 |
| 1462 | tristate "Microchip TC654/TC655 and compatibles" |
| 1463 | depends on I2C |
| 1464 | help |
| 1465 | If you say yes here you get support for TC654 and TC655. |
| 1466 | The TC654 and TC655 are PWM mode fan speed controllers with |
| 1467 | FanSense technology for use with brushless DC fans. |
| 1468 | |
| 1469 | This driver can also be built as a module. If so, the module |
| 1470 | will be called tc654. |
| 1471 | |
| 1472 | config SENSORS_TPS23861 |
| 1473 | tristate "Texas Instruments TPS23861 PoE PSE" |
| 1474 | depends on I2C |
| 1475 | select REGMAP_I2C |
| 1476 | help |
| 1477 | If you say yes here you get support for Texas Instruments |
| 1478 | TPS23861 802.3at PoE PSE chips. |
| 1479 | |
| 1480 | This driver can also be built as a module. If so, the module |
| 1481 | will be called tps23861. |
| 1482 | |
| 1483 | config SENSORS_MENF21BMC_HWMON |
| 1484 | tristate "MEN 14F021P00 BMC Hardware Monitoring" |
| 1485 | depends on MFD_MENF21BMC |
| 1486 | help |
| 1487 | Say Y here to include support for the MEN 14F021P00 BMC |
| 1488 | hardware monitoring. |
| 1489 | |
| 1490 | This driver can also be built as a module. If so the module |
| 1491 | will be called menf21bmc_hwmon. |
| 1492 | |
| 1493 | config SENSORS_MR75203 |
| 1494 | tristate "Moortec Semiconductor MR75203 PVT Controller" |
| 1495 | select REGMAP_MMIO |
| 1496 | help |
| 1497 | If you say yes here you get support for Moortec MR75203 |
| 1498 | PVT controller. |
| 1499 | |
| 1500 | This driver can also be built as a module. If so, the module |
| 1501 | will be called mr75203. |
| 1502 | |
| 1503 | config SENSORS_ADCXX |
| 1504 | tristate "National Semiconductor ADCxxxSxxx" |
| 1505 | depends on SPI_MASTER |
| 1506 | help |
| 1507 | If you say yes here you get support for the National Semiconductor |
| 1508 | ADC<bb><c>S<sss> chip family, where |
| 1509 | * bb is the resolution in number of bits (8, 10, 12) |
| 1510 | * c is the number of channels (1, 2, 4, 8) |
| 1511 | * sss is the maximum conversion speed (021 for 200 kSPS, 051 for 500 |
| 1512 | kSPS and 101 for 1 MSPS) |
| 1513 | |
| 1514 | Examples : ADC081S101, ADC124S501, ... |
| 1515 | |
| 1516 | This driver can also be built as a module. If so, the module |
| 1517 | will be called adcxx. |
| 1518 | |
| 1519 | config SENSORS_LM63 |
| 1520 | tristate "National Semiconductor LM63 and compatibles" |
| 1521 | depends on I2C |
| 1522 | help |
| 1523 | If you say yes here you get support for the National |
| 1524 | Semiconductor LM63, LM64, and LM96163 remote diode digital temperature |
| 1525 | sensors with integrated fan control. Such chips are found |
| 1526 | on the Tyan S4882 (Thunder K8QS Pro) motherboard, among |
| 1527 | others. |
| 1528 | |
| 1529 | This driver can also be built as a module. If so, the module |
| 1530 | will be called lm63. |
| 1531 | |
| 1532 | config SENSORS_LM70 |
| 1533 | tristate "National Semiconductor LM70 and compatibles" |
| 1534 | depends on SPI_MASTER |
| 1535 | help |
| 1536 | If you say yes here you get support for the National Semiconductor |
| 1537 | LM70, LM71, LM74 and Texas Instruments TMP121/TMP123, TMP122/TMP124, |
| 1538 | TMP125 digital temperature sensor chips. |
| 1539 | |
| 1540 | This driver can also be built as a module. If so, the module |
| 1541 | will be called lm70. |
| 1542 | |
| 1543 | config SENSORS_LM73 |
| 1544 | tristate "National Semiconductor LM73" |
| 1545 | depends on I2C |
| 1546 | help |
| 1547 | If you say yes here you get support for National Semiconductor LM73 |
| 1548 | sensor chips. |
| 1549 | This driver can also be built as a module. If so, the module |
| 1550 | will be called lm73. |
| 1551 | |
| 1552 | config SENSORS_LM75 |
| 1553 | tristate "National Semiconductor LM75 and compatibles" |
| 1554 | depends on I3C_OR_I2C |
| 1555 | select REGMAP_I2C |
| 1556 | select REGMAP_I3C if I3C |
| 1557 | help |
| 1558 | If you say yes here you get support for one common type of |
| 1559 | temperature sensor chip, with models including: |
| 1560 | |
| 1561 | - Analog Devices ADT75 |
| 1562 | - Atmel (now Microchip) AT30TS74 |
| 1563 | - Dallas Semiconductor DS75, DS1775 and DS7505 |
| 1564 | - Global Mixed-mode Technology (GMT) G751 |
| 1565 | - Maxim MAX6625 and MAX6626 |
| 1566 | - Microchip MCP980x |
| 1567 | - National Semiconductor LM75, LM75A |
| 1568 | - NXP's LM75A |
| 1569 | - ST Microelectronics STDS75 |
| 1570 | - ST Microelectronics STLM75 |
| 1571 | - TelCom (now Microchip) TCN75 |
| 1572 | - Texas Instruments TMP100, TMP101, TMP105, TMP112, TMP75, |
| 1573 | TMP175, TMP275 |
| 1574 | |
| 1575 | This driver supports driver model based binding through board |
| 1576 | specific I2C device tables. |
| 1577 | |
| 1578 | It also supports the "legacy" style of driver binding. To use |
| 1579 | that with some chips which don't replicate LM75 quirks exactly, |
| 1580 | you may need the "force" module parameter. |
| 1581 | |
| 1582 | This driver can also be built as a module. If so, the module |
| 1583 | will be called lm75. |
| 1584 | |
| 1585 | config SENSORS_LM77 |
| 1586 | tristate "National Semiconductor LM77" |
| 1587 | depends on I2C |
| 1588 | help |
| 1589 | If you say yes here you get support for National Semiconductor LM77 |
| 1590 | sensor chips. |
| 1591 | |
| 1592 | This driver can also be built as a module. If so, the module |
| 1593 | will be called lm77. |
| 1594 | |
| 1595 | config SENSORS_LM78 |
| 1596 | tristate "National Semiconductor LM78 and compatibles" |
| 1597 | depends on I2C |
| 1598 | select HWMON_VID |
| 1599 | help |
| 1600 | If you say yes here you get support for National Semiconductor LM78, |
| 1601 | LM78-J and LM79. |
| 1602 | |
| 1603 | This driver can also be built as a module. If so, the module |
| 1604 | will be called lm78. |
| 1605 | |
| 1606 | config SENSORS_LM80 |
| 1607 | tristate "National Semiconductor LM80 and LM96080" |
| 1608 | depends on I2C |
| 1609 | help |
| 1610 | If you say yes here you get support for National Semiconductor |
| 1611 | LM80 and LM96080 sensor chips. |
| 1612 | |
| 1613 | This driver can also be built as a module. If so, the module |
| 1614 | will be called lm80. |
| 1615 | |
| 1616 | config SENSORS_LM83 |
| 1617 | tristate "National Semiconductor LM83 and compatibles" |
| 1618 | depends on I2C |
| 1619 | select REGMAP |
| 1620 | help |
| 1621 | If you say yes here you get support for National Semiconductor |
| 1622 | LM82 and LM83 sensor chips. |
| 1623 | |
| 1624 | This driver can also be built as a module. If so, the module |
| 1625 | will be called lm83. |
| 1626 | |
| 1627 | config SENSORS_LM85 |
| 1628 | tristate "National Semiconductor LM85 and compatibles" |
| 1629 | depends on I2C |
| 1630 | select HWMON_VID |
| 1631 | help |
| 1632 | If you say yes here you get support for National Semiconductor LM85 |
| 1633 | sensor chips and clones: ADM1027, ADT7463, ADT7468, EMC6D100, |
| 1634 | EMC6D101, EMC6D102, and EMC6D103. |
| 1635 | |
| 1636 | This driver can also be built as a module. If so, the module |
| 1637 | will be called lm85. |
| 1638 | |
| 1639 | config SENSORS_LM87 |
| 1640 | tristate "National Semiconductor LM87 and compatibles" |
| 1641 | depends on I2C |
| 1642 | select HWMON_VID |
| 1643 | help |
| 1644 | If you say yes here you get support for National Semiconductor LM87 |
| 1645 | and Analog Devices ADM1024 sensor chips. |
| 1646 | |
| 1647 | This driver can also be built as a module. If so, the module |
| 1648 | will be called lm87. |
| 1649 | |
| 1650 | config SENSORS_LM90 |
| 1651 | tristate "National Semiconductor LM90 and compatibles" |
| 1652 | depends on I2C |
| 1653 | help |
| 1654 | If you say yes here you get support for National Semiconductor LM84, |
| 1655 | LM90, LM86, LM89 and LM99, Analog Devices ADM1020, ADM2021, ADM1021A, |
| 1656 | ADM1023, ADM1032, ADT7461, ADT7461A, ADT7481, ADT7482, and ADT7483A, |
| 1657 | Maxim MAX1617, MAX6642, MAX6646, MAX6647, MAX6648, MAX6649, MAX6654, |
| 1658 | MAX6657, MAX6658, MAX6659, MAX6680, MAX6681, MAX6692, MAX6695, |
| 1659 | MAX6696, |
| 1660 | ON Semiconductor NCT1008, NCT210, NCT72, NCT214, NCT218, |
| 1661 | Winbond/Nuvoton W83L771W/G/AWG/ASG, NCT7716, NCT7717 and NCT7718, |
| 1662 | Philips NE1618, SA56004, GMT G781, Texas Instruments TMP451 and TMP461 |
| 1663 | sensor chips. |
| 1664 | |
| 1665 | This driver can also be built as a module. If so, the module |
| 1666 | will be called lm90. |
| 1667 | |
| 1668 | config SENSORS_LM92 |
| 1669 | tristate "National Semiconductor LM92 and compatibles" |
| 1670 | depends on I2C |
| 1671 | select REGMAP_I2C |
| 1672 | help |
| 1673 | If you say yes here you get support for National Semiconductor LM92 |
| 1674 | and LM76 as well as Maxim MAX6633/6634/6635 sensor chips. |
| 1675 | |
| 1676 | This driver can also be built as a module. If so, the module |
| 1677 | will be called lm92. |
| 1678 | |
| 1679 | config SENSORS_LM93 |
| 1680 | tristate "National Semiconductor LM93 and compatibles" |
| 1681 | depends on I2C |
| 1682 | select HWMON_VID |
| 1683 | help |
| 1684 | If you say yes here you get support for National Semiconductor LM93, |
| 1685 | LM94, and compatible sensor chips. |
| 1686 | |
| 1687 | This driver can also be built as a module. If so, the module |
| 1688 | will be called lm93. |
| 1689 | |
| 1690 | config SENSORS_LM95234 |
| 1691 | tristate "National Semiconductor LM95234 and compatibles" |
| 1692 | depends on I2C |
| 1693 | select REGMAP_I2C |
| 1694 | help |
| 1695 | If you say yes here you get support for the LM95233 and LM95234 |
| 1696 | temperature sensor chips. |
| 1697 | |
| 1698 | This driver can also be built as a module. If so, the module |
| 1699 | will be called lm95234. |
| 1700 | |
| 1701 | config SENSORS_LM95241 |
| 1702 | tristate "National Semiconductor LM95241 and compatibles" |
| 1703 | depends on I2C |
| 1704 | help |
| 1705 | If you say yes here you get support for LM95231 and LM95241 sensor |
| 1706 | chips. |
| 1707 | |
| 1708 | This driver can also be built as a module. If so, the module |
| 1709 | will be called lm95241. |
| 1710 | |
| 1711 | config SENSORS_LM95245 |
| 1712 | tristate "National Semiconductor LM95245 and compatibles" |
| 1713 | depends on I2C |
| 1714 | select REGMAP_I2C |
| 1715 | help |
| 1716 | If you say yes here you get support for LM95235 and LM95245 |
| 1717 | temperature sensor chips. |
| 1718 | |
| 1719 | This driver can also be built as a module. If so, the module |
| 1720 | will be called lm95245. |
| 1721 | |
| 1722 | config SENSORS_PC87360 |
| 1723 | tristate "National Semiconductor PC87360 family" |
| 1724 | depends on HAS_IOPORT |
| 1725 | depends on !PPC |
| 1726 | select HWMON_VID |
| 1727 | help |
| 1728 | If you say yes here you get access to the hardware monitoring |
| 1729 | functions of the National Semiconductor PC8736x Super-I/O chips. |
| 1730 | The PC87360, PC87363 and PC87364 only have fan monitoring and |
| 1731 | control. The PC87365 and PC87366 additionally have voltage and |
| 1732 | temperature monitoring. |
| 1733 | |
| 1734 | This driver can also be built as a module. If so, the module |
| 1735 | will be called pc87360. |
| 1736 | |
| 1737 | config SENSORS_PC87427 |
| 1738 | tristate "National Semiconductor PC87427" |
| 1739 | depends on HAS_IOPORT |
| 1740 | depends on !PPC |
| 1741 | help |
| 1742 | If you say yes here you get access to the hardware monitoring |
| 1743 | functions of the National Semiconductor PC87427 Super-I/O chip. |
| 1744 | The chip has two distinct logical devices, one for fan speed |
| 1745 | monitoring and control, and one for voltage and temperature |
| 1746 | monitoring. Fan speed monitoring and control are supported, as |
| 1747 | well as temperature monitoring. Voltages aren't supported yet. |
| 1748 | |
| 1749 | This driver can also be built as a module. If so, the module |
| 1750 | will be called pc87427. |
| 1751 | |
| 1752 | config SENSORS_NTC_THERMISTOR |
| 1753 | tristate "NTC thermistor support" |
| 1754 | depends on IIO |
| 1755 | help |
| 1756 | This driver supports NTC thermistors sensor reading and its |
| 1757 | interpretation. The driver can also monitor the temperature and |
| 1758 | send notifications about the temperature. |
| 1759 | |
| 1760 | Currently, this driver supports |
| 1761 | NCP15WB473, NCP18WB473, NCP21WB473, NCP03WB473, NCP15WL333, |
| 1762 | NCP03WF104 and NCP15XH103 from Murata and B57330V2103 and |
| 1763 | B57891S0103 from EPCOS. |
| 1764 | |
| 1765 | This driver can also be built as a module. If so, the module |
| 1766 | will be called ntc_thermistor. |
| 1767 | |
| 1768 | config SENSORS_NCT6683 |
| 1769 | tristate "Nuvoton NCT6683D" |
| 1770 | depends on HAS_IOPORT |
| 1771 | depends on !PPC |
| 1772 | help |
| 1773 | If you say yes here you get support for the hardware monitoring |
| 1774 | functionality of the Nuvoton NCT6683D eSIO chip. |
| 1775 | |
| 1776 | This driver can also be built as a module. If so, the module |
| 1777 | will be called nct6683. |
| 1778 | |
| 1779 | config SENSORS_NCT6694 |
| 1780 | tristate "Nuvoton NCT6694 Hardware Monitor support" |
| 1781 | depends on MFD_NCT6694 |
| 1782 | help |
| 1783 | Say Y here to support Nuvoton NCT6694 hardware monitoring |
| 1784 | functionality. |
| 1785 | |
| 1786 | This driver can also be built as a module. If so, the module |
| 1787 | will be called nct6694-hwmon. |
| 1788 | |
| 1789 | config SENSORS_NCT6775_CORE |
| 1790 | tristate |
| 1791 | select REGMAP |
| 1792 | help |
| 1793 | This module contains common code shared by the platform and |
| 1794 | i2c versions of the nct6775 driver; it is not useful on its |
| 1795 | own. |
| 1796 | |
| 1797 | If built as a module, the module will be called |
| 1798 | nct6775-core. |
| 1799 | |
| 1800 | config SENSORS_NCT6775 |
| 1801 | tristate "Platform driver for Nuvoton NCT6775F and compatibles" |
| 1802 | depends on HAS_IOPORT |
| 1803 | depends on !PPC |
| 1804 | depends on ACPI || ACPI=n |
| 1805 | select HWMON_VID |
| 1806 | select SENSORS_NCT6775_CORE |
| 1807 | help |
| 1808 | If you say yes here you get support for the hardware monitoring |
| 1809 | functionality of the Nuvoton NCT6106D, NCT6775F, NCT6776F, NCT6779D, |
| 1810 | NCT6791D, NCT6792D, NCT6793D, NCT6795D, NCT6796D, and compatible |
| 1811 | Super-I/O chips. This driver replaces the w83627ehf driver for |
| 1812 | NCT6775F and NCT6776F. |
| 1813 | |
| 1814 | This driver can also be built as a module. If so, the module |
| 1815 | will be called nct6775. |
| 1816 | |
| 1817 | config SENSORS_NCT6775_I2C |
| 1818 | tristate "I2C driver for Nuvoton NCT6775F and compatibles" |
| 1819 | depends on I2C |
| 1820 | select REGMAP_I2C |
| 1821 | select SENSORS_NCT6775_CORE |
| 1822 | help |
| 1823 | If you say yes here you get support for the hardware monitoring |
| 1824 | functionality of the Nuvoton NCT6106D, NCT6775F, NCT6776F, NCT6779D, |
| 1825 | NCT6791D, NCT6792D, NCT6793D, NCT6795D, NCT6796D, and compatible |
| 1826 | Super-I/O chips via their I2C interface. |
| 1827 | |
| 1828 | If you're not building a kernel for a BMC, this is probably |
| 1829 | not the driver you want (see CONFIG_SENSORS_NCT6775). |
| 1830 | |
| 1831 | This driver can also be built as a module. If so, the module |
| 1832 | will be called nct6775-i2c. |
| 1833 | |
| 1834 | config SENSORS_NCT7363 |
| 1835 | tristate "Nuvoton NCT7363Y" |
| 1836 | depends on I2C |
| 1837 | select REGMAP_I2C |
| 1838 | help |
| 1839 | If you say yes here you get support for the Nuvoton NCT7363Y |
| 1840 | hardware monitoring chip. |
| 1841 | |
| 1842 | This driver can also be built as a module. If so, the module |
| 1843 | will be called nct7363. |
| 1844 | |
| 1845 | config SENSORS_NCT7802 |
| 1846 | tristate "Nuvoton NCT7802Y" |
| 1847 | depends on I2C |
| 1848 | select REGMAP_I2C |
| 1849 | help |
| 1850 | If you say yes here you get support for the Nuvoton NCT7802Y |
| 1851 | hardware monitoring chip. |
| 1852 | |
| 1853 | This driver can also be built as a module. If so, the module |
| 1854 | will be called nct7802. |
| 1855 | |
| 1856 | config SENSORS_NCT7904 |
| 1857 | tristate "Nuvoton NCT7904" |
| 1858 | depends on I2C && WATCHDOG |
| 1859 | select WATCHDOG_CORE |
| 1860 | help |
| 1861 | If you say yes here you get support for the Nuvoton NCT7904 |
| 1862 | hardware monitoring chip, including manual fan speed control |
| 1863 | and support for the integrated watchdog. |
| 1864 | |
| 1865 | This driver can also be built as a module. If so, the module |
| 1866 | will be called nct7904. |
| 1867 | |
| 1868 | config SENSORS_NPCM7XX |
| 1869 | tristate "Nuvoton NPCM750 and compatible PWM and Fan controllers" |
| 1870 | imply THERMAL |
| 1871 | help |
| 1872 | This driver provides support for Nuvoton NPCM750/730/715/705 PWM |
| 1873 | and Fan controllers. |
| 1874 | |
| 1875 | This driver can also be built as a module. If so, the module |
| 1876 | will be called npcm750-pwm-fan. |
| 1877 | |
| 1878 | config SENSORS_NSA320 |
| 1879 | tristate "ZyXEL NSA320 and compatible fan speed and temperature sensors" |
| 1880 | depends on GPIOLIB && OF |
| 1881 | depends on MACH_KIRKWOOD || COMPILE_TEST |
| 1882 | help |
| 1883 | If you say yes here you get support for hardware monitoring |
| 1884 | for the ZyXEL NSA320 Media Server and other compatible devices |
| 1885 | (probably the NSA325 and some NSA310 variants). |
| 1886 | |
| 1887 | The sensor data is taken from a Holtek HT46R065 microcontroller |
| 1888 | connected to GPIO lines. |
| 1889 | |
| 1890 | This driver can also be built as a module. If so, the module |
| 1891 | will be called nsa320-hwmon. |
| 1892 | |
| 1893 | config SENSORS_NZXT_KRAKEN2 |
| 1894 | tristate "NZXT Kraken X42/X51/X62/X72 liquid coolers" |
| 1895 | depends on USB_HID |
| 1896 | help |
| 1897 | If you say yes here you get support for hardware monitoring for the |
| 1898 | NZXT Kraken X42/X52/X62/X72 all-in-one CPU liquid coolers. |
| 1899 | |
| 1900 | This driver can also be built as a module. If so, the module |
| 1901 | will be called nzxt-kraken2. |
| 1902 | |
| 1903 | config SENSORS_NZXT_KRAKEN3 |
| 1904 | tristate "NZXT Kraken X53/X63/X73, Z53/Z63/Z73 coolers" |
| 1905 | depends on USB_HID |
| 1906 | help |
| 1907 | If you say yes here you get support for hardware monitoring for the |
| 1908 | NZXT Kraken X53/X63/X73, Z53/Z63/Z73 all-in-one CPU liquid coolers. |
| 1909 | |
| 1910 | This driver can also be built as a module. If so, the module |
| 1911 | will be called nzxt-kraken3. |
| 1912 | |
| 1913 | config SENSORS_NZXT_SMART2 |
| 1914 | tristate "NZXT RGB & Fan Controller/Smart Device v2" |
| 1915 | depends on USB_HID |
| 1916 | help |
| 1917 | If you say yes here you get support for hardware monitoring for the |
| 1918 | NZXT RGB & Fan Controller/Smart Device v2. |
| 1919 | |
| 1920 | This driver can also be built as a module. If so, the module |
| 1921 | will be called nzxt-smart2. |
| 1922 | |
| 1923 | source "drivers/hwmon/occ/Kconfig" |
| 1924 | |
| 1925 | config SENSORS_PCF8591 |
| 1926 | tristate "Philips PCF8591 ADC/DAC" |
| 1927 | depends on I2C |
| 1928 | help |
| 1929 | If you say yes here you get support for Philips PCF8591 4-channel |
| 1930 | ADC, 1-channel DAC chips. |
| 1931 | |
| 1932 | This driver can also be built as a module. If so, the module |
| 1933 | will be called pcf8591. |
| 1934 | |
| 1935 | These devices are hard to detect and rarely found on mainstream |
| 1936 | hardware. If unsure, say N. |
| 1937 | |
| 1938 | source "drivers/hwmon/peci/Kconfig" |
| 1939 | |
| 1940 | source "drivers/hwmon/pmbus/Kconfig" |
| 1941 | |
| 1942 | config SENSORS_PT5161L |
| 1943 | tristate "Astera Labs PT5161L PCIe retimer hardware monitoring" |
| 1944 | depends on I2C |
| 1945 | help |
| 1946 | If you say yes here you get support for temperature monitoring |
| 1947 | on the Astera Labs PT5161L PCIe retimer. |
| 1948 | |
| 1949 | This driver can also be built as a module. If so, the module |
| 1950 | will be called pt5161l. |
| 1951 | |
| 1952 | config SENSORS_PWM_FAN |
| 1953 | tristate "PWM fan" |
| 1954 | depends on PWM || COMPILE_TEST |
| 1955 | help |
| 1956 | If you say yes here you get support for fans connected to PWM lines. |
| 1957 | The driver uses the generic PWM interface, thus it will work on a |
| 1958 | variety of SoCs. |
| 1959 | |
| 1960 | This driver can also be built as a module. If so, the module |
| 1961 | will be called pwm-fan. |
| 1962 | |
| 1963 | config SENSORS_QNAP_MCU_HWMON |
| 1964 | tristate "QNAP MCU hardware monitoring" |
| 1965 | depends on MFD_QNAP_MCU |
| 1966 | help |
| 1967 | Say yes here to enable support for fan and temperature sensor |
| 1968 | connected to a QNAP MCU, as found in a number of QNAP network |
| 1969 | attached storage devices. |
| 1970 | |
| 1971 | This driver can also be built as a module. If so, the module |
| 1972 | will be called qnap-mcu-hwmon. |
| 1973 | |
| 1974 | config SENSORS_RASPBERRYPI_HWMON |
| 1975 | tristate "Raspberry Pi voltage monitor" |
| 1976 | depends on RASPBERRYPI_FIRMWARE || (COMPILE_TEST && !RASPBERRYPI_FIRMWARE) |
| 1977 | help |
| 1978 | If you say yes here you get support for voltage sensor on the |
| 1979 | Raspberry Pi. |
| 1980 | |
| 1981 | This driver can also be built as a module. If so, the module |
| 1982 | will be called raspberrypi-hwmon. |
| 1983 | |
| 1984 | config SENSORS_SL28CPLD |
| 1985 | tristate "Kontron sl28cpld hardware monitoring driver" |
| 1986 | depends on MFD_SL28CPLD || COMPILE_TEST |
| 1987 | help |
| 1988 | If you say yes here you get support for the fan supervisor of the |
| 1989 | sl28cpld board management controller. |
| 1990 | |
| 1991 | This driver can also be built as a module. If so, the module |
| 1992 | will be called sl28cpld-hwmon. |
| 1993 | |
| 1994 | config SENSORS_SBTSI |
| 1995 | tristate "Emulated SB-TSI temperature sensor" |
| 1996 | depends on AMD_SBTSI |
| 1997 | help |
| 1998 | If you say yes here you get support for emulated temperature |
| 1999 | sensors on AMD SoCs with SB-TSI interface connected to a BMC device. |
| 2000 | |
| 2001 | This driver can also be built as a module. If so, the module will |
| 2002 | be called sbtsi_temp. |
| 2003 | |
| 2004 | config SENSORS_SHT15 |
| 2005 | tristate "Sensiron humidity and temperature sensors. SHT15 and compat." |
| 2006 | depends on GPIOLIB || COMPILE_TEST |
| 2007 | select BITREVERSE |
| 2008 | help |
| 2009 | If you say yes here you get support for the Sensiron SHT10, SHT11, |
| 2010 | SHT15, SHT71, SHT75 humidity and temperature sensors. |
| 2011 | |
| 2012 | This driver can also be built as a module. If so, the module |
| 2013 | will be called sht15. |
| 2014 | |
| 2015 | config SENSORS_SHT21 |
| 2016 | tristate "Sensiron humidity and temperature sensors. SHT21 and compat." |
| 2017 | depends on I2C |
| 2018 | help |
| 2019 | If you say yes here you get support for the Sensiron SHT20, SHT21, |
| 2020 | SHT25 humidity and temperature sensors. |
| 2021 | |
| 2022 | This driver can also be built as a module. If so, the module |
| 2023 | will be called sht21. |
| 2024 | |
| 2025 | config SENSORS_SHT3x |
| 2026 | tristate "Sensiron humidity and temperature sensors. SHT3x and compat." |
| 2027 | depends on I2C |
| 2028 | select CRC8 |
| 2029 | help |
| 2030 | If you say yes here you get support for the Sensiron SHT30, SHT31, |
| 2031 | SHT85 and the compatible GXCAS GXHT30 humidity and temperature |
| 2032 | sensors. |
| 2033 | |
| 2034 | This driver can also be built as a module. If so, the module |
| 2035 | will be called sht3x. |
| 2036 | |
| 2037 | config SENSORS_SHT4x |
| 2038 | tristate "Sensiron humidity and temperature sensors. SHT4x and compat." |
| 2039 | depends on I2C |
| 2040 | select CRC8 |
| 2041 | help |
| 2042 | If you say yes here you get support for the Sensiron SHT40, SHT41 and |
| 2043 | SHT45 humidity and temperature sensors. |
| 2044 | |
| 2045 | This driver can also be built as a module. If so, the module |
| 2046 | will be called sht4x. |
| 2047 | |
| 2048 | config SENSORS_SHTC1 |
| 2049 | tristate "Sensiron humidity and temperature sensors. SHTC1 and compat." |
| 2050 | depends on I2C |
| 2051 | help |
| 2052 | If you say yes here you get support for the Sensiron SHTC1, SHTW1, |
| 2053 | and SHTC3 humidity and temperature sensors. |
| 2054 | |
| 2055 | This driver can also be built as a module. If so, the module |
| 2056 | will be called shtc1. |
| 2057 | |
| 2058 | config SENSORS_SIS5595 |
| 2059 | tristate "Silicon Integrated Systems Corp. SiS5595" |
| 2060 | depends on PCI && HAS_IOPORT |
| 2061 | help |
| 2062 | If you say yes here you get support for the integrated sensors in |
| 2063 | SiS5595 South Bridges. |
| 2064 | |
| 2065 | This driver can also be built as a module. If so, the module |
| 2066 | will be called sis5595. |
| 2067 | |
| 2068 | config SENSORS_SY7636A |
| 2069 | tristate "Silergy SY7636A" |
| 2070 | depends on MFD_SY7636A |
| 2071 | help |
| 2072 | If you say yes here you get support for the thermistor readout of |
| 2073 | the Silergy SY7636A PMIC. |
| 2074 | |
| 2075 | This driver can also be built as a module. If so, the module |
| 2076 | will be called sy7636a-hwmon. |
| 2077 | |
| 2078 | config SENSORS_DME1737 |
| 2079 | tristate "SMSC DME1737, SCH311x and compatibles" |
| 2080 | depends on HAS_IOPORT |
| 2081 | depends on I2C && !PPC |
| 2082 | select HWMON_VID |
| 2083 | help |
| 2084 | If you say yes here you get support for the hardware monitoring |
| 2085 | and fan control features of the SMSC DME1737, SCH311x, SCH5027, and |
| 2086 | Asus A8000 Super-I/O chips. |
| 2087 | |
| 2088 | This driver can also be built as a module. If so, the module |
| 2089 | will be called dme1737. |
| 2090 | |
| 2091 | config SENSORS_EIC7700_PVT |
| 2092 | tristate "Eswin EIC7700 Voltage, Temperature sensor driver" |
| 2093 | depends on ARCH_ESWIN || COMPILE_TEST |
| 2094 | select POLYNOMIAL |
| 2095 | help |
| 2096 | If you say yes here you get support for Eswin EIC7700 PVT sensor |
| 2097 | embedded into the SoC. |
| 2098 | |
| 2099 | This driver can also be built as a module. If so, the module will be |
| 2100 | called eic7700-pvt. |
| 2101 | |
| 2102 | config SENSORS_EMC1403 |
| 2103 | tristate "SMSC EMC1403/23 thermal sensor" |
| 2104 | depends on I2C |
| 2105 | select REGMAP_I2C |
| 2106 | help |
| 2107 | If you say yes here you get support for the SMSC EMC1403/23 |
| 2108 | temperature monitoring chip. |
| 2109 | |
| 2110 | Threshold values can be configured using sysfs. |
| 2111 | Data from the different diodes are accessible via sysfs. |
| 2112 | |
| 2113 | config SENSORS_EMC1812 |
| 2114 | tristate "Microchip Technology EMC1812 driver" |
| 2115 | depends on I2C |
| 2116 | select REGMAP_I2C |
| 2117 | help |
| 2118 | If you say yes here to build support for Microchip Technology's |
| 2119 | EMC181X/33 Multichannel Low-Voltage Remote Diode Sensor Family. |
| 2120 | |
| 2121 | This driver can also be built as a module. If so, the module |
| 2122 | will be called emc1812. |
| 2123 | |
| 2124 | config SENSORS_EMC2103 |
| 2125 | tristate "SMSC EMC2103" |
| 2126 | depends on I2C |
| 2127 | help |
| 2128 | If you say yes here you get support for the temperature |
| 2129 | and fan sensors of the SMSC EMC2103 chips. |
| 2130 | |
| 2131 | This driver can also be built as a module. If so, the module |
| 2132 | will be called emc2103. |
| 2133 | |
| 2134 | config SENSORS_EMC2305 |
| 2135 | tristate "Microchip EMC2305 and compatible EMC2301/2/3" |
| 2136 | depends on I2C |
| 2137 | imply THERMAL |
| 2138 | help |
| 2139 | If you say yes here you get support for the Microchip EMC2305 |
| 2140 | fan controller chips. |
| 2141 | The Microchip EMC2305 is a fan controller for up to 5 fans. |
| 2142 | Fan rotation speeds are reported in RPM. |
| 2143 | |
| 2144 | This driver can also be built as a module. If so, the module |
| 2145 | will be called emc2305. |
| 2146 | |
| 2147 | config SENSORS_EMC6W201 |
| 2148 | tristate "SMSC EMC6W201" |
| 2149 | depends on I2C |
| 2150 | help |
| 2151 | If you say yes here you get support for the SMSC EMC6W201 |
| 2152 | hardware monitoring chip. |
| 2153 | |
| 2154 | This driver can also be built as a module. If so, the module |
| 2155 | will be called emc6w201. |
| 2156 | |
| 2157 | config SENSORS_SMSC47M1 |
| 2158 | tristate "SMSC LPC47M10x and compatibles" |
| 2159 | depends on HAS_IOPORT |
| 2160 | depends on !PPC |
| 2161 | help |
| 2162 | If you say yes here you get support for the integrated fan |
| 2163 | monitoring and control capabilities of the SMSC LPC47B27x, |
| 2164 | LPC47M10x, LPC47M112, LPC47M13x, LPC47M14x, LPC47M15x, |
| 2165 | LPC47M192, LPC47M292 and LPC47M997 chips. |
| 2166 | |
| 2167 | The temperature and voltage sensor features of the LPC47M15x, |
| 2168 | LPC47M192, LPC47M292 and LPC47M997 are supported by another |
| 2169 | driver, select also "SMSC LPC47M192 and compatibles" below for |
| 2170 | those. |
| 2171 | |
| 2172 | This driver can also be built as a module. If so, the module |
| 2173 | will be called smsc47m1. |
| 2174 | |
| 2175 | config SENSORS_SMSC47M192 |
| 2176 | tristate "SMSC LPC47M192 and compatibles" |
| 2177 | depends on I2C |
| 2178 | select HWMON_VID |
| 2179 | help |
| 2180 | If you say yes here you get support for the temperature and |
| 2181 | voltage sensors of the SMSC LPC47M192, LPC47M15x, LPC47M292 |
| 2182 | and LPC47M997 chips. |
| 2183 | |
| 2184 | The fan monitoring and control capabilities of these chips |
| 2185 | are supported by another driver, select |
| 2186 | "SMSC LPC47M10x and compatibles" above. You need both drivers |
| 2187 | if you want fan control and voltage/temperature sensor support. |
| 2188 | |
| 2189 | This driver can also be built as a module. If so, the module |
| 2190 | will be called smsc47m192. |
| 2191 | |
| 2192 | config SENSORS_ALTERA_SOCFPGA_HWMON |
| 2193 | tristate "Altera SoC FPGA hardware monitoring features" |
| 2194 | depends on INTEL_STRATIX10_SERVICE |
| 2195 | help |
| 2196 | If you say yes here you get support for the temperature and |
| 2197 | voltage sensors of Altera SoC FPGA devices. |
| 2198 | |
| 2199 | This driver can also be built as a module. If so, the module |
| 2200 | will be called socfpga-hwmon. |
| 2201 | |
| 2202 | config SENSORS_SMSC47B397 |
| 2203 | tristate "SMSC LPC47B397-NC" |
| 2204 | depends on HAS_IOPORT |
| 2205 | depends on !PPC |
| 2206 | help |
| 2207 | If you say yes here you get support for the SMSC LPC47B397-NC |
| 2208 | sensor chip. |
| 2209 | |
| 2210 | This driver can also be built as a module. If so, the module |
| 2211 | will be called smsc47b397. |
| 2212 | |
| 2213 | config SENSORS_SCH56XX_COMMON |
| 2214 | tristate |
| 2215 | select REGMAP |
| 2216 | |
| 2217 | config SENSORS_SCH5627 |
| 2218 | tristate "SMSC SCH5627" |
| 2219 | depends on HAS_IOPORT |
| 2220 | depends on !PPC && WATCHDOG |
| 2221 | select SENSORS_SCH56XX_COMMON |
| 2222 | select WATCHDOG_CORE |
| 2223 | help |
| 2224 | If you say yes here you get support for the hardware monitoring |
| 2225 | features of the SMSC SCH5627 Super-I/O chip including support for |
| 2226 | the integrated watchdog. |
| 2227 | |
| 2228 | This driver can also be built as a module. If so, the module |
| 2229 | will be called sch5627. |
| 2230 | |
| 2231 | config SENSORS_SCH5636 |
| 2232 | tristate "SMSC SCH5636" |
| 2233 | depends on HAS_IOPORT |
| 2234 | depends on !PPC && WATCHDOG |
| 2235 | select SENSORS_SCH56XX_COMMON |
| 2236 | select WATCHDOG_CORE |
| 2237 | help |
| 2238 | SMSC SCH5636 Super I/O chips include an embedded microcontroller for |
| 2239 | hardware monitoring solutions, allowing motherboard manufacturers to |
| 2240 | create their own custom hwmon solution based upon the SCH5636. |
| 2241 | |
| 2242 | Currently this driver only supports the Fujitsu Theseus SCH5636 based |
| 2243 | hwmon solution. Say yes here if you want support for the Fujitsu |
| 2244 | Theseus' hardware monitoring features including support for the |
| 2245 | integrated watchdog. |
| 2246 | |
| 2247 | This driver can also be built as a module. If so, the module |
| 2248 | will be called sch5636. |
| 2249 | |
| 2250 | config SENSORS_STTS751 |
| 2251 | tristate "ST Microelectronics STTS751" |
| 2252 | depends on I2C |
| 2253 | help |
| 2254 | If you say yes here you get support for STTS751 |
| 2255 | temperature sensor chips. |
| 2256 | |
| 2257 | This driver can also be built as a module. If so, the module |
| 2258 | will be called stts751. |
| 2259 | |
| 2260 | config SENSORS_SFCTEMP |
| 2261 | tristate "Starfive JH71x0 temperature sensor" |
| 2262 | depends on ARCH_STARFIVE || COMPILE_TEST |
| 2263 | help |
| 2264 | If you say yes here you get support for temperature sensor |
| 2265 | on the Starfive JH71x0 SoCs. |
| 2266 | |
| 2267 | This driver can also be built as a module. If so, the module |
| 2268 | will be called sfctemp. |
| 2269 | |
| 2270 | config SENSORS_SG2042_MCU |
| 2271 | tristate "Sophgo onboard MCU support" |
| 2272 | depends on I2C |
| 2273 | depends on ARCH_SOPHGO || COMPILE_TEST |
| 2274 | help |
| 2275 | Support for onboard MCU of Sophgo SG2042 SoCs. This mcu provides |
| 2276 | power control and some basic information. |
| 2277 | |
| 2278 | This driver can be built as a module. If so, the module |
| 2279 | will be called sg2042-mcu. |
| 2280 | |
| 2281 | config SENSORS_SURFACE_FAN |
| 2282 | tristate "Surface Fan Driver" |
| 2283 | depends on SURFACE_AGGREGATOR |
| 2284 | depends on SURFACE_AGGREGATOR_BUS |
| 2285 | help |
| 2286 | Driver that provides monitoring of the fan on Surface Pro devices that |
| 2287 | have a fan, like the Surface Pro 9. |
| 2288 | |
| 2289 | This makes the fan's current speed accessible through the hwmon |
| 2290 | system. It does not provide control over the fan, the firmware is |
| 2291 | responsible for that, this driver merely provides monitoring. |
| 2292 | |
| 2293 | Select M or Y here, if you want to be able to read the fan's speed. |
| 2294 | |
| 2295 | config SENSORS_SURFACE_TEMP |
| 2296 | tristate "Microsoft Surface Thermal Sensor Driver" |
| 2297 | depends on SURFACE_AGGREGATOR |
| 2298 | depends on SURFACE_AGGREGATOR_BUS |
| 2299 | help |
| 2300 | Driver for monitoring thermal sensors connected via the Surface |
| 2301 | Aggregator Module (embedded controller) on Microsoft Surface devices. |
| 2302 | |
| 2303 | This driver can also be built as a module. If so, the module |
| 2304 | will be called surface_temp. |
| 2305 | |
| 2306 | config SENSORS_ADC128D818 |
| 2307 | tristate "Texas Instruments ADC128D818" |
| 2308 | depends on I2C |
| 2309 | help |
| 2310 | If you say yes here you get support for the Texas Instruments |
| 2311 | ADC128D818 System Monitor with Temperature Sensor chip. |
| 2312 | |
| 2313 | This driver can also be built as a module. If so, the module |
| 2314 | will be called adc128d818. |
| 2315 | |
| 2316 | config SENSORS_ADS7828 |
| 2317 | tristate "Texas Instruments ADS7828 and compatibles" |
| 2318 | depends on I2C |
| 2319 | select REGMAP_I2C |
| 2320 | help |
| 2321 | If you say yes here you get support for Texas Instruments ADS7828 and |
| 2322 | ADS7830 8-channel A/D converters. ADS7828 resolution is 12-bit, while |
| 2323 | it is 8-bit on ADS7830. |
| 2324 | |
| 2325 | This driver can also be built as a module. If so, the module |
| 2326 | will be called ads7828. |
| 2327 | |
| 2328 | config SENSORS_ADS7871 |
| 2329 | tristate "Texas Instruments ADS7871 A/D converter" |
| 2330 | depends on SPI |
| 2331 | help |
| 2332 | If you say yes here you get support for TI ADS7871 & ADS7870 |
| 2333 | |
| 2334 | This driver can also be built as a module. If so, the module |
| 2335 | will be called ads7871. |
| 2336 | |
| 2337 | config SENSORS_AMC6821 |
| 2338 | tristate "Texas Instruments AMC6821" |
| 2339 | depends on I2C |
| 2340 | select REGMAP_I2C |
| 2341 | help |
| 2342 | If you say yes here you get support for the Texas Instruments |
| 2343 | AMC6821 hardware monitoring chips. |
| 2344 | |
| 2345 | This driver can also be built as a module. If so, the module |
| 2346 | will be called amc6821. |
| 2347 | |
| 2348 | config SENSORS_INA209 |
| 2349 | tristate "TI / Burr Brown INA209" |
| 2350 | depends on I2C |
| 2351 | help |
| 2352 | If you say yes here you get support for the TI / Burr Brown INA209 |
| 2353 | voltage / current / power monitor I2C interface. |
| 2354 | |
| 2355 | This driver can also be built as a module. If so, the module will |
| 2356 | be called ina209. |
| 2357 | |
| 2358 | config SENSORS_INA2XX |
| 2359 | tristate "Texas Instruments INA219 and compatibles" |
| 2360 | depends on I2C |
| 2361 | select REGMAP_I2C |
| 2362 | help |
| 2363 | If you say yes here you get support for INA219, INA220, INA226, |
| 2364 | INA230, INA231, INA234, INA260, and SY24655 power monitor chips. |
| 2365 | |
| 2366 | The INA2xx driver is configured for the default configuration of |
| 2367 | the part as described in the datasheet. |
| 2368 | Default value for Rshunt is 10 mOhms except for INA260 which has an |
| 2369 | internal 2 mOhm shunt resistor. |
| 2370 | This driver can also be built as a module. If so, the module |
| 2371 | will be called ina2xx. |
| 2372 | |
| 2373 | config SENSORS_INA238 |
| 2374 | tristate "Texas Instruments INA238 and compatibles" |
| 2375 | depends on I2C |
| 2376 | select REGMAP_I2C |
| 2377 | help |
| 2378 | If you say yes here you get support for INA228, INA237, INA238, |
| 2379 | INA700, INA780, and SQ52206 power monitor chips. This driver supports |
| 2380 | voltage, current, power, energy, and temperature measurements as well |
| 2381 | as alarm configuration. |
| 2382 | |
| 2383 | This driver can also be built as a module. If so, the module |
| 2384 | will be called ina238. |
| 2385 | |
| 2386 | config SENSORS_INA3221 |
| 2387 | tristate "Texas Instruments INA3221 Triple Power Monitor" |
| 2388 | depends on I2C |
| 2389 | select REGMAP_I2C |
| 2390 | help |
| 2391 | If you say yes here you get support for the TI INA3221 Triple Power |
| 2392 | Monitor. |
| 2393 | |
| 2394 | This driver can also be built as a module. If so, the module |
| 2395 | will be called ina3221. |
| 2396 | |
| 2397 | config SENSORS_SPD5118 |
| 2398 | tristate "SPD5118 Compliant Temperature Sensors" |
| 2399 | depends on I3C_OR_I2C |
| 2400 | select REGMAP_I2C |
| 2401 | select REGMAP_I3C if I3C |
| 2402 | help |
| 2403 | If you say yes here you get support for SPD5118 (JEDEC JESD300) |
| 2404 | compliant temperature sensors using I2C or I3C bus interface. |
| 2405 | Such sensors are found on DDR5 memory modules. |
| 2406 | |
| 2407 | This driver supports both I2C and I3C interfaces. |
| 2408 | |
| 2409 | This driver can also be built as a module. If so, the module |
| 2410 | will be called spd5118. |
| 2411 | |
| 2412 | config SENSORS_SPD5118_DETECT |
| 2413 | bool "Enable detect function" |
| 2414 | depends on SENSORS_SPD5118 |
| 2415 | default (!DMI || !X86) |
| 2416 | help |
| 2417 | If enabled, the driver auto-detects if a chip in the SPD address |
| 2418 | range is compliant to the SPD51888 standard and auto-instantiates |
| 2419 | if that is the case. If disabled, SPD5118 compliant devices have |
| 2420 | to be instantiated by other means. On X86 systems with DMI support |
| 2421 | this will typically be done from DMI DDR detection code in the |
| 2422 | I2C SMBus subsystem. Devicetree based systems will instantiate |
| 2423 | attached devices if the DIMMs are listed in the devicetree file. |
| 2424 | |
| 2425 | Disabling the detect function will speed up boot time and reduce |
| 2426 | the risk of mis-detecting SPD5118 compliant devices. However, it |
| 2427 | may result in missed DIMMs under some circumstances. |
| 2428 | |
| 2429 | If unsure, say Y. |
| 2430 | |
| 2431 | config SENSORS_TC74 |
| 2432 | tristate "Microchip TC74" |
| 2433 | depends on I2C |
| 2434 | help |
| 2435 | If you say yes here you get support for Microchip TC74 single |
| 2436 | input temperature sensor chips. |
| 2437 | |
| 2438 | This driver can also be built as a module. If so, the module |
| 2439 | will be called tc74. |
| 2440 | |
| 2441 | config SENSORS_THMC50 |
| 2442 | tristate "Texas Instruments THMC50 / Analog Devices ADM1022" |
| 2443 | depends on I2C |
| 2444 | help |
| 2445 | If you say yes here you get support for Texas Instruments THMC50 |
| 2446 | sensor chips and clones: the Analog Devices ADM1022. |
| 2447 | |
| 2448 | This driver can also be built as a module. If so, the module |
| 2449 | will be called thmc50. |
| 2450 | |
| 2451 | config SENSORS_TMP102 |
| 2452 | tristate "Texas Instruments TMP102" |
| 2453 | depends on I2C |
| 2454 | select REGMAP_I2C |
| 2455 | help |
| 2456 | If you say yes here you get support for Texas Instruments TMP102, |
| 2457 | TMP110 and TMP113 sensor chips. |
| 2458 | |
| 2459 | This driver can also be built as a module. If so, the module |
| 2460 | will be called tmp102. |
| 2461 | |
| 2462 | config SENSORS_TMP103 |
| 2463 | tristate "Texas Instruments TMP103" |
| 2464 | depends on I2C |
| 2465 | select REGMAP_I2C |
| 2466 | help |
| 2467 | If you say yes here you get support for Texas Instruments TMP103 |
| 2468 | sensor chips. |
| 2469 | |
| 2470 | This driver can also be built as a module. If so, the module |
| 2471 | will be called tmp103. |
| 2472 | |
| 2473 | config SENSORS_TMP108 |
| 2474 | tristate "Texas Instruments TMP108" |
| 2475 | depends on I3C_OR_I2C |
| 2476 | select REGMAP_I2C |
| 2477 | select REGMAP_I3C if I3C |
| 2478 | help |
| 2479 | If you say yes here you get support for Texas Instruments TMP108 |
| 2480 | sensor chips, NXP temperature sensors P3T1035, P3T1085 and P3T2030. |
| 2481 | |
| 2482 | This driver can also be built as a module. If so, the module |
| 2483 | will be called tmp108. |
| 2484 | |
| 2485 | config SENSORS_TMP401 |
| 2486 | tristate "Texas Instruments TMP401 and compatibles" |
| 2487 | depends on I2C |
| 2488 | select REGMAP |
| 2489 | help |
| 2490 | If you say yes here you get support for Texas Instruments TMP401, |
| 2491 | TMP411, TMP431, TMP432, and TMP435 temperature sensor chips. |
| 2492 | |
| 2493 | This driver can also be built as a module. If so, the module |
| 2494 | will be called tmp401. |
| 2495 | |
| 2496 | config SENSORS_TMP421 |
| 2497 | tristate "Texas Instruments TMP421 and compatible" |
| 2498 | depends on I2C |
| 2499 | help |
| 2500 | If you say yes here you get support for Texas Instruments TMP421, |
| 2501 | TMP422, TMP423, TMP441, and TMP442 temperature sensor chips. |
| 2502 | |
| 2503 | This driver can also be built as a module. If so, the module |
| 2504 | will be called tmp421. |
| 2505 | |
| 2506 | config SENSORS_TMP464 |
| 2507 | tristate "Texas Instruments TMP464 and compatible" |
| 2508 | depends on I2C |
| 2509 | select REGMAP_I2C |
| 2510 | help |
| 2511 | If you say yes here you get support for Texas Instruments TMP464 |
| 2512 | and TMP468 temperature sensor chips. |
| 2513 | |
| 2514 | This driver can also be built as a module. If so, the module |
| 2515 | will be called tmp464. |
| 2516 | |
| 2517 | config SENSORS_TMP513 |
| 2518 | tristate "Texas Instruments TMP513 and compatibles" |
| 2519 | depends on I2C |
| 2520 | select REGMAP_I2C |
| 2521 | help |
| 2522 | If you say yes here you get support for Texas Instruments TMP512, |
| 2523 | and TMP513 temperature and power supply sensor chips. |
| 2524 | |
| 2525 | This driver can also be built as a module. If so, the module |
| 2526 | will be called tmp513. |
| 2527 | |
| 2528 | config SENSORS_TSC1641 |
| 2529 | tristate "ST Microelectronics TSC1641 Power Monitor" |
| 2530 | depends on I2C |
| 2531 | select REGMAP_I2C |
| 2532 | help |
| 2533 | If you say yes here you get support for TSC1641 power monitor chip. |
| 2534 | The TSC1641 driver is configured for the default configuration of |
| 2535 | the part except temperature is enabled by default. |
| 2536 | |
| 2537 | This driver can also be built as a module. If so, the module |
| 2538 | will be called tsc1641. |
| 2539 | |
| 2540 | config SENSORS_VEXPRESS |
| 2541 | tristate "Versatile Express" |
| 2542 | depends on VEXPRESS_CONFIG |
| 2543 | help |
| 2544 | This driver provides support for hardware sensors available on |
| 2545 | the ARM Ltd's Versatile Express platform. It can provide wide |
| 2546 | range of information like temperature, power, energy. |
| 2547 | |
| 2548 | config SENSORS_VIA_CPUTEMP |
| 2549 | tristate "VIA CPU temperature sensor" |
| 2550 | depends on X86 |
| 2551 | select HWMON_VID |
| 2552 | help |
| 2553 | If you say yes here you get support for the temperature |
| 2554 | sensor inside your CPU. Supported are all known variants of |
| 2555 | the VIA C7 and Nano. |
| 2556 | |
| 2557 | config SENSORS_VIA686A |
| 2558 | tristate "VIA686A" |
| 2559 | depends on PCI && HAS_IOPORT |
| 2560 | help |
| 2561 | If you say yes here you get support for the integrated sensors in |
| 2562 | Via 686A/B South Bridges. |
| 2563 | |
| 2564 | This driver can also be built as a module. If so, the module |
| 2565 | will be called via686a. |
| 2566 | |
| 2567 | config SENSORS_VT1211 |
| 2568 | tristate "VIA VT1211" |
| 2569 | depends on HAS_IOPORT |
| 2570 | depends on !PPC |
| 2571 | select HWMON_VID |
| 2572 | help |
| 2573 | If you say yes here then you get support for hardware monitoring |
| 2574 | features of the VIA VT1211 Super-I/O chip. |
| 2575 | |
| 2576 | This driver can also be built as a module. If so, the module |
| 2577 | will be called vt1211. |
| 2578 | |
| 2579 | config SENSORS_VT8231 |
| 2580 | tristate "VIA VT8231" |
| 2581 | depends on PCI && HAS_IOPORT |
| 2582 | select HWMON_VID |
| 2583 | help |
| 2584 | If you say yes here then you get support for the integrated sensors |
| 2585 | in the VIA VT8231 device. |
| 2586 | |
| 2587 | This driver can also be built as a module. If so, the module |
| 2588 | will be called vt8231. |
| 2589 | |
| 2590 | config SENSORS_W83773G |
| 2591 | tristate "Nuvoton W83773G" |
| 2592 | depends on I2C |
| 2593 | select REGMAP_I2C |
| 2594 | help |
| 2595 | If you say yes here you get support for the Nuvoton W83773G hardware |
| 2596 | monitoring chip. |
| 2597 | |
| 2598 | This driver can also be built as a module. If so, the module |
| 2599 | will be called w83773g. |
| 2600 | |
| 2601 | config SENSORS_W83781D |
| 2602 | tristate "Winbond W83781D, W83782D, W83783S, Asus AS99127F" |
| 2603 | depends on I2C |
| 2604 | select HWMON_VID |
| 2605 | help |
| 2606 | If you say yes here you get support for the Winbond W8378x series |
| 2607 | of sensor chips: the W83781D, W83782D and W83783S, and the similar |
| 2608 | Asus AS99127F. |
| 2609 | |
| 2610 | This driver can also be built as a module. If so, the module |
| 2611 | will be called w83781d. |
| 2612 | |
| 2613 | config SENSORS_W83791D |
| 2614 | tristate "Winbond W83791D" |
| 2615 | depends on I2C |
| 2616 | select HWMON_VID |
| 2617 | help |
| 2618 | If you say yes here you get support for the Winbond W83791D chip. |
| 2619 | |
| 2620 | This driver can also be built as a module. If so, the module |
| 2621 | will be called w83791d. |
| 2622 | |
| 2623 | config SENSORS_W83792D |
| 2624 | tristate "Winbond W83792D" |
| 2625 | depends on I2C |
| 2626 | help |
| 2627 | If you say yes here you get support for the Winbond W83792D chip. |
| 2628 | |
| 2629 | This driver can also be built as a module. If so, the module |
| 2630 | will be called w83792d. |
| 2631 | |
| 2632 | config SENSORS_W83793 |
| 2633 | tristate "Winbond W83793" |
| 2634 | depends on I2C |
| 2635 | select HWMON_VID |
| 2636 | help |
| 2637 | If you say yes here you get support for the Winbond W83793 |
| 2638 | hardware monitoring chip, including support for the integrated |
| 2639 | watchdog. |
| 2640 | |
| 2641 | This driver can also be built as a module. If so, the module |
| 2642 | will be called w83793. |
| 2643 | |
| 2644 | config SENSORS_W83795 |
| 2645 | tristate "Winbond/Nuvoton W83795G/ADG" |
| 2646 | depends on I2C |
| 2647 | help |
| 2648 | If you say yes here you get support for the Winbond W83795G and |
| 2649 | W83795ADG hardware monitoring chip, including manual fan speed |
| 2650 | control. |
| 2651 | |
| 2652 | This driver can also be built as a module. If so, the module |
| 2653 | will be called w83795. |
| 2654 | |
| 2655 | config SENSORS_W83795_FANCTRL |
| 2656 | bool "Include automatic fan control support" |
| 2657 | depends on SENSORS_W83795 |
| 2658 | help |
| 2659 | If you say yes here, support for automatic fan speed control |
| 2660 | will be included in the driver. |
| 2661 | |
| 2662 | Please also note that this option will create sysfs attribute |
| 2663 | files which may change in the future, so you shouldn't rely |
| 2664 | on them being stable. |
| 2665 | |
| 2666 | config SENSORS_W83L785TS |
| 2667 | tristate "Winbond W83L785TS-S" |
| 2668 | depends on I2C |
| 2669 | help |
| 2670 | If you say yes here you get support for the Winbond W83L785TS-S |
| 2671 | sensor chip, which is used on the Asus A7N8X, among other |
| 2672 | motherboards. |
| 2673 | |
| 2674 | This driver can also be built as a module. If so, the module |
| 2675 | will be called w83l785ts. |
| 2676 | |
| 2677 | config SENSORS_W83L786NG |
| 2678 | tristate "Winbond W83L786NG, W83L786NR" |
| 2679 | depends on I2C |
| 2680 | help |
| 2681 | If you say yes here you get support for the Winbond W83L786NG |
| 2682 | and W83L786NR sensor chips. |
| 2683 | |
| 2684 | This driver can also be built as a module. If so, the module |
| 2685 | will be called w83l786ng. |
| 2686 | |
| 2687 | config SENSORS_W83627HF |
| 2688 | tristate "Winbond W83627HF, W83627THF, W83637HF, W83687THF, W83697HF" |
| 2689 | depends on HAS_IOPORT |
| 2690 | depends on !PPC |
| 2691 | select HWMON_VID |
| 2692 | help |
| 2693 | If you say yes here you get support for the Winbond W836X7 series |
| 2694 | of sensor chips: the W83627HF, W83627THF, W83637HF, W83687THF and |
| 2695 | W83697HF. |
| 2696 | |
| 2697 | This driver can also be built as a module. If so, the module |
| 2698 | will be called w83627hf. |
| 2699 | |
| 2700 | config SENSORS_W83627EHF |
| 2701 | tristate "Winbond W83627EHF/EHG/DHG/UHG, W83667HG" |
| 2702 | depends on HAS_IOPORT |
| 2703 | depends on !PPC |
| 2704 | select HWMON_VID |
| 2705 | help |
| 2706 | If you say yes here you get support for the hardware |
| 2707 | monitoring functionality of the Winbond W83627EHF Super-I/O chip. |
| 2708 | |
| 2709 | This driver also supports the W83627EHG, which is the lead-free |
| 2710 | version of the W83627EHF, and the W83627DHG, which is a similar |
| 2711 | chip suited for specific Intel processors that use PECI such as |
| 2712 | the Core 2 Duo. And also the W83627UHG, which is a stripped down |
| 2713 | version of the W83627DHG (as far as hardware monitoring goes.) |
| 2714 | |
| 2715 | This driver also supports Nuvoton W83667HG and W83667HG-B. |
| 2716 | |
| 2717 | This driver can also be built as a module. If so, the module |
| 2718 | will be called w83627ehf. |
| 2719 | |
| 2720 | config SENSORS_WM831X |
| 2721 | tristate "WM831x PMICs" |
| 2722 | depends on MFD_WM831X |
| 2723 | help |
| 2724 | If you say yes here you get support for the hardware |
| 2725 | monitoring functionality of the Wolfson Microelectronics |
| 2726 | WM831x series of PMICs. |
| 2727 | |
| 2728 | This driver can also be built as a module. If so, the module |
| 2729 | will be called wm831x-hwmon. |
| 2730 | |
| 2731 | config SENSORS_WM8350 |
| 2732 | tristate "Wolfson Microelectronics WM835x" |
| 2733 | depends on MFD_WM8350 |
| 2734 | help |
| 2735 | If you say yes here you get support for the hardware |
| 2736 | monitoring features of the WM835x series of PMICs. |
| 2737 | |
| 2738 | This driver can also be built as a module. If so, the module |
| 2739 | will be called wm8350-hwmon. |
| 2740 | |
| 2741 | config SENSORS_ULTRA45 |
| 2742 | tristate "Sun Ultra45 PIC16F747" |
| 2743 | depends on SPARC64 |
| 2744 | help |
| 2745 | This driver provides support for the Ultra45 workstation environmental |
| 2746 | sensors. |
| 2747 | |
| 2748 | config SENSORS_XGENE |
| 2749 | tristate "APM X-Gene SoC hardware monitoring driver" |
| 2750 | depends on XGENE_SLIMPRO_MBOX || PCC |
| 2751 | help |
| 2752 | If you say yes here you get support for the temperature |
| 2753 | and power sensors for APM X-Gene SoC. |
| 2754 | |
| 2755 | config SENSORS_YOGAFAN |
| 2756 | tristate "Lenovo Yoga Fan Hardware Monitoring" |
| 2757 | depends on ACPI && HWMON && DMI |
| 2758 | help |
| 2759 | If you say yes here you get support for fan speed monitoring |
| 2760 | on Lenovo Yoga, Legion, IdeaPad, Slim and LOQ laptops. |
| 2761 | The driver interfaces with the Embedded Controller via ACPI |
| 2762 | and uses a Rate-Limited Lag filter to smooth RPM readings. |
| 2763 | |
| 2764 | This driver can also be built as a module. If so, the module |
| 2765 | will be called yogafan. |
| 2766 | |
| 2767 | config SENSORS_INTEL_M10_BMC_HWMON |
| 2768 | tristate "Intel MAX10 BMC Hardware Monitoring" |
| 2769 | depends on MFD_INTEL_M10_BMC_CORE |
| 2770 | help |
| 2771 | This driver provides support for the hardware monitoring functionality |
| 2772 | on Intel MAX10 BMC chip. |
| 2773 | |
| 2774 | This BMC Chip is used on Intel FPGA PCIe Acceleration Cards (PAC). Its |
| 2775 | sensors monitor various telemetry data of different components on the |
| 2776 | card, e.g. board temperature, FPGA core temperature/voltage/current. |
| 2777 | |
| 2778 | if ACPI |
| 2779 | |
| 2780 | comment "ACPI drivers" |
| 2781 | |
| 2782 | config SENSORS_ACPI_POWER |
| 2783 | tristate "ACPI 4.0 power meter" |
| 2784 | help |
| 2785 | This driver exposes ACPI 4.0 power meters as hardware monitoring |
| 2786 | devices. Say Y (or M) if you have a computer with ACPI 4.0 firmware |
| 2787 | and a power meter. |
| 2788 | |
| 2789 | To compile this driver as a module, choose M here: |
| 2790 | the module will be called acpi_power_meter. |
| 2791 | |
| 2792 | config SENSORS_ATK0110 |
| 2793 | tristate "ASUS ATK0110" |
| 2794 | depends on X86 |
| 2795 | help |
| 2796 | If you say yes here you get support for the ACPI hardware |
| 2797 | monitoring interface found in many ASUS motherboards. This |
| 2798 | driver will provide readings of fans, voltages and temperatures |
| 2799 | through the system firmware. |
| 2800 | |
| 2801 | This driver can also be built as a module. If so, the module |
| 2802 | will be called asus_atk0110. |
| 2803 | |
| 2804 | config SENSORS_ASUS_WMI |
| 2805 | tristate "ASUS WMI X370/X470/B450/X399" |
| 2806 | depends on ACPI_WMI |
| 2807 | help |
| 2808 | If you say yes here you get support for the ACPI hardware monitoring |
| 2809 | interface found in X370/X470/B450/X399 ASUS motherboards. This driver |
| 2810 | will provide readings of fans, voltages and temperatures through the system |
| 2811 | firmware. |
| 2812 | |
| 2813 | This driver can also be built as a module. If so, the module |
| 2814 | will be called asus_wmi_sensors. |
| 2815 | |
| 2816 | config SENSORS_ASUS_EC |
| 2817 | tristate "ASUS EC Sensors" |
| 2818 | depends on X86 |
| 2819 | depends on ACPI_EC |
| 2820 | help |
| 2821 | If you say yes here you get support for the ACPI embedded controller |
| 2822 | hardware monitoring interface found in some ASUS motherboards. This is |
| 2823 | where such sensors as water flow and temperature, optional fans, and |
| 2824 | additional temperature sensors (T_Sensor, chipset temperatures) |
| 2825 | find themselves. |
| 2826 | |
| 2827 | This driver can also be built as a module. If so, the module |
| 2828 | will be called asus_ec_sensors. |
| 2829 | |
| 2830 | config SENSORS_HP_WMI |
| 2831 | tristate "HP WMI Sensors" |
| 2832 | depends on ACPI_WMI |
| 2833 | help |
| 2834 | If you say yes here you get support for the ACPI hardware monitoring |
| 2835 | interface found in HP (and some HP Compaq) business-class computers. |
| 2836 | Available sensors vary between systems. Temperature and fan speed |
| 2837 | sensors are the most common. |
| 2838 | |
| 2839 | This driver can also be built as a module. If so, the module |
| 2840 | will be called hp_wmi_sensors. |
| 2841 | |
| 2842 | endif # ACPI |
| 2843 | |
| 2844 | endif # HWMON |