Path: blob/master/Documentation/devicetree/bindings/iio/multiplexer/io-channel-mux.yaml
26309 views
# SPDX-License-Identifier: GPL-2.01%YAML 1.22---3$id: http://devicetree.org/schemas/iio/multiplexer/io-channel-mux.yaml#4$schema: http://devicetree.org/meta-schemas/core.yaml#56title: I/O channel multiplexer78maintainers:9- Peter Rosin <peda@axentia.se>1011description: |12If a multiplexer is used to select which hardware signal is fed to13e.g. an ADC channel, these bindings describe that situation.1415For each non-empty string in the channels property, an io-channel will be16created. The number of this io-channel is the same as the index into the list17of strings in the channels property, and also matches the mux controller18state. The mux controller state is described in19Documentation/devicetree/bindings/mux/mux-controller.yaml2021properties:2223compatible:24const: io-channel-mux2526io-channels:27maxItems: 128description: Channel node of the parent channel that has multiplexed input.2930io-channel-names:31const: parent3233mux-controls: true34mux-control-names: true3536channels:37$ref: /schemas/types.yaml#/definitions/non-unique-string-array38description:39List of strings, labeling the mux controller states. An empty40string for a state means that the channel is not available.4142settle-time-us:43default: 044description:45Time required for analog signals to settle after muxing.4647"#io-channel-cells":48const: 14950required:51- compatible52- io-channels53- io-channel-names54- mux-controls55- channels5657additionalProperties: false5859examples:60- |61#include <dt-bindings/gpio/gpio.h>62mux: mux-controller {63compatible = "gpio-mux";64#mux-control-cells = <0>;6566mux-gpios = <&pioA 0 GPIO_ACTIVE_HIGH>,67<&pioA 1 GPIO_ACTIVE_HIGH>;68};6970adc-mux {71compatible = "io-channel-mux";72io-channels = <&adc 0>;73io-channel-names = "parent";7475mux-controls = <&mux>;76channels = "sync", "in", "system-regulator";77};78...798081