summaryrefslogtreecommitdiff
path: root/Documentation/hwmon/max16065
diff options
context:
space:
mode:
authorGuenter Roeck <guenter.roeck@ericsson.com>2011-08-29 22:53:20 -0700
committerGuenter Roeck <guenter.roeck@ericsson.com>2011-09-06 08:56:06 -0700
commitd91aae1e52e5289a94f4ddff968decfc8d37271e (patch)
tree9c832e9ae7d869f67d78795c46be8e1121b8ffbf /Documentation/hwmon/max16065
parentff71c182f461da5ae9d2d65f8a63f5a9193b9be1 (diff)
hwmon: (max16065) Add chip access warning to documentation
The chips supported by the max16065 driver should not be accessed using direct i2ctools commands. Add warning to driver documentation to alert users. Signed-off-by: Guenter Roeck <guenter.roeck@ericsson.com> Acked-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'Documentation/hwmon/max16065')
-rw-r--r--Documentation/hwmon/max160657
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/hwmon/max16065 b/Documentation/hwmon/max16065
index 44b4f61e04f9..c11f64a1f2ad 100644
--- a/Documentation/hwmon/max16065
+++ b/Documentation/hwmon/max16065
@@ -62,6 +62,13 @@ can be safely used to identify the chip. You will have to instantiate
the devices explicitly. Please see Documentation/i2c/instantiating-devices for
details.
+WARNING: Do not access chip registers using the i2cdump command, and do not use
+any of the i2ctools commands on a command register (0xa5 to 0xac). The chips
+supported by this driver interpret any access to a command register (including
+read commands) as request to execute the command in question. This may result in
+power loss, board resets, and/or Flash corruption. Worst case, your board may
+turn into a brick.
+
Sysfs entries
-------------