Searched +full:i2c +full:- +full:mux +full:- +full:idle +full:- +full:disconnect (Results 1 – 4 of 4) sorted by relevance
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-pca954x.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mux-pca954x.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NXP PCA954x I2C and compatible bus switches
10 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
13 The NXP PCA954x and compatible devices are I2C bus
23 - enum:
24 - maxim,max7356
25 - maxim,max7357
[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.yaml in this directory.
12 - I2C child bus nodes. See i2c-mux.yaml 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
18 children in idle state. This is necessary for example, if there are several
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.
[all …]
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mux/mux-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Peter Rosin <peda@axentia.se>
13 A multiplexer (or mux) controller will have one, or several, consumer devices
14 that uses the mux controller. Thus, a mux controller can possibly control
16 multiplexer needed by each consumer, but a single mux controller can of course
19 A mux controller provides a number of states to its consumers, and the state
20 space is a simple zero-based enumeration. I.e. 0-1 for a 2-way multiplexer,
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-i2c-devices-pca954x | 1 What: /sys/bus/i2c/.../idle_state
6 Value that exists only for mux devices that can be
8 idle. Possible values:
11 -2 disconnect on idle, i.e. deselect the last used
14 device on another mux on the same parent bus.
15 -1 leave the mux as-is, which is the most optimal
16 setting in terms of I2C operations and is the
18 0..<nchans> set the mux to a predetermined channel,
|