| 1 | # |
| 2 | # Hardware monitoring chip drivers configuration |
| 3 | # |
| 4 | |
| 5 | menuconfig HWMON |
| 6 | tristate "Hardware Monitoring support" |
| 7 | depends on HAS_IOMEM |
| 8 | default y |
| 9 | help |
| 10 | Hardware monitoring devices let you monitor the hardware health |
| 11 | of a system. Most modern motherboards include such a device. It |
| 12 | can include temperature sensors, voltage sensors, fan speed |
| 13 | sensors and various additional features such as the ability to |
| 14 | control the speed of the fans. If you want this support you |
| 15 | should say Y here and also to the specific driver(s) for your |
| 16 | sensors chip(s) below. |
| 17 | |
| 18 | To find out which specific driver(s) you need, use the |
| 19 | sensors-detect script from the lm_sensors package. Read |
| 20 | <file:Documentation/hwmon/userspace-tools> for details. |
| 21 | |
| 22 | This support can also be built as a module. If so, the module |
| 23 | will be called hwmon. |
| 24 | |
| 25 | if HWMON |
| 26 | |
| 27 | config HWMON_VID |
| 28 | tristate |
| 29 | default n |
| 30 | |
| 31 | config HWMON_DEBUG_CHIP |
| 32 | bool "Hardware Monitoring Chip debugging messages" |
| 33 | default n |
| 34 | help |
| 35 | Say Y here if you want the I2C chip drivers to produce a bunch of |
| 36 | debug messages to the system log. Select this if you are having |
| 37 | a problem with I2C support and want to see more of what is going |
| 38 | on. |
| 39 | |
| 40 | comment "Native drivers" |
| 41 | |
| 42 | config SENSORS_ABITUGURU |
| 43 | tristate "Abit uGuru (rev 1 & 2)" |
| 44 | depends on X86 && DMI && EXPERIMENTAL |
| 45 | help |
| 46 | If you say yes here you get support for the sensor part of the first |
| 47 | and second revision of the Abit uGuru chip. The voltage and frequency |
| 48 | control parts of the Abit uGuru are not supported. The Abit uGuru |
| 49 | chip can be found on Abit uGuru featuring motherboards (most modern |
| 50 | Abit motherboards from before end 2005). For more info and a list |
| 51 | of which motherboards have which revision see |
| 52 | Documentation/hwmon/abituguru |
| 53 | |
| 54 | This driver can also be built as a module. If so, the module |
| 55 | will be called abituguru. |
| 56 | |
| 57 | config SENSORS_ABITUGURU3 |
| 58 | tristate "Abit uGuru (rev 3)" |
| 59 | depends on X86 && DMI && EXPERIMENTAL |
| 60 | help |
| 61 | If you say yes here you get support for the sensor part of the |
| 62 | third revision of the Abit uGuru chip. Only reading the sensors |
| 63 | and their settings is supported. The third revision of the Abit |
| 64 | uGuru chip can be found on recent Abit motherboards (since end |
| 65 | 2005). For more info and a list of which motherboards have which |
| 66 | revision see Documentation/hwmon/abituguru3 |
| 67 | |
| 68 | This driver can also be built as a module. If so, the module |
| 69 | will be called abituguru3. |
| 70 | |
| 71 | config SENSORS_AD7414 |
| 72 | tristate "Analog Devices AD7414" |
| 73 | depends on I2C && EXPERIMENTAL |
| 74 | help |
| 75 | If you say yes here you get support for the Analog Devices |
| 76 | AD7414 temperature monitoring chip. |
| 77 | |
| 78 | This driver can also be built as a module. If so, the module |
| 79 | will be called ad7414. |
| 80 | |
| 81 | config SENSORS_AD7418 |
| 82 | tristate "Analog Devices AD7416, AD7417 and AD7418" |
| 83 | depends on I2C && EXPERIMENTAL |
| 84 | help |
| 85 | If you say yes here you get support for the Analog Devices |
| 86 | AD7416, AD7417 and AD7418 temperature monitoring chips. |
| 87 | |
| 88 | This driver can also be built as a module. If so, the module |
| 89 | will be called ad7418. |
| 90 | |
| 91 | config SENSORS_ADCXX |
| 92 | tristate "National Semiconductor ADCxxxSxxx" |
| 93 | depends on SPI_MASTER && EXPERIMENTAL |
| 94 | help |
| 95 | If you say yes here you get support for the National Semiconductor |
| 96 | ADC<bb><c>S<sss> chip family, where |
| 97 | * bb is the resolution in number of bits (8, 10, 12) |
| 98 | * c is the number of channels (1, 2, 4, 8) |
| 99 | * sss is the maximum conversion speed (021 for 200 kSPS, 051 for 500 |
| 100 | kSPS and 101 for 1 MSPS) |
| 101 | |
| 102 | Examples : ADC081S101, ADC124S501, ... |
| 103 | |
| 104 | This driver can also be built as a module. If so, the module |
| 105 | will be called adcxx. |
| 106 | |
| 107 | config SENSORS_ADM1021 |
| 108 | tristate "Analog Devices ADM1021 and compatibles" |
| 109 | depends on I2C |
| 110 | help |
| 111 | If you say yes here you get support for Analog Devices ADM1021 |
| 112 | and ADM1023 sensor chips and clones: Maxim MAX1617 and MAX1617A, |
| 113 | Genesys Logic GL523SM, National Semiconductor LM84 and TI THMC10. |
| 114 | |
| 115 | This driver can also be built as a module. If so, the module |
| 116 | will be called adm1021. |
| 117 | |
| 118 | config SENSORS_ADM1025 |
| 119 | tristate "Analog Devices ADM1025 and compatibles" |
| 120 | depends on I2C |
| 121 | select HWMON_VID |
| 122 | help |
| 123 | If you say yes here you get support for Analog Devices ADM1025 |
| 124 | and Philips NE1619 sensor chips. |
| 125 | |
| 126 | This driver can also be built as a module. If so, the module |
| 127 | will be called adm1025. |
| 128 | |
| 129 | config SENSORS_ADM1026 |
| 130 | tristate "Analog Devices ADM1026 and compatibles" |
| 131 | depends on I2C |
| 132 | select HWMON_VID |
| 133 | help |
| 134 | If you say yes here you get support for Analog Devices ADM1026 |
| 135 | sensor chip. |
| 136 | |
| 137 | This driver can also be built as a module. If so, the module |
| 138 | will be called adm1026. |
| 139 | |
| 140 | config SENSORS_ADM1029 |
| 141 | tristate "Analog Devices ADM1029" |
| 142 | depends on I2C |
| 143 | help |
| 144 | If you say yes here you get support for Analog Devices ADM1029 |
| 145 | sensor chip. |
| 146 | Very rare chip, please let us know you use it. |
| 147 | |
| 148 | This driver can also be built as a module. If so, the module |
| 149 | will be called adm1029. |
| 150 | |
| 151 | config SENSORS_ADM1031 |
| 152 | tristate "Analog Devices ADM1031 and compatibles" |
| 153 | depends on I2C |
| 154 | help |
| 155 | If you say yes here you get support for Analog Devices ADM1031 |
| 156 | and ADM1030 sensor chips. |
| 157 | |
| 158 | This driver can also be built as a module. If so, the module |
| 159 | will be called adm1031. |
| 160 | |
| 161 | config SENSORS_ADM9240 |
| 162 | tristate "Analog Devices ADM9240 and compatibles" |
| 163 | depends on I2C |
| 164 | select HWMON_VID |
| 165 | help |
| 166 | If you say yes here you get support for Analog Devices ADM9240, |
| 167 | Dallas DS1780, National Semiconductor LM81 sensor chips. |
| 168 | |
| 169 | This driver can also be built as a module. If so, the module |
| 170 | will be called adm9240. |
| 171 | |
| 172 | config SENSORS_ADT7411 |
| 173 | tristate "Analog Devices ADT7411" |
| 174 | depends on I2C && EXPERIMENTAL |
| 175 | help |
| 176 | If you say yes here you get support for the Analog Devices |
| 177 | ADT7411 voltage and temperature monitoring chip. |
| 178 | |
| 179 | This driver can also be built as a module. If so, the module |
| 180 | will be called adt7411. |
| 181 | |
| 182 | config SENSORS_ADT7462 |
| 183 | tristate "Analog Devices ADT7462" |
| 184 | depends on I2C && EXPERIMENTAL |
| 185 | help |
| 186 | If you say yes here you get support for the Analog Devices |
| 187 | ADT7462 temperature monitoring chips. |
| 188 | |
| 189 | This driver can also be built as a module. If so, the module |
| 190 | will be called adt7462. |
| 191 | |
| 192 | config SENSORS_ADT7470 |
| 193 | tristate "Analog Devices ADT7470" |
| 194 | depends on I2C && EXPERIMENTAL |
| 195 | help |
| 196 | If you say yes here you get support for the Analog Devices |
| 197 | ADT7470 temperature monitoring chips. |
| 198 | |
| 199 | This driver can also be built as a module. If so, the module |
| 200 | will be called adt7470. |
| 201 | |
| 202 | config SENSORS_ADT7475 |
| 203 | tristate "Analog Devices ADT7473, ADT7475, ADT7476 and ADT7490" |
| 204 | depends on I2C |
| 205 | select HWMON_VID |
| 206 | help |
| 207 | If you say yes here you get support for the Analog Devices |
| 208 | ADT7473, ADT7475, ADT7476 and ADT7490 hardware monitoring |
| 209 | chips. |
| 210 | |
| 211 | This driver can also be build as a module. If so, the module |
| 212 | will be called adt7475. |
| 213 | |
| 214 | config SENSORS_ASC7621 |
| 215 | tristate "Andigilog aSC7621" |
| 216 | depends on I2C |
| 217 | help |
| 218 | If you say yes here you get support for the aSC7621 |
| 219 | family of SMBus sensors chip found on most Intel X38, X48, X58, |
| 220 | 945, 965 and 975 desktop boards. Currently supported chips: |
| 221 | aSC7621 |
| 222 | aSC7621a |
| 223 | |
| 224 | This driver can also be built as a module. If so, the module |
| 225 | will be called asc7621. |
| 226 | |
| 227 | config SENSORS_K8TEMP |
| 228 | tristate "AMD Athlon64/FX or Opteron temperature sensor" |
| 229 | depends on X86 && PCI && EXPERIMENTAL |
| 230 | help |
| 231 | If you say yes here you get support for the temperature |
| 232 | sensor(s) inside your CPU. Supported is whole AMD K8 |
| 233 | microarchitecture. Please note that you will need at least |
| 234 | lm-sensors 2.10.1 for proper userspace support. |
| 235 | |
| 236 | This driver can also be built as a module. If so, the module |
| 237 | will be called k8temp. |
| 238 | |
| 239 | config SENSORS_K10TEMP |
| 240 | tristate "AMD Family 10h+ temperature sensor" |
| 241 | depends on X86 && PCI |
| 242 | help |
| 243 | If you say yes here you get support for the temperature |
| 244 | sensor(s) inside your CPU. Supported are later revisions of |
| 245 | the AMD Family 10h and all revisions of the AMD Family 11h, |
| 246 | 12h (Llano), 14h (Brazos) and 15h (Bulldozer) microarchitectures. |
| 247 | |
| 248 | This driver can also be built as a module. If so, the module |
| 249 | will be called k10temp. |
| 250 | |
| 251 | config SENSORS_FAM15H_POWER |
| 252 | tristate "AMD Family 15h processor power" |
| 253 | depends on X86 && PCI |
| 254 | help |
| 255 | If you say yes here you get support for processor power |
| 256 | information of your AMD family 15h CPU. |
| 257 | |
| 258 | This driver can also be built as a module. If so, the module |
| 259 | will be called fam15h_power. |
| 260 | |
| 261 | config SENSORS_ASB100 |
| 262 | tristate "Asus ASB100 Bach" |
| 263 | depends on X86 && I2C && EXPERIMENTAL |
| 264 | select HWMON_VID |
| 265 | help |
| 266 | If you say yes here you get support for the ASB100 Bach sensor |
| 267 | chip found on some Asus mainboards. |
| 268 | |
| 269 | This driver can also be built as a module. If so, the module |
| 270 | will be called asb100. |
| 271 | |
| 272 | config SENSORS_ATXP1 |
| 273 | tristate "Attansic ATXP1 VID controller" |
| 274 | depends on I2C && EXPERIMENTAL |
| 275 | select HWMON_VID |
| 276 | help |
| 277 | If you say yes here you get support for the Attansic ATXP1 VID |
| 278 | controller. |
| 279 | |
| 280 | If your board have such a chip, you are able to control your CPU |
| 281 | core and other voltages. |
| 282 | |
| 283 | This driver can also be built as a module. If so, the module |
| 284 | will be called atxp1. |
| 285 | |
| 286 | config SENSORS_DS620 |
| 287 | tristate "Dallas Semiconductor DS620" |
| 288 | depends on I2C |
| 289 | help |
| 290 | If you say yes here you get support for Dallas Semiconductor |
| 291 | DS620 sensor chip. |
| 292 | |
| 293 | This driver can also be built as a module. If so, the module |
| 294 | will be called ds620. |
| 295 | |
| 296 | config SENSORS_DS1621 |
| 297 | tristate "Dallas Semiconductor DS1621 and DS1625" |
| 298 | depends on I2C |
| 299 | help |
| 300 | If you say yes here you get support for Dallas Semiconductor |
| 301 | DS1621 and DS1625 sensor chips. |
| 302 | |
| 303 | This driver can also be built as a module. If so, the module |
| 304 | will be called ds1621. |
| 305 | |
| 306 | config SENSORS_I5K_AMB |
| 307 | tristate "FB-DIMM AMB temperature sensor on Intel 5000 series chipsets" |
| 308 | depends on PCI && EXPERIMENTAL |
| 309 | help |
| 310 | If you say yes here you get support for FB-DIMM AMB temperature |
| 311 | monitoring chips on systems with the Intel 5000 series chipset. |
| 312 | |
| 313 | This driver can also be built as a module. If so, the module |
| 314 | will be called i5k_amb. |
| 315 | |
| 316 | config SENSORS_F71805F |
| 317 | tristate "Fintek F71805F/FG, F71806F/FG and F71872F/FG" |
| 318 | help |
| 319 | If you say yes here you get support for hardware monitoring |
| 320 | features of the Fintek F71805F/FG, F71806F/FG and F71872F/FG |
| 321 | Super-I/O chips. |
| 322 | |
| 323 | This driver can also be built as a module. If so, the module |
| 324 | will be called f71805f. |
| 325 | |
| 326 | config SENSORS_F71882FG |
| 327 | tristate "Fintek F71882FG and compatibles" |
| 328 | help |
| 329 | If you say yes here you get support for hardware monitoring |
| 330 | features of many Fintek Super-I/O (LPC) chips. The currently |
| 331 | supported chips are: |
| 332 | F71808E/A |
| 333 | F71858FG |
| 334 | F71862FG |
| 335 | F71863FG |
| 336 | F71869F/E/A |
| 337 | F71882FG |
| 338 | F71883FG |
| 339 | F71889FG/ED/A |
| 340 | F8000 |
| 341 | F81801U |
| 342 | F81865F |
| 343 | |
| 344 | This driver can also be built as a module. If so, the module |
| 345 | will be called f71882fg. |
| 346 | |
| 347 | config SENSORS_F75375S |
| 348 | tristate "Fintek F75375S/SP and F75373" |
| 349 | depends on I2C |
| 350 | help |
| 351 | If you say yes here you get support for hardware monitoring |
| 352 | features of the Fintek F75375S/SP and F75373 |
| 353 | |
| 354 | This driver can also be built as a module. If so, the module |
| 355 | will be called f75375s. |
| 356 | |
| 357 | config SENSORS_FSCHMD |
| 358 | tristate "Fujitsu Siemens Computers sensor chips" |
| 359 | depends on X86 && I2C |
| 360 | help |
| 361 | If you say yes here you get support for the following Fujitsu |
| 362 | Siemens Computers (FSC) sensor chips: Poseidon, Scylla, Hermes, |
| 363 | Heimdall, Heracles, Hades and Syleus including support for the |
| 364 | integrated watchdog. |
| 365 | |
| 366 | This is a merged driver for FSC sensor chips replacing the fscpos, |
| 367 | fscscy and fscher drivers and adding support for several other FSC |
| 368 | sensor chips. |
| 369 | |
| 370 | This driver can also be built as a module. If so, the module |
| 371 | will be called fschmd. |
| 372 | |
| 373 | config SENSORS_G760A |
| 374 | tristate "GMT G760A" |
| 375 | depends on I2C |
| 376 | help |
| 377 | If you say yes here you get support for Global Mixed-mode |
| 378 | Technology Inc G760A fan speed PWM controller chips. |
| 379 | |
| 380 | This driver can also be built as a module. If so, the module |
| 381 | will be called g760a. |
| 382 | |
| 383 | config SENSORS_GL518SM |
| 384 | tristate "Genesys Logic GL518SM" |
| 385 | depends on I2C |
| 386 | help |
| 387 | If you say yes here you get support for Genesys Logic GL518SM |
| 388 | sensor chips. |
| 389 | |
| 390 | This driver can also be built as a module. If so, the module |
| 391 | will be called gl518sm. |
| 392 | |
| 393 | config SENSORS_GL520SM |
| 394 | tristate "Genesys Logic GL520SM" |
| 395 | depends on I2C |
| 396 | select HWMON_VID |
| 397 | help |
| 398 | If you say yes here you get support for Genesys Logic GL520SM |
| 399 | sensor chips. |
| 400 | |
| 401 | This driver can also be built as a module. If so, the module |
| 402 | will be called gl520sm. |
| 403 | |
| 404 | config SENSORS_GPIO_FAN |
| 405 | tristate "GPIO fan" |
| 406 | depends on GENERIC_GPIO |
| 407 | help |
| 408 | If you say yes here you get support for fans connected to GPIO lines. |
| 409 | |
| 410 | This driver can also be built as a module. If so, the module |
| 411 | will be called gpio-fan. |
| 412 | |
| 413 | config SENSORS_CORETEMP |
| 414 | tristate "Intel Core/Core2/Atom temperature sensor" |
| 415 | depends on X86 && PCI && EXPERIMENTAL |
| 416 | help |
| 417 | If you say yes here you get support for the temperature |
| 418 | sensor inside your CPU. Most of the family 6 CPUs |
| 419 | are supported. Check Documentation/hwmon/coretemp for details. |
| 420 | |
| 421 | config SENSORS_IBMAEM |
| 422 | tristate "IBM Active Energy Manager temperature/power sensors and control" |
| 423 | select IPMI_SI |
| 424 | depends on IPMI_HANDLER |
| 425 | help |
| 426 | If you say yes here you get support for the temperature and |
| 427 | power sensors and capping hardware in various IBM System X |
| 428 | servers that support Active Energy Manager. This includes |
| 429 | the x3350, x3550, x3650, x3655, x3755, x3850 M2, x3950 M2, |
| 430 | and certain HC10/HS2x/LS2x/QS2x blades. |
| 431 | |
| 432 | This driver can also be built as a module. If so, the module |
| 433 | will be called ibmaem. |
| 434 | |
| 435 | config SENSORS_IBMPEX |
| 436 | tristate "IBM PowerExecutive temperature/power sensors" |
| 437 | select IPMI_SI |
| 438 | depends on IPMI_HANDLER |
| 439 | help |
| 440 | If you say yes here you get support for the temperature and |
| 441 | power sensors in various IBM System X servers that support |
| 442 | PowerExecutive. So far this includes the x3350, x3550, x3650, |
| 443 | x3655, and x3755; the x3800, x3850, and x3950 models that have |
| 444 | PCI Express; and some of the HS2x, LS2x, and QS2x blades. |
| 445 | |
| 446 | This driver can also be built as a module. If so, the module |
| 447 | will be called ibmpex. |
| 448 | |
| 449 | config SENSORS_IT87 |
| 450 | tristate "ITE IT87xx and compatibles" |
| 451 | select HWMON_VID |
| 452 | help |
| 453 | If you say yes here you get support for ITE IT8705F, IT8712F, |
| 454 | IT8716F, IT8718F, IT8720F, IT8721F, IT8726F and IT8758E sensor |
| 455 | chips, and the SiS960 clone. |
| 456 | |
| 457 | This driver can also be built as a module. If so, the module |
| 458 | will be called it87. |
| 459 | |
| 460 | config SENSORS_JZ4740 |
| 461 | tristate "Ingenic JZ4740 SoC ADC driver" |
| 462 | depends on MACH_JZ4740 && MFD_JZ4740_ADC |
| 463 | help |
| 464 | If you say yes here you get support for reading adc values from the ADCIN |
| 465 | pin on Ingenic JZ4740 SoC based boards. |
| 466 | |
| 467 | This driver can also be build as a module. If so, the module will be |
| 468 | called jz4740-hwmon. |
| 469 | |
| 470 | config SENSORS_JC42 |
| 471 | tristate "JEDEC JC42.4 compliant memory module temperature sensors" |
| 472 | depends on I2C |
| 473 | help |
| 474 | If you say yes here, you get support for JEDEC JC42.4 compliant |
| 475 | temperature sensors, which are used on many DDR3 memory modules for |
| 476 | mobile devices and servers. Support will include, but not be limited |
| 477 | to, ADT7408, CAT34TS02, CAT6095, MAX6604, MCP9805, MCP98242, MCP98243, |
| 478 | MCP9843, SE97, SE98, STTS424(E), TSE2002B3, and TS3000B3. |
| 479 | |
| 480 | This driver can also be built as a module. If so, the module |
| 481 | will be called jc42. |
| 482 | |
| 483 | config SENSORS_LINEAGE |
| 484 | tristate "Lineage Compact Power Line Power Entry Module" |
| 485 | depends on I2C && EXPERIMENTAL |
| 486 | help |
| 487 | If you say yes here you get support for the Lineage Compact Power Line |
| 488 | series of DC/DC and AC/DC converters such as CP1800, CP2000AC, |
| 489 | CP2000DC, CP2725, and others. |
| 490 | |
| 491 | This driver can also be built as a module. If so, the module |
| 492 | will be called lineage-pem. |
| 493 | |
| 494 | config SENSORS_LM63 |
| 495 | tristate "National Semiconductor LM63 and LM64" |
| 496 | depends on I2C |
| 497 | help |
| 498 | If you say yes here you get support for the National |
| 499 | Semiconductor LM63 and LM64 remote diode digital temperature |
| 500 | sensors with integrated fan control. Such chips are found |
| 501 | on the Tyan S4882 (Thunder K8QS Pro) motherboard, among |
| 502 | others. |
| 503 | |
| 504 | This driver can also be built as a module. If so, the module |
| 505 | will be called lm63. |
| 506 | |
| 507 | config SENSORS_LM70 |
| 508 | tristate "National Semiconductor LM70 / Texas Instruments TMP121" |
| 509 | depends on SPI_MASTER |
| 510 | help |
| 511 | If you say yes here you get support for the National Semiconductor |
| 512 | LM70 and Texas Instruments TMP121/TMP123 digital temperature |
| 513 | sensor chips. |
| 514 | |
| 515 | This driver can also be built as a module. If so, the module |
| 516 | will be called lm70. |
| 517 | |
| 518 | config SENSORS_LM73 |
| 519 | tristate "National Semiconductor LM73" |
| 520 | depends on I2C |
| 521 | help |
| 522 | If you say yes here you get support for National Semiconductor LM73 |
| 523 | sensor chips. |
| 524 | This driver can also be built as a module. If so, the module |
| 525 | will be called lm73. |
| 526 | |
| 527 | config SENSORS_LM75 |
| 528 | tristate "National Semiconductor LM75 and compatibles" |
| 529 | depends on I2C |
| 530 | help |
| 531 | If you say yes here you get support for one common type of |
| 532 | temperature sensor chip, with models including: |
| 533 | |
| 534 | - Dallas Semiconductor DS75 and DS1775 |
| 535 | - Maxim MAX6625 and MAX6626 |
| 536 | - Microchip MCP980x |
| 537 | - National Semiconductor LM75, LM75A |
| 538 | - NXP's LM75A |
| 539 | - ST Microelectronics STDS75 |
| 540 | - TelCom (now Microchip) TCN75 |
| 541 | - Texas Instruments TMP100, TMP101, TMP105, TMP75, TMP175, |
| 542 | TMP275 |
| 543 | |
| 544 | This driver supports driver model based binding through board |
| 545 | specific I2C device tables. |
| 546 | |
| 547 | It also supports the "legacy" style of driver binding. To use |
| 548 | that with some chips which don't replicate LM75 quirks exactly, |
| 549 | you may need the "force" module parameter. |
| 550 | |
| 551 | This driver can also be built as a module. If so, the module |
| 552 | will be called lm75. |
| 553 | |
| 554 | config SENSORS_LM77 |
| 555 | tristate "National Semiconductor LM77" |
| 556 | depends on I2C |
| 557 | help |
| 558 | If you say yes here you get support for National Semiconductor LM77 |
| 559 | sensor chips. |
| 560 | |
| 561 | This driver can also be built as a module. If so, the module |
| 562 | will be called lm77. |
| 563 | |
| 564 | config SENSORS_LM78 |
| 565 | tristate "National Semiconductor LM78 and compatibles" |
| 566 | depends on I2C |
| 567 | select HWMON_VID |
| 568 | help |
| 569 | If you say yes here you get support for National Semiconductor LM78, |
| 570 | LM78-J and LM79. |
| 571 | |
| 572 | This driver can also be built as a module. If so, the module |
| 573 | will be called lm78. |
| 574 | |
| 575 | config SENSORS_LM80 |
| 576 | tristate "National Semiconductor LM80" |
| 577 | depends on I2C |
| 578 | help |
| 579 | If you say yes here you get support for National Semiconductor |
| 580 | LM80 sensor chips. |
| 581 | |
| 582 | This driver can also be built as a module. If so, the module |
| 583 | will be called lm80. |
| 584 | |
| 585 | config SENSORS_LM83 |
| 586 | tristate "National Semiconductor LM83 and compatibles" |
| 587 | depends on I2C |
| 588 | help |
| 589 | If you say yes here you get support for National Semiconductor |
| 590 | LM82 and LM83 sensor chips. |
| 591 | |
| 592 | This driver can also be built as a module. If so, the module |
| 593 | will be called lm83. |
| 594 | |
| 595 | config SENSORS_LM85 |
| 596 | tristate "National Semiconductor LM85 and compatibles" |
| 597 | depends on I2C |
| 598 | select HWMON_VID |
| 599 | help |
| 600 | If you say yes here you get support for National Semiconductor LM85 |
| 601 | sensor chips and clones: ADM1027, ADT7463, ADT7468, EMC6D100, |
| 602 | EMC6D101, EMC6D102, and EMC6D103. |
| 603 | |
| 604 | This driver can also be built as a module. If so, the module |
| 605 | will be called lm85. |
| 606 | |
| 607 | config SENSORS_LM87 |
| 608 | tristate "National Semiconductor LM87 and compatibles" |
| 609 | depends on I2C |
| 610 | select HWMON_VID |
| 611 | help |
| 612 | If you say yes here you get support for National Semiconductor LM87 |
| 613 | and Analog Devices ADM1024 sensor chips. |
| 614 | |
| 615 | This driver can also be built as a module. If so, the module |
| 616 | will be called lm87. |
| 617 | |
| 618 | config SENSORS_LM90 |
| 619 | tristate "National Semiconductor LM90 and compatibles" |
| 620 | depends on I2C |
| 621 | help |
| 622 | If you say yes here you get support for National Semiconductor LM90, |
| 623 | LM86, LM89 and LM99, Analog Devices ADM1032, ADT7461, and ADT7461A, |
| 624 | Maxim MAX6646, MAX6647, MAX6648, MAX6649, MAX6657, MAX6658, MAX6659, |
| 625 | MAX6680, MAX6681, MAX6692, MAX6695, MAX6696, ON Semiconductor NCT1008, |
| 626 | and Winbond/Nuvoton W83L771W/G/AWG/ASG sensor chips. |
| 627 | |
| 628 | This driver can also be built as a module. If so, the module |
| 629 | will be called lm90. |
| 630 | |
| 631 | config SENSORS_LM92 |
| 632 | tristate "National Semiconductor LM92 and compatibles" |
| 633 | depends on I2C |
| 634 | help |
| 635 | If you say yes here you get support for National Semiconductor LM92 |
| 636 | and Maxim MAX6635 sensor chips. |
| 637 | |
| 638 | This driver can also be built as a module. If so, the module |
| 639 | will be called lm92. |
| 640 | |
| 641 | config SENSORS_LM93 |
| 642 | tristate "National Semiconductor LM93 and compatibles" |
| 643 | depends on I2C |
| 644 | select HWMON_VID |
| 645 | help |
| 646 | If you say yes here you get support for National Semiconductor LM93, |
| 647 | LM94, and compatible sensor chips. |
| 648 | |
| 649 | This driver can also be built as a module. If so, the module |
| 650 | will be called lm93. |
| 651 | |
| 652 | config SENSORS_LTC4151 |
| 653 | tristate "Linear Technology LTC4151" |
| 654 | depends on I2C |
| 655 | default n |
| 656 | help |
| 657 | If you say yes here you get support for Linear Technology LTC4151 |
| 658 | High Voltage I2C Current and Voltage Monitor interface. |
| 659 | |
| 660 | This driver can also be built as a module. If so, the module will |
| 661 | be called ltc4151. |
| 662 | |
| 663 | config SENSORS_LTC4215 |
| 664 | tristate "Linear Technology LTC4215" |
| 665 | depends on I2C && EXPERIMENTAL |
| 666 | default n |
| 667 | help |
| 668 | If you say yes here you get support for Linear Technology LTC4215 |
| 669 | Hot Swap Controller I2C interface. |
| 670 | |
| 671 | This driver can also be built as a module. If so, the module will |
| 672 | be called ltc4215. |
| 673 | |
| 674 | config SENSORS_LTC4245 |
| 675 | tristate "Linear Technology LTC4245" |
| 676 | depends on I2C && EXPERIMENTAL |
| 677 | default n |
| 678 | help |
| 679 | If you say yes here you get support for Linear Technology LTC4245 |
| 680 | Multiple Supply Hot Swap Controller I2C interface. |
| 681 | |
| 682 | This driver can also be built as a module. If so, the module will |
| 683 | be called ltc4245. |
| 684 | |
| 685 | config SENSORS_LTC4261 |
| 686 | tristate "Linear Technology LTC4261" |
| 687 | depends on I2C && EXPERIMENTAL |
| 688 | default n |
| 689 | help |
| 690 | If you say yes here you get support for Linear Technology LTC4261 |
| 691 | Negative Voltage Hot Swap Controller I2C interface. |
| 692 | |
| 693 | This driver can also be built as a module. If so, the module will |
| 694 | be called ltc4261. |
| 695 | |
| 696 | config SENSORS_LM95241 |
| 697 | tristate "National Semiconductor LM95241 sensor chip" |
| 698 | depends on I2C |
| 699 | help |
| 700 | If you say yes here you get support for LM95241 sensor chip. |
| 701 | |
| 702 | This driver can also be built as a module. If so, the module |
| 703 | will be called lm95241. |
| 704 | |
| 705 | config SENSORS_MAX1111 |
| 706 | tristate "Maxim MAX1111 Multichannel, Serial 8-bit ADC chip" |
| 707 | depends on SPI_MASTER |
| 708 | help |
| 709 | Say y here to support Maxim's MAX1111 ADC chips. |
| 710 | |
| 711 | This driver can also be built as a module. If so, the module |
| 712 | will be called max1111. |
| 713 | |
| 714 | config SENSORS_MAX16065 |
| 715 | tristate "Maxim MAX16065 System Manager and compatibles" |
| 716 | depends on I2C |
| 717 | help |
| 718 | If you say yes here you get support for hardware monitoring |
| 719 | capabilities of the following Maxim System Manager chips. |
| 720 | MAX16065 |
| 721 | MAX16066 |
| 722 | MAX16067 |
| 723 | MAX16068 |
| 724 | MAX16070 |
| 725 | MAX16071 |
| 726 | |
| 727 | This driver can also be built as a module. If so, the module |
| 728 | will be called max16065. |
| 729 | |
| 730 | config SENSORS_MAX1619 |
| 731 | tristate "Maxim MAX1619 sensor chip" |
| 732 | depends on I2C |
| 733 | help |
| 734 | If you say yes here you get support for MAX1619 sensor chip. |
| 735 | |
| 736 | This driver can also be built as a module. If so, the module |
| 737 | will be called max1619. |
| 738 | |
| 739 | config SENSORS_MAX6639 |
| 740 | tristate "Maxim MAX6639 sensor chip" |
| 741 | depends on I2C && EXPERIMENTAL |
| 742 | help |
| 743 | If you say yes here you get support for the MAX6639 |
| 744 | sensor chips. |
| 745 | |
| 746 | This driver can also be built as a module. If so, the module |
| 747 | will be called max6639. |
| 748 | |
| 749 | config SENSORS_MAX6642 |
| 750 | tristate "Maxim MAX6642 sensor chip" |
| 751 | depends on I2C && EXPERIMENTAL |
| 752 | help |
| 753 | If you say yes here you get support for MAX6642 sensor chip. |
| 754 | MAX6642 is a SMBus-Compatible Remote/Local Temperature Sensor |
| 755 | with Overtemperature Alarm from Maxim. |
| 756 | |
| 757 | This driver can also be built as a module. If so, the module |
| 758 | will be called max6642. |
| 759 | |
| 760 | config SENSORS_MAX6650 |
| 761 | tristate "Maxim MAX6650 sensor chip" |
| 762 | depends on I2C && EXPERIMENTAL |
| 763 | help |
| 764 | If you say yes here you get support for the MAX6650 / MAX6651 |
| 765 | sensor chips. |
| 766 | |
| 767 | This driver can also be built as a module. If so, the module |
| 768 | will be called max6650. |
| 769 | |
| 770 | config SENSORS_PC87360 |
| 771 | tristate "National Semiconductor PC87360 family" |
| 772 | select HWMON_VID |
| 773 | help |
| 774 | If you say yes here you get access to the hardware monitoring |
| 775 | functions of the National Semiconductor PC8736x Super-I/O chips. |
| 776 | The PC87360, PC87363 and PC87364 only have fan monitoring and |
| 777 | control. The PC87365 and PC87366 additionally have voltage and |
| 778 | temperature monitoring. |
| 779 | |
| 780 | This driver can also be built as a module. If so, the module |
| 781 | will be called pc87360. |
| 782 | |
| 783 | config SENSORS_PC87427 |
| 784 | tristate "National Semiconductor PC87427" |
| 785 | help |
| 786 | If you say yes here you get access to the hardware monitoring |
| 787 | functions of the National Semiconductor PC87427 Super-I/O chip. |
| 788 | The chip has two distinct logical devices, one for fan speed |
| 789 | monitoring and control, and one for voltage and temperature |
| 790 | monitoring. Fan speed monitoring and control are supported, as |
| 791 | well as temperature monitoring. Voltages aren't supported yet. |
| 792 | |
| 793 | This driver can also be built as a module. If so, the module |
| 794 | will be called pc87427. |
| 795 | |
| 796 | config SENSORS_PCF8591 |
| 797 | tristate "Philips PCF8591 ADC/DAC" |
| 798 | depends on I2C |
| 799 | default n |
| 800 | help |
| 801 | If you say yes here you get support for Philips PCF8591 4-channel |
| 802 | ADC, 1-channel DAC chips. |
| 803 | |
| 804 | This driver can also be built as a module. If so, the module |
| 805 | will be called pcf8591. |
| 806 | |
| 807 | These devices are hard to detect and rarely found on mainstream |
| 808 | hardware. If unsure, say N. |
| 809 | |
| 810 | config PMBUS |
| 811 | tristate "PMBus support" |
| 812 | depends on I2C && EXPERIMENTAL |
| 813 | default n |
| 814 | help |
| 815 | Say yes here if you want to enable PMBus support. |
| 816 | |
| 817 | This driver can also be built as a module. If so, the module will |
| 818 | be called pmbus_core. |
| 819 | |
| 820 | if PMBUS |
| 821 | |
| 822 | config SENSORS_PMBUS |
| 823 | tristate "Generic PMBus devices" |
| 824 | default n |
| 825 | help |
| 826 | If you say yes here you get hardware monitoring support for generic |
| 827 | PMBus devices, including but not limited to BMR450, BMR451, BMR453, |
| 828 | BMR454, and LTC2978. |
| 829 | |
| 830 | This driver can also be built as a module. If so, the module will |
| 831 | be called pmbus. |
| 832 | |
| 833 | config SENSORS_ADM1275 |
| 834 | tristate "Analog Devices ADM1275" |
| 835 | default n |
| 836 | help |
| 837 | If you say yes here you get hardware monitoring support for Analog |
| 838 | Devices ADM1275 Hot-Swap Controller and Digital Power Monitor. |
| 839 | |
| 840 | This driver can also be built as a module. If so, the module will |
| 841 | be called adm1275. |
| 842 | |
| 843 | config SENSORS_MAX16064 |
| 844 | tristate "Maxim MAX16064" |
| 845 | default n |
| 846 | help |
| 847 | If you say yes here you get hardware monitoring support for Maxim |
| 848 | MAX16064. |
| 849 | |
| 850 | This driver can also be built as a module. If so, the module will |
| 851 | be called max16064. |
| 852 | |
| 853 | config SENSORS_MAX34440 |
| 854 | tristate "Maxim MAX34440/MAX34441" |
| 855 | default n |
| 856 | help |
| 857 | If you say yes here you get hardware monitoring support for Maxim |
| 858 | MAX34440 and MAX34441. |
| 859 | |
| 860 | This driver can also be built as a module. If so, the module will |
| 861 | be called max34440. |
| 862 | |
| 863 | config SENSORS_MAX8688 |
| 864 | tristate "Maxim MAX8688" |
| 865 | default n |
| 866 | help |
| 867 | If you say yes here you get hardware monitoring support for Maxim |
| 868 | MAX8688. |
| 869 | |
| 870 | This driver can also be built as a module. If so, the module will |
| 871 | be called max8688. |
| 872 | |
| 873 | config SENSORS_UCD9000 |
| 874 | tristate "TI UCD90120, UCD90124, UCD9090, UCD90910" |
| 875 | default n |
| 876 | help |
| 877 | If you say yes here you get hardware monitoring support for TI |
| 878 | UCD90120, UCD90124, UCD9090, UCD90910 Sequencer and System Health |
| 879 | Controllers. |
| 880 | |
| 881 | This driver can also be built as a module. If so, the module will |
| 882 | be called ucd9000. |
| 883 | |
| 884 | config SENSORS_UCD9200 |
| 885 | tristate "TI UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, UCD9248" |
| 886 | default n |
| 887 | help |
| 888 | If you say yes here you get hardware monitoring support for TI |
| 889 | UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, and UCD9248 |
| 890 | Digital PWM System Controllers. |
| 891 | |
| 892 | This driver can also be built as a module. If so, the module will |
| 893 | be called ucd9200. |
| 894 | |
| 895 | endif # PMBUS |
| 896 | |
| 897 | config SENSORS_SHT15 |
| 898 | tristate "Sensiron humidity and temperature sensors. SHT15 and compat." |
| 899 | depends on GENERIC_GPIO |
| 900 | help |
| 901 | If you say yes here you get support for the Sensiron SHT10, SHT11, |
| 902 | SHT15, SHT71, SHT75 humidity and temperature sensors. |
| 903 | |
| 904 | This driver can also be built as a module. If so, the module |
| 905 | will be called sht15. |
| 906 | |
| 907 | config SENSORS_SHT21 |
| 908 | tristate "Sensiron humidity and temperature sensors. SHT21 and compat." |
| 909 | depends on I2C |
| 910 | help |
| 911 | If you say yes here you get support for the Sensiron SHT21, SHT25 |
| 912 | humidity and temperature sensors. |
| 913 | |
| 914 | This driver can also be built as a module. If so, the module |
| 915 | will be called sht21. |
| 916 | |
| 917 | config SENSORS_S3C |
| 918 | tristate "Samsung built-in ADC" |
| 919 | depends on S3C_ADC |
| 920 | help |
| 921 | If you say yes here you get support for the on-board ADCs of |
| 922 | the Samsung S3C24XX, S3C64XX and other series of SoC |
| 923 | |
| 924 | This driver can also be built as a module. If so, the module |
| 925 | will be called s3c-hwmon. |
| 926 | |
| 927 | config SENSORS_S3C_RAW |
| 928 | bool "Include raw channel attributes in sysfs" |
| 929 | depends on SENSORS_S3C |
| 930 | help |
| 931 | Say Y here if you want to include raw copies of all the ADC |
| 932 | channels in sysfs. |
| 933 | |
| 934 | config SENSORS_SIS5595 |
| 935 | tristate "Silicon Integrated Systems Corp. SiS5595" |
| 936 | depends on PCI |
| 937 | help |
| 938 | If you say yes here you get support for the integrated sensors in |
| 939 | SiS5595 South Bridges. |
| 940 | |
| 941 | This driver can also be built as a module. If so, the module |
| 942 | will be called sis5595. |
| 943 | |
| 944 | config SENSORS_SMM665 |
| 945 | tristate "Summit Microelectronics SMM665" |
| 946 | depends on I2C && EXPERIMENTAL |
| 947 | default n |
| 948 | help |
| 949 | If you say yes here you get support for the hardware monitoring |
| 950 | features of the Summit Microelectronics SMM665/SMM665B Six-Channel |
| 951 | Active DC Output Controller / Monitor. |
| 952 | |
| 953 | Other supported chips are SMM465, SMM665C, SMM764, and SMM766. |
| 954 | Support for those chips is untested. |
| 955 | |
| 956 | This driver can also be built as a module. If so, the module will |
| 957 | be called smm665. |
| 958 | |
| 959 | config SENSORS_DME1737 |
| 960 | tristate "SMSC DME1737, SCH311x and compatibles" |
| 961 | depends on I2C && EXPERIMENTAL |
| 962 | select HWMON_VID |
| 963 | help |
| 964 | If you say yes here you get support for the hardware monitoring |
| 965 | and fan control features of the SMSC DME1737, SCH311x, SCH5027, and |
| 966 | Asus A8000 Super-I/O chips. |
| 967 | |
| 968 | This driver can also be built as a module. If so, the module |
| 969 | will be called dme1737. |
| 970 | |
| 971 | config SENSORS_EMC1403 |
| 972 | tristate "SMSC EMC1403/23 thermal sensor" |
| 973 | depends on I2C |
| 974 | help |
| 975 | If you say yes here you get support for the SMSC EMC1403/23 |
| 976 | temperature monitoring chip. |
| 977 | |
| 978 | Threshold values can be configured using sysfs. |
| 979 | Data from the different diodes are accessible via sysfs. |
| 980 | |
| 981 | config SENSORS_EMC2103 |
| 982 | tristate "SMSC EMC2103" |
| 983 | depends on I2C |
| 984 | help |
| 985 | If you say yes here you get support for the temperature |
| 986 | and fan sensors of the SMSC EMC2103 chips. |
| 987 | |
| 988 | This driver can also be built as a module. If so, the module |
| 989 | will be called emc2103. |
| 990 | |
| 991 | config SENSORS_EMC6W201 |
| 992 | tristate "SMSC EMC6W201" |
| 993 | depends on I2C |
| 994 | help |
| 995 | If you say yes here you get support for the SMSC EMC6W201 |
| 996 | hardware monitoring chip. |
| 997 | |
| 998 | This driver can also be built as a module. If so, the module |
| 999 | will be called emc6w201. |
| 1000 | |
| 1001 | config SENSORS_SMSC47M1 |
| 1002 | tristate "SMSC LPC47M10x and compatibles" |
| 1003 | help |
| 1004 | If you say yes here you get support for the integrated fan |
| 1005 | monitoring and control capabilities of the SMSC LPC47B27x, |
| 1006 | LPC47M10x, LPC47M112, LPC47M13x, LPC47M14x, LPC47M15x, |
| 1007 | LPC47M192, LPC47M292 and LPC47M997 chips. |
| 1008 | |
| 1009 | The temperature and voltage sensor features of the LPC47M15x, |
| 1010 | LPC47M192, LPC47M292 and LPC47M997 are supported by another |
| 1011 | driver, select also "SMSC LPC47M192 and compatibles" below for |
| 1012 | those. |
| 1013 | |
| 1014 | This driver can also be built as a module. If so, the module |
| 1015 | will be called smsc47m1. |
| 1016 | |
| 1017 | config SENSORS_SMSC47M192 |
| 1018 | tristate "SMSC LPC47M192 and compatibles" |
| 1019 | depends on I2C |
| 1020 | select HWMON_VID |
| 1021 | help |
| 1022 | If you say yes here you get support for the temperature and |
| 1023 | voltage sensors of the SMSC LPC47M192, LPC47M15x, LPC47M292 |
| 1024 | and LPC47M997 chips. |
| 1025 | |
| 1026 | The fan monitoring and control capabilities of these chips |
| 1027 | are supported by another driver, select |
| 1028 | "SMSC LPC47M10x and compatibles" above. You need both drivers |
| 1029 | if you want fan control and voltage/temperature sensor support. |
| 1030 | |
| 1031 | This driver can also be built as a module. If so, the module |
| 1032 | will be called smsc47m192. |
| 1033 | |
| 1034 | config SENSORS_SMSC47B397 |
| 1035 | tristate "SMSC LPC47B397-NC" |
| 1036 | depends on EXPERIMENTAL |
| 1037 | help |
| 1038 | If you say yes here you get support for the SMSC LPC47B397-NC |
| 1039 | sensor chip. |
| 1040 | |
| 1041 | This driver can also be built as a module. If so, the module |
| 1042 | will be called smsc47b397. |
| 1043 | |
| 1044 | config SENSORS_SCH5627 |
| 1045 | tristate "SMSC SCH5627" |
| 1046 | help |
| 1047 | If you say yes here you get support for the hardware monitoring |
| 1048 | features of the SMSC SCH5627 Super-I/O chip. |
| 1049 | |
| 1050 | This driver can also be built as a module. If so, the module |
| 1051 | will be called sch5627. |
| 1052 | |
| 1053 | config SENSORS_ADS1015 |
| 1054 | tristate "Texas Instruments ADS1015" |
| 1055 | depends on I2C |
| 1056 | help |
| 1057 | If you say yes here you get support for Texas Instruments ADS1015 |
| 1058 | 12-bit 4-input ADC device. |
| 1059 | |
| 1060 | This driver can also be built as a module. If so, the module |
| 1061 | will be called ads1015. |
| 1062 | |
| 1063 | config SENSORS_ADS7828 |
| 1064 | tristate "Texas Instruments ADS7828" |
| 1065 | depends on I2C |
| 1066 | help |
| 1067 | If you say yes here you get support for Texas Instruments ADS7828 |
| 1068 | 12-bit 8-channel ADC device. |
| 1069 | |
| 1070 | This driver can also be built as a module. If so, the module |
| 1071 | will be called ads7828. |
| 1072 | |
| 1073 | config SENSORS_ADS7871 |
| 1074 | tristate "Texas Instruments ADS7871 A/D converter" |
| 1075 | depends on SPI |
| 1076 | help |
| 1077 | If you say yes here you get support for TI ADS7871 & ADS7870 |
| 1078 | |
| 1079 | This driver can also be built as a module. If so, the module |
| 1080 | will be called ads7871. |
| 1081 | |
| 1082 | config SENSORS_AMC6821 |
| 1083 | tristate "Texas Instruments AMC6821" |
| 1084 | depends on I2C && EXPERIMENTAL |
| 1085 | help |
| 1086 | If you say yes here you get support for the Texas Instruments |
| 1087 | AMC6821 hardware monitoring chips. |
| 1088 | |
| 1089 | This driver can also be build as a module. If so, the module |
| 1090 | will be called amc6821. |
| 1091 | |
| 1092 | config SENSORS_THMC50 |
| 1093 | tristate "Texas Instruments THMC50 / Analog Devices ADM1022" |
| 1094 | depends on I2C |
| 1095 | help |
| 1096 | If you say yes here you get support for Texas Instruments THMC50 |
| 1097 | sensor chips and clones: the Analog Devices ADM1022. |
| 1098 | |
| 1099 | This driver can also be built as a module. If so, the module |
| 1100 | will be called thmc50. |
| 1101 | |
| 1102 | config SENSORS_TMP102 |
| 1103 | tristate "Texas Instruments TMP102" |
| 1104 | depends on I2C && EXPERIMENTAL |
| 1105 | help |
| 1106 | If you say yes here you get support for Texas Instruments TMP102 |
| 1107 | sensor chips. |
| 1108 | |
| 1109 | This driver can also be built as a module. If so, the module |
| 1110 | will be called tmp102. |
| 1111 | |
| 1112 | config SENSORS_TMP401 |
| 1113 | tristate "Texas Instruments TMP401 and compatibles" |
| 1114 | depends on I2C && EXPERIMENTAL |
| 1115 | help |
| 1116 | If you say yes here you get support for Texas Instruments TMP401 and |
| 1117 | TMP411 temperature sensor chips. |
| 1118 | |
| 1119 | This driver can also be built as a module. If so, the module |
| 1120 | will be called tmp401. |
| 1121 | |
| 1122 | config SENSORS_TMP421 |
| 1123 | tristate "Texas Instruments TMP421 and compatible" |
| 1124 | depends on I2C && EXPERIMENTAL |
| 1125 | help |
| 1126 | If you say yes here you get support for Texas Instruments TMP421, |
| 1127 | TMP422 and TMP423 temperature sensor chips. |
| 1128 | |
| 1129 | This driver can also be built as a module. If so, the module |
| 1130 | will be called tmp421. |
| 1131 | |
| 1132 | config SENSORS_TWL4030_MADC |
| 1133 | tristate "Texas Instruments TWL4030 MADC Hwmon" |
| 1134 | depends on TWL4030_MADC |
| 1135 | help |
| 1136 | If you say yes here you get hwmon support for triton |
| 1137 | TWL4030-MADC. |
| 1138 | |
| 1139 | This driver can also be built as a module. If so it will be called |
| 1140 | twl4030-madc-hwmon. |
| 1141 | |
| 1142 | config SENSORS_VIA_CPUTEMP |
| 1143 | tristate "VIA CPU temperature sensor" |
| 1144 | depends on X86 |
| 1145 | help |
| 1146 | If you say yes here you get support for the temperature |
| 1147 | sensor inside your CPU. Supported are all known variants of |
| 1148 | the VIA C7 and Nano. |
| 1149 | |
| 1150 | config SENSORS_VIA686A |
| 1151 | tristate "VIA686A" |
| 1152 | depends on PCI |
| 1153 | help |
| 1154 | If you say yes here you get support for the integrated sensors in |
| 1155 | Via 686A/B South Bridges. |
| 1156 | |
| 1157 | This driver can also be built as a module. If so, the module |
| 1158 | will be called via686a. |
| 1159 | |
| 1160 | config SENSORS_VT1211 |
| 1161 | tristate "VIA VT1211" |
| 1162 | select HWMON_VID |
| 1163 | help |
| 1164 | If you say yes here then you get support for hardware monitoring |
| 1165 | features of the VIA VT1211 Super-I/O chip. |
| 1166 | |
| 1167 | This driver can also be built as a module. If so, the module |
| 1168 | will be called vt1211. |
| 1169 | |
| 1170 | config SENSORS_VT8231 |
| 1171 | tristate "VIA VT8231" |
| 1172 | depends on PCI |
| 1173 | select HWMON_VID |
| 1174 | help |
| 1175 | If you say yes here then you get support for the integrated sensors |
| 1176 | in the VIA VT8231 device. |
| 1177 | |
| 1178 | This driver can also be built as a module. If so, the module |
| 1179 | will be called vt8231. |
| 1180 | |
| 1181 | config SENSORS_W83781D |
| 1182 | tristate "Winbond W83781D, W83782D, W83783S, Asus AS99127F" |
| 1183 | depends on I2C |
| 1184 | select HWMON_VID |
| 1185 | help |
| 1186 | If you say yes here you get support for the Winbond W8378x series |
| 1187 | of sensor chips: the W83781D, W83782D and W83783S, and the similar |
| 1188 | Asus AS99127F. |
| 1189 | |
| 1190 | This driver can also be built as a module. If so, the module |
| 1191 | will be called w83781d. |
| 1192 | |
| 1193 | config SENSORS_W83791D |
| 1194 | tristate "Winbond W83791D" |
| 1195 | depends on I2C |
| 1196 | select HWMON_VID |
| 1197 | help |
| 1198 | If you say yes here you get support for the Winbond W83791D chip. |
| 1199 | |
| 1200 | This driver can also be built as a module. If so, the module |
| 1201 | will be called w83791d. |
| 1202 | |
| 1203 | config SENSORS_W83792D |
| 1204 | tristate "Winbond W83792D" |
| 1205 | depends on I2C |
| 1206 | help |
| 1207 | If you say yes here you get support for the Winbond W83792D chip. |
| 1208 | |
| 1209 | This driver can also be built as a module. If so, the module |
| 1210 | will be called w83792d. |
| 1211 | |
| 1212 | config SENSORS_W83793 |
| 1213 | tristate "Winbond W83793" |
| 1214 | depends on I2C && EXPERIMENTAL |
| 1215 | select HWMON_VID |
| 1216 | help |
| 1217 | If you say yes here you get support for the Winbond W83793 |
| 1218 | hardware monitoring chip, including support for the integrated |
| 1219 | watchdog. |
| 1220 | |
| 1221 | This driver can also be built as a module. If so, the module |
| 1222 | will be called w83793. |
| 1223 | |
| 1224 | config SENSORS_W83795 |
| 1225 | tristate "Winbond/Nuvoton W83795G/ADG" |
| 1226 | depends on I2C && EXPERIMENTAL |
| 1227 | help |
| 1228 | If you say yes here you get support for the Winbond W83795G and |
| 1229 | W83795ADG hardware monitoring chip. |
| 1230 | |
| 1231 | This driver can also be built as a module. If so, the module |
| 1232 | will be called w83795. |
| 1233 | |
| 1234 | config SENSORS_W83795_FANCTRL |
| 1235 | boolean "Include fan control support (DANGEROUS)" |
| 1236 | depends on SENSORS_W83795 && EXPERIMENTAL |
| 1237 | default n |
| 1238 | help |
| 1239 | If you say yes here, support for the both manual and automatic |
| 1240 | fan control features will be included in the driver. |
| 1241 | |
| 1242 | This part of the code wasn't carefully reviewed and tested yet, |
| 1243 | so enabling this option is strongly discouraged on production |
| 1244 | servers. Only developers and testers should enable it for the |
| 1245 | time being. |
| 1246 | |
| 1247 | Please also note that this option will create sysfs attribute |
| 1248 | files which may change in the future, so you shouldn't rely |
| 1249 | on them being stable. |
| 1250 | |
| 1251 | config SENSORS_W83L785TS |
| 1252 | tristate "Winbond W83L785TS-S" |
| 1253 | depends on I2C && EXPERIMENTAL |
| 1254 | help |
| 1255 | If you say yes here you get support for the Winbond W83L785TS-S |
| 1256 | sensor chip, which is used on the Asus A7N8X, among other |
| 1257 | motherboards. |
| 1258 | |
| 1259 | This driver can also be built as a module. If so, the module |
| 1260 | will be called w83l785ts. |
| 1261 | |
| 1262 | config SENSORS_W83L786NG |
| 1263 | tristate "Winbond W83L786NG, W83L786NR" |
| 1264 | depends on I2C && EXPERIMENTAL |
| 1265 | help |
| 1266 | If you say yes here you get support for the Winbond W83L786NG |
| 1267 | and W83L786NR sensor chips. |
| 1268 | |
| 1269 | This driver can also be built as a module. If so, the module |
| 1270 | will be called w83l786ng. |
| 1271 | |
| 1272 | config SENSORS_W83627HF |
| 1273 | tristate "Winbond W83627HF, W83627THF, W83637HF, W83687THF, W83697HF" |
| 1274 | select HWMON_VID |
| 1275 | help |
| 1276 | If you say yes here you get support for the Winbond W836X7 series |
| 1277 | of sensor chips: the W83627HF, W83627THF, W83637HF, W83687THF and |
| 1278 | W83697HF. |
| 1279 | |
| 1280 | This driver can also be built as a module. If so, the module |
| 1281 | will be called w83627hf. |
| 1282 | |
| 1283 | config SENSORS_W83627EHF |
| 1284 | tristate "Winbond W83627EHF/EHG/DHG, W83667HG, NCT6775F, NCT6776F" |
| 1285 | select HWMON_VID |
| 1286 | help |
| 1287 | If you say yes here you get support for the hardware |
| 1288 | monitoring functionality of the Winbond W83627EHF Super-I/O chip. |
| 1289 | |
| 1290 | This driver also supports the W83627EHG, which is the lead-free |
| 1291 | version of the W83627EHF, and the W83627DHG, which is a similar |
| 1292 | chip suited for specific Intel processors that use PECI such as |
| 1293 | the Core 2 Duo. |
| 1294 | |
| 1295 | This driver also supports Nuvoton W83667HG, W83667HG-B, NCT6775F |
| 1296 | (also known as W83667HG-I), and NCT6776F. |
| 1297 | |
| 1298 | This driver can also be built as a module. If so, the module |
| 1299 | will be called w83627ehf. |
| 1300 | |
| 1301 | config SENSORS_WM831X |
| 1302 | tristate "WM831x PMICs" |
| 1303 | depends on MFD_WM831X |
| 1304 | help |
| 1305 | If you say yes here you get support for the hardware |
| 1306 | monitoring functionality of the Wolfson Microelectronics |
| 1307 | WM831x series of PMICs. |
| 1308 | |
| 1309 | This driver can also be built as a module. If so, the module |
| 1310 | will be called wm831x-hwmon. |
| 1311 | |
| 1312 | config SENSORS_WM8350 |
| 1313 | tristate "Wolfson Microelectronics WM835x" |
| 1314 | depends on MFD_WM8350 |
| 1315 | help |
| 1316 | If you say yes here you get support for the hardware |
| 1317 | monitoring features of the WM835x series of PMICs. |
| 1318 | |
| 1319 | This driver can also be built as a module. If so, the module |
| 1320 | will be called wm8350-hwmon. |
| 1321 | |
| 1322 | config SENSORS_ULTRA45 |
| 1323 | tristate "Sun Ultra45 PIC16F747" |
| 1324 | depends on SPARC64 |
| 1325 | help |
| 1326 | This driver provides support for the Ultra45 workstation environmental |
| 1327 | sensors. |
| 1328 | |
| 1329 | config SENSORS_APPLESMC |
| 1330 | tristate "Apple SMC (Motion sensor, light sensor, keyboard backlight)" |
| 1331 | depends on INPUT && X86 |
| 1332 | select NEW_LEDS |
| 1333 | select LEDS_CLASS |
| 1334 | select INPUT_POLLDEV |
| 1335 | default n |
| 1336 | help |
| 1337 | This driver provides support for the Apple System Management |
| 1338 | Controller, which provides an accelerometer (Apple Sudden Motion |
| 1339 | Sensor), light sensors, temperature sensors, keyboard backlight |
| 1340 | control and fan control. |
| 1341 | |
| 1342 | Only Intel-based Apple's computers are supported (MacBook Pro, |
| 1343 | MacBook, MacMini). |
| 1344 | |
| 1345 | Data from the different sensors, keyboard backlight control and fan |
| 1346 | control are accessible via sysfs. |
| 1347 | |
| 1348 | This driver also provides an absolute input class device, allowing |
| 1349 | the laptop to act as a pinball machine-esque joystick. |
| 1350 | |
| 1351 | Say Y here if you have an applicable laptop and want to experience |
| 1352 | the awesome power of applesmc. |
| 1353 | |
| 1354 | config SENSORS_MC13783_ADC |
| 1355 | tristate "Freescale MC13783 ADC" |
| 1356 | depends on MFD_MC13783 |
| 1357 | help |
| 1358 | Support for the A/D converter on MC13783 PMIC. |
| 1359 | |
| 1360 | if ACPI |
| 1361 | |
| 1362 | comment "ACPI drivers" |
| 1363 | |
| 1364 | config SENSORS_ACPI_POWER |
| 1365 | tristate "ACPI 4.0 power meter" |
| 1366 | help |
| 1367 | This driver exposes ACPI 4.0 power meters as hardware monitoring |
| 1368 | devices. Say Y (or M) if you have a computer with ACPI 4.0 firmware |
| 1369 | and a power meter. |
| 1370 | |
| 1371 | To compile this driver as a module, choose M here: |
| 1372 | the module will be called acpi_power_meter. |
| 1373 | |
| 1374 | config SENSORS_ATK0110 |
| 1375 | tristate "ASUS ATK0110" |
| 1376 | depends on X86 && EXPERIMENTAL |
| 1377 | help |
| 1378 | If you say yes here you get support for the ACPI hardware |
| 1379 | monitoring interface found in many ASUS motherboards. This |
| 1380 | driver will provide readings of fans, voltages and temperatures |
| 1381 | through the system firmware. |
| 1382 | |
| 1383 | This driver can also be built as a module. If so, the module |
| 1384 | will be called asus_atk0110. |
| 1385 | |
| 1386 | endif # ACPI |
| 1387 | |
| 1388 | endif # HWMON |