summaryrefslogtreecommitdiff
path: root/include/linux/pmbus.h
diff options
context:
space:
mode:
authorErik Rosen <erik.rosen@metormote.com>2021-06-09 11:32:05 +0200
committerGuenter Roeck <linux@roeck-us.net>2021-06-17 04:21:46 -0700
commitdbc0860f7a3d43604c380822a456d26ef6f70a06 (patch)
tree918521228b372ed549be2d0292b0cced872a8b63 /include/linux/pmbus.h
parentff53b77e1e1bc9fd21e087e37a8444e8559d8d36 (diff)
hwmon: (pmbus) Add new pmbus flag NO_WRITE_PROTECT
Some PMBus chips respond with invalid data when reading the WRITE_PROTECT register. For such chips, this flag should be set so that the PMBus core driver doesn't use the WRITE_PROTECT command to determine its behavior. Signed-off-by: Erik Rosen <erik.rosen@metormote.com> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'include/linux/pmbus.h')
-rw-r--r--include/linux/pmbus.h9
1 files changed, 9 insertions, 0 deletions
diff --git a/include/linux/pmbus.h b/include/linux/pmbus.h
index edd7c84fef65..12c515a27d3a 100644
--- a/include/linux/pmbus.h
+++ b/include/linux/pmbus.h
@@ -56,6 +56,15 @@
*/
#define PMBUS_READ_STATUS_AFTER_FAILED_CHECK BIT(3)
+/*
+ * PMBUS_NO_WRITE_PROTECT
+ *
+ * Some PMBus chips respond with invalid data when reading the WRITE_PROTECT
+ * register. For such chips, this flag should be set so that the PMBus core
+ * driver doesn't use the WRITE_PROTECT command to determine its behavior.
+ */
+#define PMBUS_NO_WRITE_PROTECT BIT(4)
+
struct pmbus_platform_data {
u32 flags; /* Device specific flags */