| Guenter Roeck | 9d2ecfb | 2011-07-12 07:15:19 -0700 | [diff] [blame] | 1 | # |
| 2 | # PMBus chip drivers configuration |
| 3 | # |
| 4 | |
| 5 | menuconfig PMBUS |
| 6 | tristate "PMBus support" |
| 7 | depends on I2C && EXPERIMENTAL |
| 8 | default n |
| 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 |
| Guenter Roeck | e0455e3 | 2011-06-25 15:13:44 -0700 | [diff] [blame] | 22 | PMBus devices, including but not limited to ADP4000, BMR450, BMR451, |
| 23 | BMR453, BMR454, LTC2978, NCP4200, and NCP4208. |
| Guenter Roeck | 9d2ecfb | 2011-07-12 07:15:19 -0700 | [diff] [blame] | 24 | |
| 25 | This driver can also be built as a module. If so, the module will |
| 26 | be called pmbus. |
| 27 | |
| 28 | config SENSORS_ADM1275 |
| 29 | tristate "Analog Devices ADM1275" |
| 30 | default n |
| 31 | help |
| 32 | If you say yes here you get hardware monitoring support for Analog |
| 33 | Devices ADM1275 Hot-Swap Controller and Digital Power Monitor. |
| 34 | |
| 35 | This driver can also be built as a module. If so, the module will |
| 36 | be called adm1275. |
| 37 | |
| Guenter Roeck | 03e9bd8 | 2011-07-08 10:43:57 -0700 | [diff] [blame^] | 38 | config SENSORS_LM25066 |
| 39 | tristate "National Semiconductor LM25066 and compatibles" |
| 40 | default n |
| 41 | help |
| 42 | If you say yes here you get hardware monitoring support for National |
| 43 | Semiconductor LM25066, LM5064, and LM5066. |
| 44 | |
| 45 | This driver can also be built as a module. If so, the module will |
| 46 | be called lm25066. |
| 47 | |
| Guenter Roeck | 9d2ecfb | 2011-07-12 07:15:19 -0700 | [diff] [blame] | 48 | config SENSORS_MAX16064 |
| 49 | tristate "Maxim MAX16064" |
| 50 | default n |
| 51 | help |
| 52 | If you say yes here you get hardware monitoring support for Maxim |
| 53 | MAX16064. |
| 54 | |
| 55 | This driver can also be built as a module. If so, the module will |
| 56 | be called max16064. |
| 57 | |
| 58 | config SENSORS_MAX34440 |
| 59 | tristate "Maxim MAX34440/MAX34441" |
| 60 | default n |
| 61 | help |
| 62 | If you say yes here you get hardware monitoring support for Maxim |
| 63 | MAX34440 and MAX34441. |
| 64 | |
| 65 | This driver can also be built as a module. If so, the module will |
| 66 | be called max34440. |
| 67 | |
| 68 | config SENSORS_MAX8688 |
| 69 | tristate "Maxim MAX8688" |
| 70 | default n |
| 71 | help |
| 72 | If you say yes here you get hardware monitoring support for Maxim |
| 73 | MAX8688. |
| 74 | |
| 75 | This driver can also be built as a module. If so, the module will |
| 76 | be called max8688. |
| 77 | |
| 78 | config SENSORS_UCD9000 |
| 79 | tristate "TI UCD90120, UCD90124, UCD9090, UCD90910" |
| 80 | default n |
| 81 | help |
| 82 | If you say yes here you get hardware monitoring support for TI |
| 83 | UCD90120, UCD90124, UCD9090, UCD90910 Sequencer and System Health |
| 84 | Controllers. |
| 85 | |
| 86 | This driver can also be built as a module. If so, the module will |
| 87 | be called ucd9000. |
| 88 | |
| 89 | config SENSORS_UCD9200 |
| 90 | tristate "TI UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, UCD9248" |
| 91 | default n |
| 92 | help |
| 93 | If you say yes here you get hardware monitoring support for TI |
| 94 | UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, and UCD9248 |
| 95 | Digital PWM System Controllers. |
| 96 | |
| 97 | This driver can also be built as a module. If so, the module will |
| 98 | be called ucd9200. |
| 99 | |
| 100 | endif # PMBUS |