diff options
-rw-r--r-- | Documentation/hwmon/pmbus | 3 | ||||
-rw-r--r-- | drivers/hwmon/pmbus/Kconfig | 3 | ||||
-rw-r--r-- | drivers/hwmon/pmbus/pmbus.c | 1 |
3 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/hwmon/pmbus b/Documentation/hwmon/pmbus index c2b157ba9006..f90f99920cc5 100644 --- a/Documentation/hwmon/pmbus +++ b/Documentation/hwmon/pmbus | |||
@@ -15,13 +15,14 @@ Supported chips: | |||
15 | http://www.onsemi.com/pub_link/Collateral/NCP4200-D.PDF | 15 | http://www.onsemi.com/pub_link/Collateral/NCP4200-D.PDF |
16 | http://www.onsemi.com/pub_link/Collateral/JUNE%202009-%20REV.%200.PDF | 16 | http://www.onsemi.com/pub_link/Collateral/JUNE%202009-%20REV.%200.PDF |
17 | * Lineage Power | 17 | * Lineage Power |
18 | Prefixes: 'pdt003', 'pdt006', 'pdt012', 'udt020' | 18 | Prefixes: 'mdt040', 'pdt003', 'pdt006', 'pdt012', 'udt020' |
19 | Addresses scanned: - | 19 | Addresses scanned: - |
20 | Datasheets: | 20 | Datasheets: |
21 | http://www.lineagepower.com/oem/pdf/PDT003A0X.pdf | 21 | http://www.lineagepower.com/oem/pdf/PDT003A0X.pdf |
22 | http://www.lineagepower.com/oem/pdf/PDT006A0X.pdf | 22 | http://www.lineagepower.com/oem/pdf/PDT006A0X.pdf |
23 | http://www.lineagepower.com/oem/pdf/PDT012A0X.pdf | 23 | http://www.lineagepower.com/oem/pdf/PDT012A0X.pdf |
24 | http://www.lineagepower.com/oem/pdf/UDT020A0X.pdf | 24 | http://www.lineagepower.com/oem/pdf/UDT020A0X.pdf |
25 | http://www.lineagepower.com/oem/pdf/MDT040A0X.pdf | ||
25 | * Texas Instruments TPS40400, TPS40422 | 26 | * Texas Instruments TPS40400, TPS40422 |
26 | Prefixes: 'tps40400', 'tps40422' | 27 | Prefixes: 'tps40400', 'tps40422' |
27 | Addresses scanned: - | 28 | Addresses scanned: - |
diff --git a/drivers/hwmon/pmbus/Kconfig b/drivers/hwmon/pmbus/Kconfig index 7968c815f443..d1aa2dbd5b75 100644 --- a/drivers/hwmon/pmbus/Kconfig +++ b/drivers/hwmon/pmbus/Kconfig | |||
@@ -20,7 +20,8 @@ config SENSORS_PMBUS | |||
20 | help | 20 | help |
21 | If you say yes here you get hardware monitoring support for generic | 21 | If you say yes here you get hardware monitoring support for generic |
22 | PMBus devices, including but not limited to ADP4000, BMR453, BMR454, | 22 | PMBus devices, including but not limited to ADP4000, BMR453, BMR454, |
23 | NCP4200, NCP4208, TPS40400, and TPS40422. | 23 | MDT040, NCP4200, NCP4208, PDT003, PDT006, PDT012, UDT020, TPS40400, |
24 | and TPS40422. | ||
24 | 25 | ||
25 | This driver can also be built as a module. If so, the module will | 26 | This driver can also be built as a module. If so, the module will |
26 | be called pmbus. | 27 | be called pmbus. |
diff --git a/drivers/hwmon/pmbus/pmbus.c b/drivers/hwmon/pmbus/pmbus.c index 7d5161dd04f0..7e91700131a7 100644 --- a/drivers/hwmon/pmbus/pmbus.c +++ b/drivers/hwmon/pmbus/pmbus.c | |||
@@ -185,6 +185,7 @@ static const struct i2c_device_id pmbus_id[] = { | |||
185 | {"adp4000", 1}, | 185 | {"adp4000", 1}, |
186 | {"bmr453", 1}, | 186 | {"bmr453", 1}, |
187 | {"bmr454", 1}, | 187 | {"bmr454", 1}, |
188 | {"mdt040", 1}, | ||
188 | {"ncp4200", 1}, | 189 | {"ncp4200", 1}, |
189 | {"ncp4208", 1}, | 190 | {"ncp4208", 1}, |
190 | {"pdt003", 1}, | 191 | {"pdt003", 1}, |