aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDoug Anderson <dianders@chromium.org>2014-04-29 13:30:51 -0400
committerWolfram Sang <wsa@the-dreams.de>2014-05-22 04:09:22 -0400
commita83bea7c1170ad8c68d65ed2fff6a533e68f67a4 (patch)
tree0bf15296942f62d84c0e67be5622b316eaa5e388
parent482116badacba9308abd6c5cae2f5f19e2f81449 (diff)
i2c: mux: Add more warnings to i2c-arb-gpio-challenge docs
This adds some more warnings to the i2c-arb-gpio-challenge docs to help encourage people not to use it in their designs unless they have no choice. Signed-off-by: Doug Anderson <dianders@chromium.org> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
-rw-r--r--Documentation/devicetree/bindings/i2c/i2c-arb-gpio-challenge.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/i2c/i2c-arb-gpio-challenge.txt b/Documentation/devicetree/bindings/i2c/i2c-arb-gpio-challenge.txt
index 1ac8ea8ade1d..bfeabb843941 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-arb-gpio-challenge.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c-arb-gpio-challenge.txt
@@ -8,6 +8,12 @@ the standard I2C multi-master rules. Using GPIOs is generally useful in
8the case where there is a device on the bus that has errata and/or bugs 8the case where there is a device on the bus that has errata and/or bugs
9that makes standard multimaster mode not feasible. 9that makes standard multimaster mode not feasible.
10 10
11Note that this scheme works well enough but has some downsides:
12* It is nonstandard (not using standard I2C multimaster)
13* Having two masters on a bus in general makes it relatively hard to debug
14 problems (hard to tell if i2c issues were caused by one master, another, or
15 some device on the bus).
16
11 17
12Algorithm: 18Algorithm:
13 19