Searched +full:i2c +full:- +full:gpio (Results 1 – 25 of 311) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Bindings for GPIO bitbanged I2C
10 - Wolfram Sang <wolfram@the-dreams.de>
13 - $ref: /schemas/i2c/i2c-controller.yaml#
18 - const: i2c-gpio
20 sda-gpios:
22 gpio used for the sda signal, this should be flagged as
[all …]
|
| D | i2c-mux.txt | 1 Common i2c bus multiplexer/switch properties.
3 An i2c bus multiplexer/switch will have several child busses that are
4 numbered uniquely in a device dependent manner. The nodes for an i2c bus
8 - #address-cells = <1>;
9 This property is required if the i2c-mux child node does not exist.
11 - #size-cells = <0>;
12 This property is required if the i2c-mux child node does not exist.
14 - i2c-mux
15 For i2c multiplexers/switches that have child nodes that are a mixture
16 of both i2c child busses and other child nodes, the 'i2c-mux' subnode
[all …]
|
| D | i2c-mux-ltc4306.txt | 1 * Linear Technology / Analog Devices I2C bus switch
5 - compatible: Must contain one of the following.
7 - reg: The I2C address of the device.
11 - Standard I2C mux properties. See i2c-mux.txt in this directory.
12 - I2C child bus nodes. See i2c-mux.txt in this directory.
16 - enable-gpios: Reference to the GPIO connected to the enable input.
17 - i2c-mux-idle-disconnect: Boolean; if defined, forces mux to disconnect all
19 multiplexers on the bus and the devices behind them use same I2C addresses.
20 - gpio-controller: Marks the device node as a GPIO Controller.
21 - #gpio-cells: Should be two. The first cell is the pin number and
[all …]
|
| D | i2c-cbus-gpio.txt | 1 Device tree bindings for i2c-cbus-gpio driver
4 - compatible = "i2c-cbus-gpio";
5 - gpios: clk, dat, sel
6 - #address-cells = <1>;
7 - #size-cells = <0>;
10 - child nodes conforming to i2c bus binding
14 i2c@0 {
15 compatible = "i2c-cbus-gpio";
16 gpios = <&gpio 66 0 /* clk */
17 &gpio 65 0 /* dat */
[all …]
|
| D | i2c-imx.txt | 1 * Freescale Inter IC (I2C) and High Speed Inter IC (HS-I2C) for i.MX
4 - compatible :
5 - "fsl,imx1-i2c" for I2C compatible with the one integrated on i.MX1 SoC
6 - "fsl,imx21-i2c" for I2C compatible with the one integrated on i.MX21 SoC
7 - "fsl,vf610-i2c" for I2C compatible with the one integrated on Vybrid vf610 SoC
8 - reg : Should contain I2C/HS-I2C registers location and length
9 - interrupts : Should contain I2C/HS-I2C interrupt
10 - clocks : Should contain the I2C/HS-I2C clock specifier
13 - clock-frequency : Constains desired I2C/HS-I2C bus clock frequency in Hz.
15 - dmas: A list of two dma specifiers, one for each entry in dma-names.
[all …]
|
| D | i2c-mux-gpio.txt | 1 GPIO-based I2C Bus Mux
3 This binding describes an I2C bus multiplexer that uses GPIOs to
4 route the I2C signals.
6 +-----+ +-----+
8 +------------+ +-----+ +-----+
10 | | /--------+--------+
11 | +------+ | +------+ child bus A, on GPIO value set to 0
12 | | I2C |-|--| Mux |
13 | +------+ | +--+---+ child bus B, on GPIO value set to 1
14 | | | \----------+--------+--------+
[all …]
|
| D | i2c-arb.txt | 1 Common i2c arbitration bus properties.
3 - i2c-arb child node
5 Required properties for the i2c-arb child node:
6 - #address-cells = <1>;
7 - #size-cells = <0>;
9 Optional properties for i2c-arb child node:
10 - Child nodes conforming to i2c bus binding
16 An NXP pca9541 I2C bus master selector at address 0x74
17 with a NXP pca8574 GPIO expander attached.
24 i2c-arb {
[all …]
|
| D | i2c-arb-gpio-challenge.txt | 1 GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
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.
7 the standard I2C multi-master rules. Using GPIOs is generally useful in
12 * It is nonstandard (not using standard I2C multimaster)
14 problems (hard to tell if i2c issues were caused by one master, another, or
21 others can see. These are all active low with pull-ups enabled. We'll
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
43 - compatible: i2c-arb-gpio-challenge
[all …]
|
| D | i2c-s3c2410.txt | 1 * Samsung's I2C controller
3 The Samsung's I2C controller is used to interface with I2C devices.
6 - compatible: value should be either of the following.
7 (a) "samsung, s3c2410-i2c", for i2c compatible with s3c2410 i2c.
8 (b) "samsung, s3c2440-i2c", for i2c compatible with s3c2440 i2c.
9 (c) "samsung, s3c2440-hdmiphy-i2c", for s3c2440-like i2c used
11 (d) "samsung, exynos5-sata-phy-i2c", for s3c2440-like i2c used as
13 - reg: physical base address of the controller and length of memory mapped
15 - interrupts: interrupt number to the cpu.
16 - samsung,i2c-sda-delay: Delay (in ns) applied to data line (SDA) edges.
[all …]
|
| D | i2c-pxa-pci-ce4100.txt | 1 CE4100 I2C
2 ----------
4 CE4100 has one PCI device which is described as the I2C-Controller. This
5 PCI device has three PCI-bars, each bar contains a complete I2C
6 controller. So we have a total of three independent I2C-Controllers
8 The driver is probed via the PCI-ID and is gathering the information of
10 Grant Likely recommended to use the ranges property to map the PCI-Bar
12 of the specific I2C controller. This were his exact words:
22 non-zero if you had 2 or more devices mapped off
30 ------------------------------------------------
[all …]
|
| /Documentation/i2c/muxes/ |
| D | i2c-mux-gpio.rst | 2 Kernel driver i2c-mux-gpio
8 -----------
10 i2c-mux-gpio is an i2c mux driver providing access to I2C bus segments
11 from a master I2C bus and a hardware MUX controlled through GPIO pins.
15 ---------- ---------- Bus segment 1 - - - - -
16 | | SCL/SDA | |-------------- | |
17 | |------------| |
19 | Linux | GPIO 1..N | MUX |--------------- Devices
20 | |------------| | | |
22 | | | |---------------| |
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gateworks,pld-gpio.txt | 1 Gateworks PLD GPIO controller bindings
3 The GPIO controller should be a child node on an I2C bus,
4 see: i2c/i2c.txt for details.
7 - compatible: Should be "gateworks,pld-gpio"
8 - reg: I2C slave address
9 - gpio-controller: Marks the device node as a GPIO controller.
10 - #gpio-cells: Should be <2>. The first cell is the gpio number and
16 compatible = "gateworks,pld-gpio";
18 gpio-controller;
19 #gpio-cells = <2>;
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | sbs,sbs-manager.txt | 1 Binding for sbs-manager
4 - compatible: "<vendor>,<part-number>", "sbs,sbs-charger" as fallback. The part
7 - reg: integer, i2c address of the device. Should be <0xa>.
9 - gpio-controller: Marks the port as GPIO controller.
10 See "gpio-specifier" in .../devicetree/bindings/gpio/gpio.txt.
11 - #gpio-cells: Should be <2>. The first cell is the pin number, the second cell
13 See "gpio-specifier" in .../devicetree/bindings/gpio/gpio.txt.
15 From OS view the device is basically an i2c-mux used to communicate with up to
17 behaviour. So standard i2c-mux nodes can be used to register up to four slave
23 compatible = "lltc,ltc1760", "sbs,sbs-manager";
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | ak4118.txt | 3 This device supports I2C mode.
7 - compatible : "asahi-kasei,ak4118"
8 - reg : The I2C address of the device for I2C
9 - reset-gpios: A GPIO specifier for the reset pin
10 - irq-gpios: A GPIO specifier for the IRQ pin
14 &i2c {
16 #sound-dai-cells = <0>;
17 compatible = "asahi-kasei,ak4118";
19 reset-gpios = <&gpio 0 GPIO_ACTIVE_LOW>
20 irq-gpios = <&gpio 1 GPIO_ACTIVE_HIGH>;
|
| D | wm8804.txt | 3 This device supports both I2C and SPI (configured with pin strapping
8 - compatible : "wlf,wm8804"
10 - reg : the I2C address of the device for I2C, the chip select
13 - PVDD-supply, DVDD-supply : Power supplies for the device, as covered
18 - wlf,reset-gpio: A GPIO specifier for the GPIO controlling the reset pin
|
| D | cs4271.txt | 3 This driver supports both the I2C and the SPI bus.
7 - compatible: "cirrus,cs4271"
10 Documentation/devicetree/bindings/spi/spi-bus.txt
12 Required properties on I2C:
14 - reg: the i2c address
19 - reset-gpio: a GPIO spec to define which pin is connected to the chip's
21 - cirrus,amuteb-eq-bmutec: When given, the Codec's AMUTEB=BMUTEC flag
23 - cirrus,enable-soft-reset:
25 line is de-asserted. That also means that clocks cannot be changed
27 a complete re-initialization of all registers.
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 2 Subsystem drivers using GPIO
5 Note that standard kernel drivers exist for common GPIO tasks and will provide
6 the right in-kernel and userspace APIs/ABIs for the job, and that these
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
14 i.e. a LED will turn on/off in response to a GPIO line going high or low
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
21 GPIO line cannot generate interrupts, so it needs to be periodically polled
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-mcp23s08.txt | 2 8-/16-bit I/O expander with serial interface (I2C/SPI)
5 - compatible : Should be
6 - "mcp,mcp23s08" (DEPRECATED) for 8 GPIO SPI version
7 - "mcp,mcp23s17" (DEPRECATED) for 16 GPIO SPI version
8 - "mcp,mcp23008" (DEPRECATED) for 8 GPIO I2C version or
9 - "mcp,mcp23017" (DEPRECATED) for 16 GPIO I2C version of the chip
11 - "microchip,mcp23s08" for 8 GPIO SPI version
12 - "microchip,mcp23s17" for 16 GPIO SPI version
13 - "microchip,mcp23s18" for 16 GPIO SPI version
14 - "microchip,mcp23008" for 8 GPIO I2C version or
[all …]
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | pixcir_i2c_ts.txt | 1 * Pixcir I2C touchscreen controllers
4 - compatible: must be "pixcir,pixcir_ts" or "pixcir,pixcir_tangoc"
5 - reg: I2C address of the chip
6 - interrupts: interrupt to which the chip is connected
7 - attb-gpio: GPIO connected to the ATTB line of the chip
8 - touchscreen-size-x: horizontal resolution of touchscreen (in pixels)
9 - touchscreen-size-y: vertical resolution of touchscreen (in pixels)
12 - reset-gpios: GPIO connected to the RESET line of the chip
13 - enable-gpios: GPIO connected to the ENABLE line of the chip
14 - wake-gpios: GPIO connected to the WAKE line of the chip
[all …]
|
| D | eeti.txt | 4 - compatible: should be "eeti,exc3000-i2c"
5 - reg: I2C address of the chip. Should be set to <0xa>
6 - interrupts: interrupt to which the chip is connected
9 - attn-gpios: A handle to a GPIO to check whether interrupt is still
11 support for level-triggered IRQs.
16 - touchscreen-inverted-x
17 - touchscreen-inverted-y
18 - touchscreen-swapped-x-y
22 i2c-master {
24 compatible = "eeti,exc3000-i2c";
[all …]
|
| /Documentation/devicetree/bindings/mux/ |
| D | gpio-mux.txt | 1 GPIO-based multiplexer controller bindings
3 Define what GPIO pins are used to control a multiplexer. Or several
7 - compatible : "gpio-mux"
8 - mux-gpios : list of gpios used to control the multiplexer, least
10 - #mux-control-cells : <0>
11 * Standard mux-controller bindings as decribed in mux-controller.txt
14 - idle-state : if present, the state the mux will have when idle. The
18 multiplexer GPIO pins, where the first pin is the least significant
23 mux: mux-controller {
24 compatible = "gpio-mux";
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | sff,sfp.txt | 1 Small Form Factor (SFF) Committee Small Form-factor Pluggable (SFP)
6 - compatible : must be one of
10 - i2c-bus : phandle of an I2C bus controller for the SFP two wire serial
15 - mod-def0-gpios : GPIO phandle and a specifier of the MOD-DEF0 (AKA Mod_ABS)
16 module presence input gpio signal, active (module absent) high. Must
19 - los-gpios : GPIO phandle and a specifier of the Receiver Loss of Signal
20 Indication input gpio signal, active (signal lost) high
22 - tx-fault-gpios : GPIO phandle and a specifier of the Module Transmitter
23 Fault input gpio signal, active (fault condition) high
25 - tx-disable-gpios : GPIO phandle and a specifier of the Transmitter Disable
[all …]
|
| /Documentation/devicetree/bindings/display/tilcdc/ |
| D | tfp410.txt | 1 Device-Tree bindings for tilcdc DRM TFP410 output driver
4 - compatible: value should be "ti,tilcdc,tfp410".
5 - i2c: the phandle for the i2c device to use for DDC
8 - pinctrl-names, pinctrl-0: the pincontrol settings to configure
10 - powerdn-gpio: the powerdown GPIO, pulled low to power down the
17 i2c = <&i2c2>;
18 pinctrl-names = "default";
19 pinctrl-0 = <&bone_dvi_cape_dvi_00A1_pins>;
20 powerdn-gpio = <&gpio2 31 0>;
|
| /Documentation/devicetree/bindings/extcon/ |
| D | extcon-ptn5150.txt | 3 PTN5150 is a small thin low power CC logic chip supporting the USB Type-C
5 It is interfaced to the host controller using an I2C interface.
8 - compatible: should be "nxp,ptn5150"
9 - reg: specifies the I2C slave address of the device
10 - int-gpio: should contain a phandle and GPIO specifier for the GPIO pin
12 - vbus-gpio: should contain a phandle and GPIO specifier for the GPIO pin which
14 - pinctrl-names : a pinctrl state named "default" must be defined.
15 - pinctrl-0 : phandle referencing pin configuration of interrupt and vbus
22 int-gpio = <&msmgpio 78 GPIO_ACTIVE_HIGH>;
23 vbus-gpio = <&msmgpio 148 GPIO_ACTIVE_HIGH>;
[all …]
|
| /Documentation/devicetree/bindings/board/ |
| D | fsl-board.txt | 10 - compatible : Should be "fsl,<board>-bcsr"
11 - reg : Offset and length of the register set for the device
16 compatible = "fsl,mpc8360mds-bcsr";
20 * Freescale on-board FPGA
22 This is the memory-mapped registers for on board FPGA.
25 - compatible: should be a board-specific string followed by a string
27 "fsl,<board>-fpga", "fsl,fpga-pixis", or
28 "fsl,<board>-fpga", "fsl,fpga-qixis"
29 - reg: should contain the address and the length of the FPGA register set.
32 - interrupts: should specify event (wakeup) IRQ.
[all …]
|
12345678910>>...13