Commit 91564418 authored by Konstantin Aladyshev's avatar Konstantin Aladyshev Committed by Guenter Roeck

hwmon: (pmbus/mp2975) Correct comment inside 'mp2975_read_byte_data'

The current driver code no longer perfrom internal conversion from
VID to direct. Instead it configures READ_VOUT using MFR_DC_LOOP_CTRL.
Correct the comment message inside the 'mp2975_read_byte_data'
function to match the driver logic.
Signed-off-by: default avatarKonstantin Aladyshev <aladyshev22@gmail.com>
Fixes: c60fe56c ("hwmon: (pmbus/mp2975) Fix driver initialization for MP2975 device")
Link: https://lore.kernel.org/r/20240127154844.989-1-aladyshev22@gmail.comSigned-off-by: default avatarGuenter Roeck <linux@roeck-us.net>
parent c60fe56c
...@@ -131,10 +131,9 @@ static int mp2975_read_byte_data(struct i2c_client *client, int page, int reg) ...@@ -131,10 +131,9 @@ static int mp2975_read_byte_data(struct i2c_client *client, int page, int reg)
switch (reg) { switch (reg) {
case PMBUS_VOUT_MODE: case PMBUS_VOUT_MODE:
/* /*
* Enforce VOUT direct format, since device allows to set the * Report direct format as configured by MFR_DC_LOOP_CTRL.
* different formats for the different rails. Conversion from * Unlike on MP2971/MP2973 the reported VOUT_MODE isn't automatically
* VID to direct provided by driver internally, in case it is * internally updated, but always reads as PB_VOUT_MODE_VID.
* necessary.
*/ */
return PB_VOUT_MODE_DIRECT; return PB_VOUT_MODE_DIRECT;
default: default:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment