About Kernel Documentation Linux Kernel Contact Linux Resources Linux Blog

Documentation / devicetree / bindings / i2c / i2c-arb-gpio-challenge.txt




Custom Search

Based on kernel version 3.16. Page generated on 2014-08-06 21:37 EST.

1	GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
2	=================================================================
3	This uses GPIO lines and a challenge & response mechanism to arbitrate who is
4	the master of an I2C bus in a multimaster situation.
5	
6	In many cases using GPIOs to arbitrate is not needed and a design can use
7	the standard I2C multi-master rules.  Using GPIOs is generally useful in
8	the case where there is a device on the bus that has errata and/or bugs
9	that makes standard multimaster mode not feasible.
10	
11	Note 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	
17	
18	Algorithm:
19	
20	All masters on the bus have a 'bus claim' line which is an output that the
21	others can see. These are all active low with pull-ups enabled.  We'll
22	describe these lines as:
23	
24	- OUR_CLAIM: output from us signaling to other hosts that we want the bus
25	- THEIR_CLAIMS: output from others signaling that they want the bus
26	
27	The basic algorithm is to assert your line when you want the bus, then make
28	sure that the other side doesn't want it also.  A detailed explanation is best
29	done with an example.
30	
31	Let's say we want to claim the bus.  We:
32	1. Assert OUR_CLAIM.
33	2. Waits a little bit for the other sides to notice (slew time, say 10
34	   microseconds).
35	3. Check THEIR_CLAIMS.  If none are asserted then the we have the bus and we are
36	   done.
37	4. Otherwise, wait for a few milliseconds and see if THEIR_CLAIMS are released.
38	5. If not, back off, release the claim and wait for a few more milliseconds.
39	6. Go back to 1 (until retry time has expired).
40	
41	
42	Required properties:
43	- compatible: i2c-arb-gpio-challenge
44	- our-claim-gpio: The GPIO that we use to claim the bus.
45	- their-claim-gpios: The GPIOs that the other sides use to claim the bus.
46	  Note that some implementations may only support a single other master.
47	- Standard I2C mux properties. See mux.txt in this directory.
48	- Single I2C child bus node at reg 0. See mux.txt in this directory.
49	
50	Optional properties:
51	- slew-delay-us: microseconds to wait for a GPIO to go high. Default is 10 us.
52	- wait-retry-us: we'll attempt another claim after this many microseconds.
53	    Default is 3000 us.
54	- wait-free-us: we'll give up after this many microseconds. Default is 50000 us.
55	
56	
57	Example:
58		i2c@12CA0000 {
59			compatible = "acme,some-i2c-device";
60			#address-cells = <1>;
61			#size-cells = <0>;
62		};
63	
64		i2c-arbitrator {
65			compatible = "i2c-arb-gpio-challenge";
66			#address-cells = <1>;
67			#size-cells = <0>;
68	
69			i2c-parent = <&{/i2c@12CA0000}>;
70	
71			our-claim-gpio = <&gpf0 3 1>;
72			their-claim-gpios = <&gpe0 4 1>;
73			slew-delay-us = <10>;
74			wait-retry-us = <3000>;
75			wait-free-us = <50000>;
76	
77			i2c@0 {
78				reg = <0>;
79				#address-cells = <1>;
80				#size-cells = <0>;
81	
82				i2c@52 {
83					// Normal I2C device
84				};
85			};
86		};
Hide Line Numbers
About Kernel Documentation Linux Kernel Contact Linux Resources Linux Blog

Information is copyright its respective author. All material is available from the Linux Kernel Source distributed under a GPL License. This page is provided as a free service by mjmwired.net.