summaryrefslogtreecommitdiffstats
path: root/recipes-kernel/linux/linux-ti33x-psp-3.2/3.2.12/0041-hwmon-zl6100-Enable-interval-between-chip-accesses-f.patch
diff options
context:
space:
mode:
Diffstat (limited to 'recipes-kernel/linux/linux-ti33x-psp-3.2/3.2.12/0041-hwmon-zl6100-Enable-interval-between-chip-accesses-f.patch')
-rw-r--r--recipes-kernel/linux/linux-ti33x-psp-3.2/3.2.12/0041-hwmon-zl6100-Enable-interval-between-chip-accesses-f.patch72
1 files changed, 72 insertions, 0 deletions
diff --git a/recipes-kernel/linux/linux-ti33x-psp-3.2/3.2.12/0041-hwmon-zl6100-Enable-interval-between-chip-accesses-f.patch b/recipes-kernel/linux/linux-ti33x-psp-3.2/3.2.12/0041-hwmon-zl6100-Enable-interval-between-chip-accesses-f.patch
new file mode 100644
index 00000000..7d266e88
--- /dev/null
+++ b/recipes-kernel/linux/linux-ti33x-psp-3.2/3.2.12/0041-hwmon-zl6100-Enable-interval-between-chip-accesses-f.patch
@@ -0,0 +1,72 @@
1From e4dffc01371682d0b23d22f1fe611f96b53cc486 Mon Sep 17 00:00:00 2001
2From: Guenter Roeck <guenter.roeck@ericsson.com>
3Date: Tue, 13 Mar 2012 09:05:14 -0700
4Subject: [PATCH 41/42] hwmon: (zl6100) Enable interval between chip accesses
5 for all chips
6
7commit fecfb64422d91a9621a3f96ab75c3a5f13e80b58 upstream.
8
9Intersil reports that all chips supported by the zl6100 driver require
10an interval between chip accesses, even ZL2004 and ZL6105 which were thought
11to be safe.
12
13Reported-by: Vivek Gani <vgani@intersil.com>
14Signed-off-by: Guenter Roeck <guenter.roeck@ericsson.com>
15Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
16---
17 Documentation/hwmon/zl6100 | 14 ++++++--------
18 drivers/hwmon/pmbus/zl6100.c | 11 +++--------
19 2 files changed, 9 insertions(+), 16 deletions(-)
20
21diff --git a/Documentation/hwmon/zl6100 b/Documentation/hwmon/zl6100
22index 7617798..c5e1a5b 100644
23--- a/Documentation/hwmon/zl6100
24+++ b/Documentation/hwmon/zl6100
25@@ -73,14 +73,12 @@ Module parameters
26 delay
27 -----
28
29-Some Intersil/Zilker Labs DC-DC controllers require a minimum interval between
30-I2C bus accesses. According to Intersil, the minimum interval is 2 ms, though
31-1 ms appears to be sufficient and has not caused any problems in testing.
32-The problem is known to affect ZL6100, ZL2105, and ZL2008. It is known not to
33-affect ZL2004 and ZL6105. The driver automatically sets the interval to 1 ms
34-except for ZL2004 and ZL6105. To enable manual override, the driver provides a
35-writeable module parameter, 'delay', which can be used to set the interval to
36-a value between 0 and 65,535 microseconds.
37+Intersil/Zilker Labs DC-DC controllers require a minimum interval between I2C
38+bus accesses. According to Intersil, the minimum interval is 2 ms, though 1 ms
39+appears to be sufficient and has not caused any problems in testing. The problem
40+is known to affect all currently supported chips. For manual override, the
41+driver provides a writeable module parameter, 'delay', which can be used to set
42+the interval to a value between 0 and 65,535 microseconds.
43
44
45 Sysfs entries
46diff --git a/drivers/hwmon/pmbus/zl6100.c b/drivers/hwmon/pmbus/zl6100.c
47index ba296fd..5c5cdd2 100644
48--- a/drivers/hwmon/pmbus/zl6100.c
49+++ b/drivers/hwmon/pmbus/zl6100.c
50@@ -178,16 +178,11 @@ static int zl6100_probe(struct i2c_client *client,
51 data->id = mid->driver_data;
52
53 /*
54- * ZL2008, ZL2105, and ZL6100 are known to require a wait time
55- * between I2C accesses. ZL2004 and ZL6105 are known to be safe.
56- *
57- * Only clear the wait time for chips known to be safe. The wait time
58- * can be cleared later for additional chips if tests show that it
59- * is not needed (in other words, better be safe than sorry).
60+ * According to information from the chip vendor, all currently
61+ * supported chips are known to require a wait time between I2C
62+ * accesses.
63 */
64 data->delay = delay;
65- if (data->id == zl2004 || data->id == zl6105)
66- data->delay = 0;
67
68 /*
69 * Since there was a direct I2C device access above, wait before
70--
711.7.9.4
72