| xj | b04a402 | 2021-11-25 15:01:52 +0800 | [diff] [blame] | 1 | # |
| 2 | # PMBus chip drivers configuration |
| 3 | # |
| 4 | |
| 5 | menuconfig PMBUS |
| 6 | tristate "PMBus support" |
| 7 | depends on I2C |
| 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 |
| 22 | PMBus devices, including but not limited to ADP4000, BMR453, BMR454, |
| 23 | MDT040, NCP4200, NCP4208, PDT003, PDT006, PDT012, TPS40400, TPS544B20, |
| 24 | TPS544B25, TPS544C20, TPS544C25, and UDT020. |
| 25 | |
| 26 | This driver can also be built as a module. If so, the module will |
| 27 | be called pmbus. |
| 28 | |
| 29 | config SENSORS_ADM1275 |
| 30 | tristate "Analog Devices ADM1275 and compatibles" |
| 31 | default n |
| 32 | help |
| 33 | If you say yes here you get hardware monitoring support for Analog |
| 34 | Devices ADM1075, ADM1272, ADM1275, ADM1276, ADM1278, ADM1293, |
| 35 | and ADM1294 Hot-Swap Controller and Digital Power Monitors. |
| 36 | |
| 37 | This driver can also be built as a module. If so, the module will |
| 38 | be called adm1275. |
| 39 | |
| 40 | config SENSORS_IBM_CFFPS |
| 41 | tristate "IBM Common Form Factor Power Supply" |
| 42 | depends on LEDS_CLASS |
| 43 | help |
| 44 | If you say yes here you get hardware monitoring support for the IBM |
| 45 | Common Form Factor power supply. |
| 46 | |
| 47 | This driver can also be built as a module. If so, the module will |
| 48 | be called ibm-cffps. |
| 49 | |
| 50 | config SENSORS_IR35221 |
| 51 | tristate "Infineon IR35221" |
| 52 | default n |
| 53 | help |
| 54 | If you say yes here you get hardware monitoring support for the |
| 55 | Infineon IR35221 controller. |
| 56 | |
| 57 | This driver can also be built as a module. If so, the module will |
| 58 | be called ir35521. |
| 59 | |
| 60 | config SENSORS_LM25066 |
| 61 | tristate "National Semiconductor LM25066 and compatibles" |
| 62 | default n |
| 63 | help |
| 64 | If you say yes here you get hardware monitoring support for National |
| 65 | Semiconductor LM25056, LM25066, LM5064, and LM5066. |
| 66 | |
| 67 | This driver can also be built as a module. If so, the module will |
| 68 | be called lm25066. |
| 69 | |
| 70 | config SENSORS_LTC2978 |
| 71 | tristate "Linear Technologies LTC2978 and compatibles" |
| 72 | default n |
| 73 | help |
| 74 | If you say yes here you get hardware monitoring support for Linear |
| 75 | Technology LTC2974, LTC2975, LTC2977, LTC2978, LTC2980, LTC3880, |
| 76 | LTC3883, LTC3886, LTC3887, LTCM2987, LTM4675, and LTM4676. |
| 77 | |
| 78 | This driver can also be built as a module. If so, the module will |
| 79 | be called ltc2978. |
| 80 | |
| 81 | config SENSORS_LTC2978_REGULATOR |
| 82 | bool "Regulator support for LTC2978 and compatibles" |
| 83 | depends on SENSORS_LTC2978 && REGULATOR |
| 84 | help |
| 85 | If you say yes here you get regulator support for Linear |
| 86 | Technology LTC2974, LTC2977, LTC2978, LTC3880, LTC3883, and LTM4676. |
| 87 | |
| 88 | config SENSORS_LTC3815 |
| 89 | tristate "Linear Technologies LTC3815" |
| 90 | default n |
| 91 | help |
| 92 | If you say yes here you get hardware monitoring support for Linear |
| 93 | Technology LTC3815. |
| 94 | |
| 95 | This driver can also be built as a module. If so, the module will |
| 96 | be called ltc3815. |
| 97 | |
| 98 | config SENSORS_MAX16064 |
| 99 | tristate "Maxim MAX16064" |
| 100 | default n |
| 101 | help |
| 102 | If you say yes here you get hardware monitoring support for Maxim |
| 103 | MAX16064. |
| 104 | |
| 105 | This driver can also be built as a module. If so, the module will |
| 106 | be called max16064. |
| 107 | |
| 108 | config SENSORS_MAX20751 |
| 109 | tristate "Maxim MAX20751" |
| 110 | default n |
| 111 | help |
| 112 | If you say yes here you get hardware monitoring support for Maxim |
| 113 | MAX20751. |
| 114 | |
| 115 | This driver can also be built as a module. If so, the module will |
| 116 | be called max20751. |
| 117 | |
| 118 | config SENSORS_MAX31785 |
| 119 | tristate "Maxim MAX31785 and compatibles" |
| 120 | default n |
| 121 | help |
| 122 | If you say yes here you get hardware monitoring support for Maxim |
| 123 | MAX31785. |
| 124 | |
| 125 | This driver can also be built as a module. If so, the module will |
| 126 | be called max31785. |
| 127 | |
| 128 | config SENSORS_MAX34440 |
| 129 | tristate "Maxim MAX34440 and compatibles" |
| 130 | default n |
| 131 | help |
| 132 | If you say yes here you get hardware monitoring support for Maxim |
| 133 | MAX34440, MAX34441, MAX34446, MAX34451, MAX34460, and MAX34461. |
| 134 | |
| 135 | This driver can also be built as a module. If so, the module will |
| 136 | be called max34440. |
| 137 | |
| 138 | config SENSORS_MAX8688 |
| 139 | tristate "Maxim MAX8688" |
| 140 | default n |
| 141 | help |
| 142 | If you say yes here you get hardware monitoring support for Maxim |
| 143 | MAX8688. |
| 144 | |
| 145 | This driver can also be built as a module. If so, the module will |
| 146 | be called max8688. |
| 147 | |
| 148 | config SENSORS_TPS40422 |
| 149 | tristate "TI TPS40422" |
| 150 | default n |
| 151 | help |
| 152 | If you say yes here you get hardware monitoring support for TI |
| 153 | TPS40422. |
| 154 | |
| 155 | This driver can also be built as a module. If so, the module will |
| 156 | be called tps40422. |
| 157 | |
| 158 | config SENSORS_TPS53679 |
| 159 | tristate "TI TPS53679" |
| 160 | help |
| 161 | If you say yes here you get hardware monitoring support for TI |
| 162 | TPS53679. |
| 163 | |
| 164 | This driver can also be built as a module. If so, the module will |
| 165 | be called tps53679. |
| 166 | |
| 167 | config SENSORS_UCD9000 |
| 168 | tristate "TI UCD90120, UCD90124, UCD90160, UCD9090, UCD90910" |
| 169 | default n |
| 170 | help |
| 171 | If you say yes here you get hardware monitoring support for TI |
| 172 | UCD90120, UCD90124, UCD90160, UCD9090, UCD90910, Sequencer and System |
| 173 | Health Controllers. |
| 174 | |
| 175 | This driver can also be built as a module. If so, the module will |
| 176 | be called ucd9000. |
| 177 | |
| 178 | config SENSORS_UCD9200 |
| 179 | tristate "TI UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, UCD9248" |
| 180 | default n |
| 181 | help |
| 182 | If you say yes here you get hardware monitoring support for TI |
| 183 | UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, and UCD9248 |
| 184 | Digital PWM System Controllers. |
| 185 | |
| 186 | This driver can also be built as a module. If so, the module will |
| 187 | be called ucd9200. |
| 188 | |
| 189 | config SENSORS_ZL6100 |
| 190 | tristate "Intersil ZL6100 and compatibles" |
| 191 | default n |
| 192 | help |
| 193 | If you say yes here you get hardware monitoring support for Intersil |
| 194 | ZL2004, ZL2005, ZL2006, ZL2008, ZL2105, ZL2106, ZL6100, ZL6105, |
| 195 | ZL9101M, and ZL9117M Digital DC/DC Controllers, as well as for |
| 196 | Ericsson BMR450, BMR451, BMR462, BMR463, and BMR464. |
| 197 | |
| 198 | This driver can also be built as a module. If so, the module will |
| 199 | be called zl6100. |
| 200 | |
| 201 | endif # PMBUS |