diff options
| author | Atif Ofluoglu <mailto:atif.ofluoglu@maximintegrated.com> | 2022-04-15 16:34:29 +0300 |
|---|---|---|
| committer | Guenter Roeck <linux@roeck-us.net> | 2022-05-20 10:57:05 -0700 |
| commit | e5c498ccc90c87155d1f6980cac050d48b8a84b4 (patch) | |
| tree | f3709f82348dea7a43b67e663f21f58200004b76 /drivers/hwmon/pmbus/Kconfig | |
| parent | 229b159c505a7ee5da86f952db1e644b213ccb61 (diff) | |
hwmon: (pmbus/max16601) Add MAX16602 support
Adding another MAX16602 chip support to MAX16601 driver
Tested with MAX16602 works as expected.
Signed-off-by: Atif Ofluoglu <atif.ofluoglu@maximintegrated.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'drivers/hwmon/pmbus/Kconfig')
| -rw-r--r-- | drivers/hwmon/pmbus/Kconfig | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/hwmon/pmbus/Kconfig b/drivers/hwmon/pmbus/Kconfig index a2ea1d5a8765..53683d2d0fb2 100644 --- a/drivers/hwmon/pmbus/Kconfig +++ b/drivers/hwmon/pmbus/Kconfig @@ -228,10 +228,10 @@ config SENSORS_MAX16064 be called max16064. config SENSORS_MAX16601 - tristate "Maxim MAX16508, MAX16601" + tristate "Maxim MAX16508, MAX16601, MAX16602" help If you say yes here you get hardware monitoring support for Maxim - MAX16508 and MAX16601. + MAX16508, MAX16601 and MAX16602. This driver can also be built as a module. If so, the module will be called max16601. |