Lines Matching +full:data +full:- +full:pins

19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .Nd GPIO I2C bit-banging device driver
35 .Bd -ragged -offset indent
45 .Bd -literal -offset indent
51 driver provides an IIC bit-banging interface using two GPIO pins for the
55 simulates an open collector kind of output when managing the pins on the
56 bus, even on systems which don't directly support configuring gpio pins
58 The pins are never driven to the logical value of '1'.
59 They are driven to '0' or switched to input mode (Hi-Z/tri-state), and
67 .Bl -tag -width ".Va hint.gpioiic.%d.atXXX"
72 Normally just gpiobus0 on systems with a single bank of gpio pins.
73 .It Va hint.gpioiic.%d.pins
74 This is a bitmask of the pins on the
77 bit-banging bus.
81 (any other bits - i.e., pins - will be ignored).
84 must be a child of the gpiobus, both gpio pins must be part of that bus.
87 .Va hint.gpioiic.%d.pins
93 .Va hint.gpioiic.%d.pins
103 conforms to the standard bindings document i2c/i2c-gpio.yaml.
109 .Bd -literal
112 		compatible = "i2c-gpio";
113 		pinctrl-names = "default";
114 		pinctrl-0 = <&pinctrl_gpioiic0>;
115 		scl-gpios = <&gpio1  5 GPIO_ACTIVE_HIGH>;
116 		sda-gpios = <&gpio7 11 GPIO_ACTIVE_HIGH>;
130 .Bl -tag -width ".Va compatible"
132 Should be set to "i2c-gpio".
134 .It Va scl-gpios Va sda-gpios
135 These properties indicate which GPIO pins should be used for clock
136 and data on the GPIO IIC bit-banging bus.
137 There is no requirement that the two pins belong to the same gpio controller.
138 .It Va pinctrl-names pinctrl-0
139 These properties may be required to configure the chosen pins as gpio
140 pins, unless the pins default to that state on your system.