From d6fd60e81f499d5cc9226dece8dab4a6a5e01f9e Mon Sep 17 00:00:00 2001 From: Guenter Roeck Date: Mon, 29 Aug 2011 22:53:20 -0700 Subject: [PATCH] --- yaml --- r: 263638 b: refs/heads/master c: d91aae1e52e5289a94f4ddff968decfc8d37271e h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/hwmon/max16065 | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index 005f1df43c66..ba2474732d6a 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: ff71c182f461da5ae9d2d65f8a63f5a9193b9be1 +refs/heads/master: d91aae1e52e5289a94f4ddff968decfc8d37271e diff --git a/trunk/Documentation/hwmon/max16065 b/trunk/Documentation/hwmon/max16065 index 44b4f61e04f9..c11f64a1f2ad 100644 --- a/trunk/Documentation/hwmon/max16065 +++ b/trunk/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 -------------