| .. | .. |
|---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
|---|
| 1 | 2 | # |
|---|
| 2 | 3 | # PMBus chip drivers configuration |
|---|
| 3 | 4 | # |
|---|
| .. | .. |
|---|
| 5 | 6 | menuconfig PMBUS |
|---|
| 6 | 7 | tristate "PMBus support" |
|---|
| 7 | 8 | depends on I2C |
|---|
| 8 | | - default n |
|---|
| 9 | 9 | help |
|---|
| 10 | 10 | Say yes here if you want to enable PMBus support. |
|---|
| 11 | 11 | |
|---|
| .. | .. |
|---|
| 20 | 20 | help |
|---|
| 21 | 21 | If you say yes here you get hardware monitoring support for generic |
|---|
| 22 | 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. |
|---|
| 23 | + MAX20796, MDT040, NCP4200, NCP4208, PDT003, PDT006, PDT012, TPS40400, |
|---|
| 24 | + TPS544B20, TPS544B25, TPS544C20, TPS544C25, and UDT020. |
|---|
| 25 | 25 | |
|---|
| 26 | 26 | This driver can also be built as a module. If so, the module will |
|---|
| 27 | 27 | be called pmbus. |
|---|
| 28 | 28 | |
|---|
| 29 | +config SENSORS_ADM1266 |
|---|
| 30 | + tristate "Analog Devices ADM1266 Sequencer" |
|---|
| 31 | + select CRC8 |
|---|
| 32 | + depends on GPIOLIB |
|---|
| 33 | + help |
|---|
| 34 | + If you say yes here you get hardware monitoring support for Analog |
|---|
| 35 | + Devices ADM1266 Cascadable Super Sequencer. |
|---|
| 36 | + |
|---|
| 37 | + This driver can also be built as a module. If so, the module will |
|---|
| 38 | + be called adm1266. |
|---|
| 39 | + |
|---|
| 29 | 40 | config SENSORS_ADM1275 |
|---|
| 30 | 41 | tristate "Analog Devices ADM1275 and compatibles" |
|---|
| 31 | | - default n |
|---|
| 32 | 42 | help |
|---|
| 33 | 43 | If you say yes here you get hardware monitoring support for Analog |
|---|
| 34 | 44 | Devices ADM1075, ADM1272, ADM1275, ADM1276, ADM1278, ADM1293, |
|---|
| .. | .. |
|---|
| 36 | 46 | |
|---|
| 37 | 47 | This driver can also be built as a module. If so, the module will |
|---|
| 38 | 48 | be called adm1275. |
|---|
| 49 | + |
|---|
| 50 | +config SENSORS_BEL_PFE |
|---|
| 51 | + tristate "Bel PFE Compatible Power Supplies" |
|---|
| 52 | + help |
|---|
| 53 | + If you say yes here you get hardware monitoring support for BEL |
|---|
| 54 | + PFE1100 and PFE3000 Power Supplies. |
|---|
| 55 | + |
|---|
| 56 | + This driver can also be built as a module. If so, the module will |
|---|
| 57 | + be called bel-pfe. |
|---|
| 39 | 58 | |
|---|
| 40 | 59 | config SENSORS_IBM_CFFPS |
|---|
| 41 | 60 | tristate "IBM Common Form Factor Power Supply" |
|---|
| .. | .. |
|---|
| 47 | 66 | This driver can also be built as a module. If so, the module will |
|---|
| 48 | 67 | be called ibm-cffps. |
|---|
| 49 | 68 | |
|---|
| 69 | +config SENSORS_INSPUR_IPSPS |
|---|
| 70 | + tristate "INSPUR Power System Power Supply" |
|---|
| 71 | + help |
|---|
| 72 | + If you say yes here you get hardware monitoring support for the INSPUR |
|---|
| 73 | + Power System power supply. |
|---|
| 74 | + |
|---|
| 75 | + This driver can also be built as a module. If so, the module will |
|---|
| 76 | + be called inspur-ipsps. |
|---|
| 77 | + |
|---|
| 50 | 78 | config SENSORS_IR35221 |
|---|
| 51 | 79 | tristate "Infineon IR35221" |
|---|
| 52 | | - default n |
|---|
| 53 | 80 | help |
|---|
| 54 | 81 | If you say yes here you get hardware monitoring support for the |
|---|
| 55 | 82 | Infineon IR35221 controller. |
|---|
| 56 | 83 | |
|---|
| 57 | 84 | This driver can also be built as a module. If so, the module will |
|---|
| 58 | | - be called ir35521. |
|---|
| 85 | + be called ir35221. |
|---|
| 86 | + |
|---|
| 87 | +config SENSORS_IR38064 |
|---|
| 88 | + tristate "Infineon IR38064" |
|---|
| 89 | + help |
|---|
| 90 | + If you say yes here you get hardware monitoring support for Infineon |
|---|
| 91 | + IR38064. |
|---|
| 92 | + |
|---|
| 93 | + This driver can also be built as a module. If so, the module will |
|---|
| 94 | + be called ir38064. |
|---|
| 95 | + |
|---|
| 96 | +config SENSORS_IRPS5401 |
|---|
| 97 | + tristate "Infineon IRPS5401" |
|---|
| 98 | + help |
|---|
| 99 | + If you say yes here you get hardware monitoring support for the |
|---|
| 100 | + Infineon IRPS5401 controller. |
|---|
| 101 | + |
|---|
| 102 | + This driver can also be built as a module. If so, the module will |
|---|
| 103 | + be called irps5401. |
|---|
| 104 | + |
|---|
| 105 | +config SENSORS_ISL68137 |
|---|
| 106 | + tristate "Renesas Digital Multiphase Voltage Regulators" |
|---|
| 107 | + help |
|---|
| 108 | + If you say yes here you get hardware monitoring support for Renesas |
|---|
| 109 | + digital multiphase voltage regulators. |
|---|
| 110 | + |
|---|
| 111 | + This driver can also be built as a module. If so, the module will |
|---|
| 112 | + be called isl68137. |
|---|
| 59 | 113 | |
|---|
| 60 | 114 | config SENSORS_LM25066 |
|---|
| 61 | 115 | tristate "National Semiconductor LM25066 and compatibles" |
|---|
| 62 | | - default n |
|---|
| 63 | 116 | help |
|---|
| 64 | 117 | If you say yes here you get hardware monitoring support for National |
|---|
| 65 | 118 | Semiconductor LM25056, LM25066, LM5064, and LM5066. |
|---|
| .. | .. |
|---|
| 69 | 122 | |
|---|
| 70 | 123 | config SENSORS_LTC2978 |
|---|
| 71 | 124 | tristate "Linear Technologies LTC2978 and compatibles" |
|---|
| 72 | | - default n |
|---|
| 73 | 125 | help |
|---|
| 74 | 126 | 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. |
|---|
| 127 | + Technology LTC2972, LTC2974, LTC2975, LTC2977, LTC2978, LTC2979, |
|---|
| 128 | + LTC2980, and LTM2987. |
|---|
| 77 | 129 | |
|---|
| 78 | 130 | This driver can also be built as a module. If so, the module will |
|---|
| 79 | 131 | be called ltc2978. |
|---|
| .. | .. |
|---|
| 82 | 134 | bool "Regulator support for LTC2978 and compatibles" |
|---|
| 83 | 135 | depends on SENSORS_LTC2978 && REGULATOR |
|---|
| 84 | 136 | help |
|---|
| 85 | | - If you say yes here you get regulator support for Linear |
|---|
| 86 | | - Technology LTC2974, LTC2977, LTC2978, LTC3880, LTC3883, and LTM4676. |
|---|
| 137 | + If you say yes here you get regulator support for Linear Technology |
|---|
| 138 | + LTC3880, LTC3883, LTC3884, LTC3886, LTC3887, LTC3889, LTC7880, |
|---|
| 139 | + LTM4644, LTM4675, LTM4676, LTM4677, LTM4678, LTM4680, LTM4686, |
|---|
| 140 | + and LTM4700. |
|---|
| 87 | 141 | |
|---|
| 88 | 142 | config SENSORS_LTC3815 |
|---|
| 89 | 143 | tristate "Linear Technologies LTC3815" |
|---|
| 90 | | - default n |
|---|
| 91 | 144 | help |
|---|
| 92 | 145 | If you say yes here you get hardware monitoring support for Linear |
|---|
| 93 | 146 | Technology LTC3815. |
|---|
| .. | .. |
|---|
| 97 | 150 | |
|---|
| 98 | 151 | config SENSORS_MAX16064 |
|---|
| 99 | 152 | tristate "Maxim MAX16064" |
|---|
| 100 | | - default n |
|---|
| 101 | 153 | help |
|---|
| 102 | 154 | If you say yes here you get hardware monitoring support for Maxim |
|---|
| 103 | 155 | MAX16064. |
|---|
| .. | .. |
|---|
| 105 | 157 | This driver can also be built as a module. If so, the module will |
|---|
| 106 | 158 | be called max16064. |
|---|
| 107 | 159 | |
|---|
| 160 | +config SENSORS_MAX16601 |
|---|
| 161 | + tristate "Maxim MAX16601" |
|---|
| 162 | + help |
|---|
| 163 | + If you say yes here you get hardware monitoring support for Maxim |
|---|
| 164 | + MAX16601. |
|---|
| 165 | + |
|---|
| 166 | + This driver can also be built as a module. If so, the module will |
|---|
| 167 | + be called max16601. |
|---|
| 168 | + |
|---|
| 169 | +config SENSORS_MAX20730 |
|---|
| 170 | + tristate "Maxim MAX20710, MAX20730, MAX20734, MAX20743" |
|---|
| 171 | + help |
|---|
| 172 | + If you say yes here you get hardware monitoring support for Maxim |
|---|
| 173 | + MAX20710, MAX20730, MAX20734, and MAX20743. |
|---|
| 174 | + |
|---|
| 175 | + This driver can also be built as a module. If so, the module will |
|---|
| 176 | + be called max20730. |
|---|
| 177 | + |
|---|
| 108 | 178 | config SENSORS_MAX20751 |
|---|
| 109 | 179 | tristate "Maxim MAX20751" |
|---|
| 110 | | - default n |
|---|
| 111 | 180 | help |
|---|
| 112 | 181 | If you say yes here you get hardware monitoring support for Maxim |
|---|
| 113 | 182 | MAX20751. |
|---|
| .. | .. |
|---|
| 117 | 186 | |
|---|
| 118 | 187 | config SENSORS_MAX31785 |
|---|
| 119 | 188 | tristate "Maxim MAX31785 and compatibles" |
|---|
| 120 | | - default n |
|---|
| 121 | 189 | help |
|---|
| 122 | 190 | If you say yes here you get hardware monitoring support for Maxim |
|---|
| 123 | 191 | MAX31785. |
|---|
| .. | .. |
|---|
| 127 | 195 | |
|---|
| 128 | 196 | config SENSORS_MAX34440 |
|---|
| 129 | 197 | tristate "Maxim MAX34440 and compatibles" |
|---|
| 130 | | - default n |
|---|
| 131 | 198 | help |
|---|
| 132 | 199 | If you say yes here you get hardware monitoring support for Maxim |
|---|
| 133 | 200 | MAX34440, MAX34441, MAX34446, MAX34451, MAX34460, and MAX34461. |
|---|
| .. | .. |
|---|
| 137 | 204 | |
|---|
| 138 | 205 | config SENSORS_MAX8688 |
|---|
| 139 | 206 | tristate "Maxim MAX8688" |
|---|
| 140 | | - default n |
|---|
| 141 | 207 | help |
|---|
| 142 | 208 | If you say yes here you get hardware monitoring support for Maxim |
|---|
| 143 | 209 | MAX8688. |
|---|
| .. | .. |
|---|
| 145 | 211 | This driver can also be built as a module. If so, the module will |
|---|
| 146 | 212 | be called max8688. |
|---|
| 147 | 213 | |
|---|
| 214 | +config SENSORS_MP2975 |
|---|
| 215 | + tristate "MPS MP2975" |
|---|
| 216 | + help |
|---|
| 217 | + If you say yes here you get hardware monitoring support for MPS |
|---|
| 218 | + MP2975 Dual Loop Digital Multi-Phase Controller. |
|---|
| 219 | + |
|---|
| 220 | + This driver can also be built as a module. If so, the module will |
|---|
| 221 | + be called mp2975. |
|---|
| 222 | + |
|---|
| 223 | +config SENSORS_PXE1610 |
|---|
| 224 | + tristate "Infineon PXE1610" |
|---|
| 225 | + help |
|---|
| 226 | + If you say yes here you get hardware monitoring support for Infineon |
|---|
| 227 | + PXE1610. |
|---|
| 228 | + |
|---|
| 229 | + This driver can also be built as a module. If so, the module will |
|---|
| 230 | + be called pxe1610. |
|---|
| 231 | + |
|---|
| 148 | 232 | config SENSORS_TPS40422 |
|---|
| 149 | 233 | tristate "TI TPS40422" |
|---|
| 150 | | - default n |
|---|
| 151 | 234 | help |
|---|
| 152 | 235 | If you say yes here you get hardware monitoring support for TI |
|---|
| 153 | 236 | TPS40422. |
|---|
| .. | .. |
|---|
| 156 | 239 | be called tps40422. |
|---|
| 157 | 240 | |
|---|
| 158 | 241 | config SENSORS_TPS53679 |
|---|
| 159 | | - tristate "TI TPS53679" |
|---|
| 242 | + tristate "TI TPS53647, TPS53667, TPS53679, TPS53681, TPS53688" |
|---|
| 160 | 243 | help |
|---|
| 161 | 244 | If you say yes here you get hardware monitoring support for TI |
|---|
| 162 | | - TPS53679. |
|---|
| 245 | + TPS53647, TPS53667, TPS53679, TPS53681, and TPS53688. |
|---|
| 163 | 246 | |
|---|
| 164 | 247 | This driver can also be built as a module. If so, the module will |
|---|
| 165 | 248 | be called tps53679. |
|---|
| 166 | 249 | |
|---|
| 167 | 250 | config SENSORS_UCD9000 |
|---|
| 168 | | - tristate "TI UCD90120, UCD90124, UCD90160, UCD9090, UCD90910" |
|---|
| 169 | | - default n |
|---|
| 251 | + tristate "TI UCD90120, UCD90124, UCD90160, UCD90320, UCD9090, UCD90910" |
|---|
| 170 | 252 | help |
|---|
| 171 | 253 | If you say yes here you get hardware monitoring support for TI |
|---|
| 172 | | - UCD90120, UCD90124, UCD90160, UCD9090, UCD90910, Sequencer and System |
|---|
| 173 | | - Health Controllers. |
|---|
| 254 | + UCD90120, UCD90124, UCD90160, UCD90320, UCD9090, UCD90910, Sequencer |
|---|
| 255 | + and System Health Controllers. |
|---|
| 174 | 256 | |
|---|
| 175 | 257 | This driver can also be built as a module. If so, the module will |
|---|
| 176 | 258 | be called ucd9000. |
|---|
| 177 | 259 | |
|---|
| 178 | 260 | config SENSORS_UCD9200 |
|---|
| 179 | 261 | tristate "TI UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, UCD9248" |
|---|
| 180 | | - default n |
|---|
| 181 | 262 | help |
|---|
| 182 | 263 | If you say yes here you get hardware monitoring support for TI |
|---|
| 183 | 264 | UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, and UCD9248 |
|---|
| .. | .. |
|---|
| 186 | 267 | This driver can also be built as a module. If so, the module will |
|---|
| 187 | 268 | be called ucd9200. |
|---|
| 188 | 269 | |
|---|
| 270 | +config SENSORS_XDPE122 |
|---|
| 271 | + tristate "Infineon XDPE122 family" |
|---|
| 272 | + help |
|---|
| 273 | + If you say yes here you get hardware monitoring support for Infineon |
|---|
| 274 | + XDPE12254, XDPE12284, device. |
|---|
| 275 | + |
|---|
| 276 | + This driver can also be built as a module. If so, the module will |
|---|
| 277 | + be called xdpe12284. |
|---|
| 278 | + |
|---|
| 189 | 279 | config SENSORS_ZL6100 |
|---|
| 190 | 280 | tristate "Intersil ZL6100 and compatibles" |
|---|
| 191 | | - default n |
|---|
| 192 | 281 | help |
|---|
| 193 | 282 | If you say yes here you get hardware monitoring support for Intersil |
|---|
| 194 | 283 | ZL2004, ZL2005, ZL2006, ZL2008, ZL2105, ZL2106, ZL6100, ZL6105, |
|---|