aboutsummaryrefslogtreecommitdiff
path: root/Documentation/hwmon
diff options
context:
space:
mode:
authorGravatar Mårten Lindahl <marten.lindahl@axis.com> 2022-04-28 16:40:38 +0200
committerGravatar Guenter Roeck <linux@roeck-us.net> 2022-05-20 10:57:06 -0700
commitb90f994a37cc1fc028807007fbf5f1df7d6bf141 (patch)
tree563720e20a1c74a1a6bfef8ecfc35af9b30cca91 /Documentation/hwmon
parenthwmon: (pmbus) Use _pmbus_read_byte_data with callback (diff)
downloadlinux-b90f994a37cc1fc028807007fbf5f1df7d6bf141.tar.gz
linux-b90f994a37cc1fc028807007fbf5f1df7d6bf141.tar.bz2
linux-b90f994a37cc1fc028807007fbf5f1df7d6bf141.zip
hwmon: (pmbus/ltc2978) Add chip specific write_byte_data
Several of the manuals for devices supported by this driver describes the need for a minimum wait time before the chip is ready to receive next command. This wait time is already implemented in the driver as a ltc_wait_ready function with a driver defined wait time of 100 ms, and is considered for specific devices before reading/writing data on the pmbus. Since this driver uses the default pmbus_regulator_ops for the enable/ disable/is_enabled functions we should add a driver specific callback for write_byte_data to prevent bypassing the wait time recommendations for the following devices: ltc3880/ltc3882/ltc3883/ltc3884/ltc3886/ ltc3887/ltc3889/ltm4664/ltm4675/ltm4676/ltm4677/ltm4678/ltm4680/ltm4686/ ltm4700/ltc7880. Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com> Link: https://lore.kernel.org/r/20220428144039.2464667-4-marten.lindahl@axis.com Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'Documentation/hwmon')
0 files changed, 0 insertions, 0 deletions