| | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| | 2 | # |
| | 3 | # PMBus chip drivers configuration |
| | 4 | # |
| | 5 | |
| | 6 | menuconfig PMBUS |
| | 7 | tristate "PMBus support" |
| | 8 | depends on I2C |
| | 9 | help |
| | 10 | Say yes here if you want to enable PMBus support. |
| | 11 | |
| | 12 | This driver can also be built as a module. If so, the module will |
| | 13 | be called pmbus_core. |
| | 14 | |
| | 15 | if PMBUS |
| | 16 | |
| | 17 | config SENSORS_PMBUS |
| | 18 | tristate "Generic PMBus devices" |
| | 19 | default y |
| | 20 | help |
| | 21 | If you say yes here you get hardware monitoring support for generic |
| | 22 | PMBus devices, including but not limited to ADP4000, BMR310, BMR453, |
| | 23 | BMR454, BMR456, BMR457, BMR458, BMR480, BMR490, BMR491, BMR492, |
| | 24 | MAX20796, MDT040, NCP4200, NCP4208, PDT003, PDT006, PDT012, |
| | 25 | TPS40400, TPS544B20, TPS544B25, TPS544C20, TPS544C25, and UDT020. |
| | 26 | |
| | 27 | This driver can also be built as a module. If so, the module will |
| | 28 | be called pmbus. |
| | 29 | |
| | 30 | config SENSORS_ACBEL_FSG032 |
| | 31 | tristate "ACBEL FSG032 Power Supply" |
| | 32 | help |
| | 33 | If you say yes here you get hardware monitoring support for the ACBEL |
| | 34 | FSG032 Power Supply. |
| | 35 | |
| | 36 | This driver can also be built as a module. If so, the module will |
| | 37 | be called acbel-fsg032. |
| | 38 | |
| | 39 | config SENSORS_ADM1266 |
| | 40 | tristate "Analog Devices ADM1266 Sequencer" |
| | 41 | select CRC8 |
| | 42 | depends on GPIOLIB |
| | 43 | help |
| | 44 | If you say yes here you get hardware monitoring support for Analog |
| | 45 | Devices ADM1266 Cascadable Super Sequencer. |
| | 46 | |
| | 47 | This driver can also be built as a module. If so, the module will |
| | 48 | be called adm1266. |
| | 49 | |
| | 50 | config SENSORS_ADM1275 |
| | 51 | tristate "Analog Devices ADM1275 and compatibles" |
| | 52 | help |
| | 53 | If you say yes here you get hardware monitoring support for Analog |
| | 54 | Devices ADM1075, ADM1272, ADM1273, ADM1275, ADM1276, ADM1278, ADM1281, |
| | 55 | ADM1293, and ADM1294 Hot-Swap Controller and Digital Power Monitors. |
| | 56 | |
| | 57 | This driver can also be built as a module. If so, the module will |
| | 58 | be called adm1275. |
| | 59 | |
| | 60 | config SENSORS_ADP1050 |
| | 61 | tristate "Analog Devices ADP1050 digital controller for Power Supplies" |
| | 62 | help |
| | 63 | If you say yes here you get hardware monitoring support for Analog |
| | 64 | Devices ADP1050 digital controller for isolated power supply with |
| | 65 | PMBus interface. |
| | 66 | |
| | 67 | This driver can also be built as a module. If so, the module will |
| | 68 | be called adp1050. |
| | 69 | |
| | 70 | config SENSORS_BEL_PFE |
| | 71 | tristate "Bel PFE Compatible Power Supplies" |
| | 72 | help |
| | 73 | If you say yes here you get hardware monitoring support for BEL |
| | 74 | PFE1100 and PFE3000 Power Supplies. |
| | 75 | |
| | 76 | This driver can also be built as a module. If so, the module will |
| | 77 | be called bel-pfe. |
| | 78 | |
| | 79 | config SENSORS_BPA_RS600 |
| | 80 | tristate "BluTek BPA-RS600 Power Supplies" |
| | 81 | help |
| | 82 | If you say yes here you get hardware monitoring support for BluTek |
| | 83 | BPA-RS600 Power Supplies. |
| | 84 | |
| | 85 | This driver can also be built as a module. If so, the module will |
| | 86 | be called bpa-rs600. |
| | 87 | |
| | 88 | config SENSORS_CRPS |
| | 89 | tristate "Intel Common Redundant Power Supply" |
| | 90 | help |
| | 91 | If you say yes here you get hardware monitoring support for the Intel |
| | 92 | Common Redundant Power Supply. |
| | 93 | |
| | 94 | This driver can also be built as a module. If so, the module will |
| | 95 | be called crps. |
| | 96 | |
| | 97 | config SENSORS_DELTA_AHE50DC_FAN |
| | 98 | tristate "Delta AHE-50DC fan control module" |
| | 99 | help |
| | 100 | If you say yes here you get hardware monitoring support for |
| | 101 | the integrated fan control module of the Delta AHE-50DC |
| | 102 | Open19 power shelf. |
| | 103 | |
| | 104 | This driver can also be built as a module. If so, the module |
| | 105 | will be called delta-ahe50dc-fan. |
| | 106 | |
| | 107 | config SENSORS_FSP_3Y |
| | 108 | tristate "FSP/3Y-Power power supplies" |
| | 109 | help |
| | 110 | If you say yes here you get hardware monitoring support for |
| | 111 | FSP/3Y-Power hot-swap power supplies. |
| | 112 | Supported models: YH-5151E, YM-2151E |
| | 113 | |
| | 114 | This driver can also be built as a module. If so, the module will |
| | 115 | be called fsp-3y. |
| | 116 | |
| | 117 | config SENSORS_IBM_CFFPS |
| | 118 | tristate "IBM Common Form Factor Power Supply" |
| | 119 | depends on LEDS_CLASS |
| | 120 | help |
| | 121 | If you say yes here you get hardware monitoring support for the IBM |
| | 122 | Common Form Factor power supply. |
| | 123 | |
| | 124 | This driver can also be built as a module. If so, the module will |
| | 125 | be called ibm-cffps. |
| | 126 | |
| | 127 | config SENSORS_DPS920AB |
| | 128 | tristate "Delta DPS920AB Power Supply" |
| | 129 | help |
| | 130 | If you say yes here you get hardware monitoring support for Delta |
| | 131 | DPS920AB Power Supplies. |
| | 132 | |
| | 133 | This driver can also be built as a module. If so, the module will |
| | 134 | be called dps920ab. |
| | 135 | |
| | 136 | config SENSORS_INA233 |
| | 137 | tristate "Texas Instruments INA233 and compatibles" |
| | 138 | help |
| | 139 | If you say yes here you get hardware monitoring support for Texas |
| | 140 | Instruments INA233. |
| | 141 | |
| | 142 | This driver can also be built as a module. If so, the module will |
| | 143 | be called ina233. |
| | 144 | |
| | 145 | config SENSORS_INSPUR_IPSPS |
| | 146 | tristate "INSPUR Power System Power Supply" |
| | 147 | help |
| | 148 | If you say yes here you get hardware monitoring support for the INSPUR |
| | 149 | Power System power supply. |
| | 150 | |
| | 151 | This driver can also be built as a module. If so, the module will |
| | 152 | be called inspur-ipsps. |
| | 153 | |
| | 154 | config SENSORS_IR35221 |
| | 155 | tristate "Infineon IR35221" |
| | 156 | help |
| | 157 | If you say yes here you get hardware monitoring support for the |
| | 158 | Infineon IR35221 controller. |
| | 159 | |
| | 160 | This driver can also be built as a module. If so, the module will |
| | 161 | be called ir35221. |
| | 162 | |
| | 163 | config SENSORS_IR36021 |
| | 164 | tristate "Infineon IR36021" |
| | 165 | help |
| | 166 | If you say yes here you get hardware monitoring support for Infineon |
| | 167 | IR36021. |
| | 168 | |
| | 169 | This driver can also be built as a module. If so, the module will |
| | 170 | be called ir36021. |
| | 171 | |
| | 172 | config SENSORS_IR38064 |
| | 173 | tristate "Infineon IR38064 and compatibles" |
| | 174 | help |
| | 175 | If you say yes here you get hardware monitoring support for Infineon |
| | 176 | IR38060, IR38064, IR38164 and IR38263. |
| | 177 | |
| | 178 | This driver can also be built as a module. If so, the module will |
| | 179 | be called ir38064. |
| | 180 | |
| | 181 | config SENSORS_IR38064_REGULATOR |
| | 182 | bool "Regulator support for IR38064 and compatibles" |
| | 183 | depends on SENSORS_IR38064 && REGULATOR |
| | 184 | help |
| | 185 | Uses the IR38064 or compatible as regulator. |
| | 186 | |
| | 187 | config SENSORS_IRPS5401 |
| | 188 | tristate "Infineon IRPS5401" |
| | 189 | help |
| | 190 | If you say yes here you get hardware monitoring support for the |
| | 191 | Infineon IRPS5401 controller. |
| | 192 | |
| | 193 | This driver can also be built as a module. If so, the module will |
| | 194 | be called irps5401. |
| | 195 | |
| | 196 | config SENSORS_ISL68137 |
| | 197 | tristate "Renesas Digital Multiphase Voltage Regulators" |
| | 198 | help |
| | 199 | If you say yes here you get hardware monitoring support for Renesas |
| | 200 | digital multiphase voltage regulators. |
| | 201 | |
| | 202 | This driver can also be built as a module. If so, the module will |
| | 203 | be called isl68137. |
| | 204 | |
| | 205 | config SENSORS_LM25066 |
| | 206 | tristate "National Semiconductor LM25066 and compatibles" |
| | 207 | help |
| | 208 | If you say yes here you get hardware monitoring support for National |
| | 209 | Semiconductor LM25056, LM25066, LM5064, and LM5066. |
| | 210 | |
| | 211 | This driver can also be built as a module. If so, the module will |
| | 212 | be called lm25066. |
| | 213 | |
| | 214 | config SENSORS_LM25066_REGULATOR |
| | 215 | bool "Regulator support for LM25066 and compatibles" |
| | 216 | depends on SENSORS_LM25066 && REGULATOR |
| | 217 | help |
| | 218 | If you say yes here you get regulator support for National |
| | 219 | Semiconductor LM25066, LM5064, and LM5066. |
| | 220 | |
| | 221 | config SENSORS_LT3074 |
| | 222 | tristate "Analog Devices LT3074" |
| | 223 | help |
| | 224 | If you say yes here you get hardware monitoring support for Analog |
| | 225 | Devices LT3074. |
| | 226 | |
| | 227 | This driver can also be built as a module. If so, the module will |
| | 228 | be called lt3074. |
| | 229 | |
| | 230 | config SENSORS_LT3074_REGULATOR |
| | 231 | tristate "Regulator support for LT3074" |
| | 232 | depends on SENSORS_LT3074 && REGULATOR |
| | 233 | help |
| | 234 | If you say yes here you get regulator support for Analog Devices |
| | 235 | LT3074. The LT3074 is a low voltage, ultralow noise, high PSRR, |
| | 236 | dropout linear regulator. The device supplies up to 3A with a |
| | 237 | typical dropout voltage of 45mV. |
| | 238 | |
| | 239 | config SENSORS_LT7182S |
| | 240 | tristate "Analog Devices LT7182S" |
| | 241 | help |
| | 242 | If you say yes here you get hardware monitoring support for Analog |
| | 243 | Devices LT7182S. |
| | 244 | |
| | 245 | This driver can also be built as a module. If so, the module will |
| | 246 | be called lt7182s. |
| | 247 | |
| | 248 | config SENSORS_LTC2978 |
| | 249 | tristate "Linear Technologies LTC2978 and compatibles" |
| | 250 | help |
| | 251 | If you say yes here you get hardware monitoring support for Linear |
| | 252 | Technology LTC2972, LTC2974, LTC2975, LTC2977, LTC2978, LTC2979, |
| | 253 | LTC2980, and LTM2987. |
| | 254 | |
| | 255 | This driver can also be built as a module. If so, the module will |
| | 256 | be called ltc2978. |
| | 257 | |
| | 258 | config SENSORS_LTC2978_REGULATOR |
| | 259 | bool "Regulator support for LTC2978 and compatibles" |
| | 260 | depends on SENSORS_LTC2978 && REGULATOR |
| | 261 | help |
| | 262 | If you say yes here you get regulator support for Linear Technology |
| | 263 | LT7170, LT7171, LTC3880, LTC3883, LTC3884, LTC3886, LTC3887, LTC3889, |
| | 264 | LTC7841, LTC7880, LTM4644, LTM4673, LTM4675, LTM4676, LTM4677, |
| | 265 | LTM4678, LTM4680, LTM4686, and LTM4700. |
| | 266 | |
| | 267 | config SENSORS_LTC3815 |
| | 268 | tristate "Linear Technologies LTC3815" |
| | 269 | help |
| | 270 | If you say yes here you get hardware monitoring support for Linear |
| | 271 | Technology LTC3815. |
| | 272 | |
| | 273 | This driver can also be built as a module. If so, the module will |
| | 274 | be called ltc3815. |
| | 275 | |
| | 276 | config SENSORS_LTC4286 |
| | 277 | bool "Analog Devices LTC4286" |
| | 278 | help |
| | 279 | LTC4286 is an integrated solution for hot swap applications that |
| | 280 | allows a board to be safely inserted and removed from a live |
| | 281 | backplane. |
| | 282 | This chip could be used to monitor voltage, current, ...etc. |
| | 283 | If you say yes here you get hardware monitoring support for Analog |
| | 284 | Devices LTC4286. |
| | 285 | |
| | 286 | config SENSORS_MAX15301 |
| | 287 | tristate "Maxim MAX15301" |
| | 288 | help |
| | 289 | If you say yes here you get hardware monitoring support for Maxim |
| | 290 | MAX15301, MAX15303, as well as for Flex BMR461. |
| | 291 | |
| | 292 | This driver can also be built as a module. If so, the module will |
| | 293 | be called max15301. |
| | 294 | |
| | 295 | config SENSORS_MAX16064 |
| | 296 | tristate "Maxim MAX16064" |
| | 297 | help |
| | 298 | If you say yes here you get hardware monitoring support for Maxim |
| | 299 | MAX16064. |
| | 300 | |
| | 301 | This driver can also be built as a module. If so, the module will |
| | 302 | be called max16064. |
| | 303 | |
| | 304 | config SENSORS_MAX16601 |
| | 305 | tristate "Maxim MAX16508, MAX16600, MAX16601, and MAX16602" |
| | 306 | help |
| | 307 | If you say yes here you get hardware monitoring support for Maxim |
| | 308 | MAX16508, MAX16600, MAX16601, and MAX16602. |
| | 309 | |
| | 310 | This driver can also be built as a module. If so, the module will |
| | 311 | be called max16601. |
| | 312 | |
| | 313 | config SENSORS_MAX20730 |
| | 314 | tristate "Maxim MAX20710, MAX20730, MAX20734, MAX20743" |
| | 315 | help |
| | 316 | If you say yes here you get hardware monitoring support for Maxim |
| | 317 | MAX20710, MAX20730, MAX20734, and MAX20743. |
| | 318 | |
| | 319 | This driver can also be built as a module. If so, the module will |
| | 320 | be called max20730. |
| | 321 | |
| | 322 | config SENSORS_MAX20751 |
| | 323 | tristate "Maxim MAX20751" |
| | 324 | help |
| | 325 | If you say yes here you get hardware monitoring support for Maxim |
| | 326 | MAX20751. |
| | 327 | |
| | 328 | This driver can also be built as a module. If so, the module will |
| | 329 | be called max20751. |
| | 330 | |
| | 331 | config SENSORS_MAX31785 |
| | 332 | tristate "Maxim MAX31785 and compatibles" |
| | 333 | help |
| | 334 | If you say yes here you get hardware monitoring support for Maxim |
| | 335 | MAX31785. |
| | 336 | |
| | 337 | This driver can also be built as a module. If so, the module will |
| | 338 | be called max31785. |
| | 339 | |
| | 340 | config SENSORS_MAX34440 |
| | 341 | tristate "Maxim MAX34440 and compatibles" |
| | 342 | help |
| | 343 | If you say yes here you get hardware monitoring support for Maxim |
| | 344 | MAX34440, MAX34441, MAX34446, MAX34451, MAX34460, and MAX34461. |
| | 345 | |
| | 346 | This driver can also be built as a module. If so, the module will |
| | 347 | be called max34440. |
| | 348 | |
| | 349 | config SENSORS_MAX8688 |
| | 350 | tristate "Maxim MAX8688" |
| | 351 | help |
| | 352 | If you say yes here you get hardware monitoring support for Maxim |
| | 353 | MAX8688. |
| | 354 | |
| | 355 | This driver can also be built as a module. If so, the module will |
| | 356 | be called max8688. |
| | 357 | |
| | 358 | config SENSORS_MP2856 |
| | 359 | tristate "MPS MP2856" |
| | 360 | help |
| | 361 | If you say yes here you get hardware monitoring support for MPS |
| | 362 | MP2856 MP2857 Dual Loop Digital Multi-Phase Controller. |
| | 363 | |
| | 364 | This driver can also be built as a module. If so, the module will |
| | 365 | be called mp2856. |
| | 366 | |
| | 367 | config SENSORS_MP2888 |
| | 368 | tristate "MPS MP2888" |
| | 369 | help |
| | 370 | If you say yes here you get hardware monitoring support for MPS |
| | 371 | MP2888 Digital, Multi-Phase, Pulse-Width Modulation Controller. |
| | 372 | |
| | 373 | This driver can also be built as a module. If so, the module will |
| | 374 | be called mp2888. |
| | 375 | |
| | 376 | config SENSORS_MP2891 |
| | 377 | tristate "MPS MP2891" |
| | 378 | help |
| | 379 | If you say yes here you get hardware monitoring support for MPS |
| | 380 | MP2891 Dual Loop Digital Multi-Phase Controller. |
| | 381 | |
| | 382 | This driver can also be built as a module. If so, the module will |
| | 383 | be called mp2891. |
| | 384 | |
| | 385 | config SENSORS_MP2975 |
| | 386 | tristate "MPS MP2975" |
| | 387 | help |
| | 388 | If you say yes here you get hardware monitoring support for MPS |
| | 389 | MP2975 Dual Loop Digital Multi-Phase Controller. |
| | 390 | |
| | 391 | This driver can also be built as a module. If so, the module will |
| | 392 | be called mp2975. |
| | 393 | |
| | 394 | config SENSORS_MP2993 |
| | 395 | tristate "MPS MP2993" |
| | 396 | help |
| | 397 | If you say yes here you get hardware monitoring support for MPS |
| | 398 | MP2993 Dual Loop Digital Multi-Phase Controller. |
| | 399 | |
| | 400 | This driver can also be built as a module. If so, the module will |
| | 401 | be called mp2993. |
| | 402 | |
| | 403 | config SENSORS_MP2975_REGULATOR |
| | 404 | depends on SENSORS_MP2975 && REGULATOR |
| | 405 | bool "Regulator support for MPS MP2975" |
| | 406 | help |
| | 407 | If you say yes here you get regulator support for MPS MP2975 |
| | 408 | Dual Loop Digital Multi-Phase Controller. |
| | 409 | |
| | 410 | config SENSORS_MP5023 |
| | 411 | tristate "MPS MP5023" |
| | 412 | help |
| | 413 | If you say yes here you get hardware monitoring support for MPS |
| | 414 | MP5023. |
| | 415 | |
| | 416 | This driver can also be built as a module. If so, the module will |
| | 417 | be called mp5023. |
| | 418 | |
| | 419 | config SENSORS_MP5920 |
| | 420 | tristate "MPS MP5920" |
| | 421 | help |
| | 422 | If you say yes here you get hardware monitoring support for Monolithic |
| | 423 | MP5920. |
| | 424 | |
| | 425 | This driver can also be built as a module. If so, the module will |
| | 426 | be called mp5920. |
| | 427 | |
| | 428 | config SENSORS_MP5990 |
| | 429 | tristate "MPS MP5990" |
| | 430 | help |
| | 431 | If you say yes here you get hardware monitoring support for MPS |
| | 432 | MP5990. |
| | 433 | |
| | 434 | This driver can also be built as a module. If so, the module will |
| | 435 | be called mp5990. |
| | 436 | |
| | 437 | config SENSORS_MP9941 |
| | 438 | tristate "MPS MP9941" |
| | 439 | help |
| | 440 | If you say yes here you get hardware monitoring support for MPS |
| | 441 | MP9941. |
| | 442 | |
| | 443 | This driver can also be built as a module. If so, the module will |
| | 444 | be called mp9941. |
| | 445 | |
| | 446 | config SENSORS_MPQ7932_REGULATOR |
| | 447 | bool "Regulator support for MPQ7932" |
| | 448 | depends on SENSORS_MPQ7932 && REGULATOR |
| | 449 | help |
| | 450 | If you say yes here you get six integrated buck converter regulator |
| | 451 | support for power management IC MPS MPQ7932. |
| | 452 | |
| | 453 | config SENSORS_MPQ7932 |
| | 454 | tristate "MPS MPQ7932" |
| | 455 | help |
| | 456 | If you say yes here you get hardware monitoring functionality support |
| | 457 | for power management IC MPS MPQ7932. |
| | 458 | |
| | 459 | This driver can also be built as a module. If so, the module will |
| | 460 | be called mpq7932. |
| | 461 | |
| | 462 | config SENSORS_MPQ8785 |
| | 463 | tristate "MPS MPQ8785" |
| | 464 | help |
| | 465 | If you say yes here you get hardware monitoring functionality support |
| | 466 | for power management IC MPS MPQ8785. |
| | 467 | |
| | 468 | This driver can also be built as a module. If so, the module will |
| | 469 | be called mpq8785. |
| | 470 | |
| | 471 | config SENSORS_PIM4328 |
| | 472 | tristate "Flex PIM4328 and compatibles" |
| | 473 | help |
| | 474 | If you say yes here you get hardware monitoring support for Flex |
| | 475 | PIM4328, PIM4820 and PIM4006 Power Interface Modules. |
| | 476 | |
| | 477 | This driver can also be built as a module. If so, the module will |
| | 478 | be called pim4328. |
| | 479 | |
| | 480 | config SENSORS_PLI1209BC |
| | 481 | tristate "Vicor PLI1209BC" |
| | 482 | help |
| | 483 | If you say yes here you get hardware monitoring support for Vicor |
| | 484 | PLI1209BC Digital Supervisor. |
| | 485 | |
| | 486 | This driver can also be built as a module. If so, the module will |
| | 487 | be called pli1209bc. |
| | 488 | |
| | 489 | config SENSORS_PLI1209BC_REGULATOR |
| | 490 | bool "Regulator support for PLI1209BC" |
| | 491 | depends on SENSORS_PLI1209BC && REGULATOR |
| | 492 | help |
| | 493 | If you say yes here you get regulator support for Vicor PLI1209BC |
| | 494 | Digital Supervisor. |
| | 495 | |
| | 496 | config SENSORS_PM6764TR |
| | 497 | tristate "ST PM6764TR" |
| | 498 | help |
| | 499 | If you say yes here you get hardware monitoring support for ST |
| | 500 | PM6764TR. |
| | 501 | |
| | 502 | This driver can also be built as a module. If so, the module will |
| | 503 | be called pm6764tr. |
| | 504 | |
| | 505 | config SENSORS_PXE1610 |
| | 506 | tristate "Infineon PXE1610" |
| | 507 | help |
| | 508 | If you say yes here you get hardware monitoring support for Infineon |
| | 509 | PXE1610. |
| | 510 | |
| | 511 | This driver can also be built as a module. If so, the module will |
| | 512 | be called pxe1610. |
| | 513 | |
| | 514 | config SENSORS_Q54SJ108A2 |
| | 515 | tristate "Delta Power Supplies Q54SJ108A2" |
| | 516 | help |
| | 517 | If you say yes here you get hardware monitoring support for Delta |
| | 518 | Q54SJ108A2 series Power Supplies. |
| | 519 | |
| | 520 | This driver can also be built as a module. If so, the module will |
| | 521 | be called q54sj108a2. |
| | 522 | |
| | 523 | config SENSORS_STPDDC60 |
| | 524 | tristate "ST STPDDC60" |
| | 525 | help |
| | 526 | If you say yes here you get hardware monitoring support for ST |
| | 527 | STPDDC60 Universal Digital Multicell Controller, as well as for |
| | 528 | Flex BMR481. |
| | 529 | |
| | 530 | This driver can also be built as a module. If so, the module will |
| | 531 | be called stpddc60. |
| | 532 | |
| | 533 | config SENSORS_TDA38640 |
| | 534 | tristate "Infineon TDA38640" |
| | 535 | help |
| | 536 | If you say yes here you get hardware monitoring support for Infineon |
| | 537 | TDA38640. |
| | 538 | |
| | 539 | This driver can also be built as a module. If so, the module will |
| | 540 | be called tda38640. |
| | 541 | |
| | 542 | config SENSORS_TDA38640_REGULATOR |
| | 543 | bool "Regulator support for TDA38640 and compatibles" |
| | 544 | depends on SENSORS_TDA38640 && REGULATOR |
| | 545 | help |
| | 546 | If you say yes here you get regulator support for Infineon |
| | 547 | TDA38640 as regulator. |
| | 548 | |
| | 549 | config SENSORS_TPS25990 |
| | 550 | tristate "TI TPS25990" |
| | 551 | help |
| | 552 | If you say yes here you get hardware monitoring support for TI |
| | 553 | TPS25990. |
| | 554 | |
| | 555 | This driver can also be built as a module. If so, the module will |
| | 556 | be called tps25990. |
| | 557 | |
| | 558 | config SENSORS_TPS25990_REGULATOR |
| | 559 | bool "Regulator support for TPS25990 and compatibles" |
| | 560 | depends on SENSORS_TPS25990 && REGULATOR |
| | 561 | default SENSORS_TPS25990 |
| | 562 | help |
| | 563 | If you say yes here you get regulator support for Texas Instruments |
| | 564 | TPS25990. |
| | 565 | |
| | 566 | config SENSORS_TPS40422 |
| | 567 | tristate "TI TPS40422" |
| | 568 | help |
| | 569 | If you say yes here you get hardware monitoring support for TI |
| | 570 | TPS40422. |
| | 571 | |
| | 572 | This driver can also be built as a module. If so, the module will |
| | 573 | be called tps40422. |
| | 574 | |
| | 575 | config SENSORS_TPS53679 |
| | 576 | tristate "TI TPS53647, TPS53667, TPS53676, TPS53679, TPS53681, TPS53688" |
| | 577 | help |
| | 578 | If you say yes here you get hardware monitoring support for TI |
| | 579 | TPS53647, TPS53667, TPS53676, TPS53679, TPS53681, and TPS53688. |
| | 580 | |
| | 581 | This driver can also be built as a module. If so, the module will |
| | 582 | be called tps53679. |
| | 583 | |
| | 584 | config SENSORS_TPS546D24 |
| | 585 | tristate "TPS546D24" |
| | 586 | help |
| | 587 | If you say yes here you get hardware monitoring support for TEXAS |
| | 588 | TPS546D24. |
| | 589 | |
| | 590 | This driver can also be built as a module. If so, the module will |
| | 591 | be called tps546d24 |
| | 592 | |
| | 593 | config SENSORS_UCD9000 |
| | 594 | tristate "TI UCD90120, UCD90124, UCD90160, UCD90320, UCD9090, UCD90910" |
| | 595 | help |
| | 596 | If you say yes here you get hardware monitoring support for TI |
| | 597 | UCD90120, UCD90124, UCD90160, UCD90320, UCD9090, UCD90910, Sequencer |
| | 598 | and System Health Controllers. |
| | 599 | |
| | 600 | This driver can also be built as a module. If so, the module will |
| | 601 | be called ucd9000. |
| | 602 | |
| | 603 | config SENSORS_UCD9200 |
| | 604 | tristate "TI UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, UCD9248" |
| | 605 | help |
| | 606 | If you say yes here you get hardware monitoring support for TI |
| | 607 | UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, and UCD9248 |
| | 608 | Digital PWM System Controllers. |
| | 609 | |
| | 610 | This driver can also be built as a module. If so, the module will |
| | 611 | be called ucd9200. |
| | 612 | |
| | 613 | config SENSORS_XDP710 |
| | 614 | tristate "Infineon XDP710 family" |
| | 615 | help |
| | 616 | If you say yes here you get hardware monitoring support for Infineon |
| | 617 | XDP710. |
| | 618 | |
| | 619 | This driver can also be built as a module. If so, the module will |
| | 620 | be called xdp710. |
| | 621 | |
| | 622 | config SENSORS_XDPE152 |
| | 623 | tristate "Infineon XDPE152 family" |
| | 624 | help |
| | 625 | If you say yes here you get hardware monitoring support for Infineon |
| | 626 | XDPE15284, XDPE152C4, device. |
| | 627 | |
| | 628 | This driver can also be built as a module. If so, the module will |
| | 629 | be called xdpe152c4. |
| | 630 | |
| | 631 | config SENSORS_XDPE122 |
| | 632 | tristate "Infineon XDPE122 family" |
| | 633 | help |
| | 634 | If you say yes here you get hardware monitoring support for Infineon |
| | 635 | XDPE12254, XDPE12284, device. |
| | 636 | |
| | 637 | This driver can also be built as a module. If so, the module will |
| | 638 | be called xdpe12284. |
| | 639 | |
| | 640 | config SENSORS_XDPE122_REGULATOR |
| | 641 | bool "Regulator support for XDPE122 and compatibles" |
| | 642 | depends on SENSORS_XDPE122 && REGULATOR |
| | 643 | help |
| | 644 | Uses the xdpe12284 or compatible as regulator. |
| | 645 | |
| | 646 | config SENSORS_ZL6100 |
| | 647 | tristate "Intersil ZL6100 and compatibles" |
| | 648 | help |
| | 649 | If you say yes here you get hardware monitoring support for Intersil |
| | 650 | ZL2004, ZL2005, ZL2006, ZL2008, ZL2105, ZL2106, ZL6100, ZL6105, |
| | 651 | ZL9101M, and ZL9117M Digital DC/DC Controllers, as well as for |
| | 652 | Ericsson BMR450, BMR451, BMR462, BMR463, and BMR464. |
| | 653 | |
| | 654 | This driver can also be built as a module. If so, the module will |
| | 655 | be called zl6100. |
| | 656 | |
| | 657 | endif # PMBUS |
projects / linux-2.6-block.git / blame_incremental