Searched +full:i2c +full:- +full:arb +full:- +full:gpio +full:- +full:challenge (Results 1 – 5 of 5) sorted by relevance
1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause3 ---4 $id: http://devicetree.org/schemas/i2c/i2c-arb-gpio-challenge.yaml#5 $schema: http://devicetree.org/meta-schemas/core.yaml#7 title: GPIO-based I2C Arbitration Using a Challenge & Response Mechanism10 - Doug Anderson <dianders@chromium.org>11 - Peter Rosin <peda@axentia.se>14 This uses GPIO lines and a challenge & response mechanism to arbitrate who is15 the master of an I2C bus in a multimaster situation.18 standard I2C multi-master rules. Using GPIOs is generally useful in the case[all …]
1 # SPDX-License-Identifier: GPL-2.0-only3 # Multiplexer I2C chip drivers configuration6 menu "Multiplexer I2C Chip support"10 tristate "GPIO-based I2C arbitration"15 I2C multimaster arbitration scheme using GPIOs and a challenge &17 a GPIO.20 will be called i2c-arb-gpio-challenge.23 tristate "GPIO-based I2C multiplexer"27 GPIO based I2C multiplexer. This driver provides access to28 I2C busses connected through a MUX, which is controlled[all …]
1 # SPDX-License-Identifier: GPL-2.03 # Makefile for multiplexer I2C chip drivers.5 obj-$(CONFIG_I2C_ARB_GPIO_CHALLENGE) += i2c-arb-gpio-challenge.o7 obj-$(CONFIG_I2C_DEMUX_PINCTRL) += i2c-demux-pinctrl.o9 obj-$(CONFIG_I2C_MUX_GPIO) += i2c-mux-gpio.o10 obj-$(CONFIG_I2C_MUX_GPMUX) += i2c-mux-gpmux.o11 obj-$(CONFIG_I2C_MUX_LTC4306) += i2c-mux-ltc4306.o12 obj-$(CONFIG_I2C_MUX_MLXCPLD) += i2c-mux-mlxcpld.o13 obj-$(CONFIG_I2C_MUX_MULE) += i2c-mux-mule.o14 obj-$(CONFIG_I2C_MUX_PCA9541) += i2c-mux-pca9541.o[all …]
1 // SPDX-License-Identifier: GPL-2.08 #include <dt-bindings/gpio/gpio.h>9 #include <dt-bindings/clock/maxim,max77686.h>10 #include <dt-bindings/interrupt-controller/irq.h>11 #include <dt-bindings/input/input.h>12 #include <dt-bindings/sound/samsung-i2s.h>30 stdout-path = "serial3:115200n8";33 gpio-keys {34 compatible = "gpio-keys";35 pinctrl-names = "default";[all …]
2 I2C muxes and complex topologies5 There are a couple of reasons for building more complex I2C topologies6 than a straight-forward I2C bus with one adapter and one or more devices.16 from the I2C bus, at least most of the time, and sits behind a gate19 Several types of hardware components such as I2C muxes, I2C gates and I2C22 These components are represented as I2C adapter trees by Linux, where25 I2C transfers, and all adapters with a parent are part of an "i2c-mux"29 an I2C transfer on one of its child adapters. The mux driver can39 There are two variants of locking available to I2C muxes, they can be40 mux-locked or parent-locked muxes.[all …]