Searched +full:spi +full:- +full:mux (Results 1 – 25 of 39) sorted by relevance
12
| /Documentation/devicetree/bindings/spi/ |
| D | spi-mux.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/spi-mux.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Generic SPI Multiplexer 10 This binding describes a SPI bus multiplexer to route the SPI chip select 11 signals. This can be used when you need more devices than the SPI controller 13 setting of the multiplexer to a channel needs to be done by a specific SPI mux 16 MOSI /--------------------------------+--------+--------+--------\ 17 MISO |/------------------------------+|-------+|-------+|-------\| [all …]
|
| D | snps,dw-apb-ssi.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 4 $id: http://devicetree.org/schemas/spi/snps,dw-apb-ssi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Mark Brown <broonie@kernel.org> 13 - $ref: spi-controller.yaml# 14 - if: 19 - mscc,ocelot-spi 20 - mscc,jaguar2-spi 25 - if: [all …]
|
| D | samsung,spi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/samsung,spi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Samsung S3C/S5P/Exynos SoC SPI controller 10 - Krzysztof Kozlowski <krzk@kernel.org> 13 All the SPI controller nodes should be represented in the aliases node using 14 the following format 'spi{n}' where n is a unique number for the alias. 19 - enum: 20 - google,gs101-spi [all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | lantiq,pinctrl-falcon.txt | 4 - compatible: "lantiq,pinctrl-falcon" 5 - reg: Should contain the physical address and length of the gpio/pinmux 8 Please refer to pinctrl-bindings.txt in this directory for details of the 15 mux function to select on those group(s), and two pin configuration parameters: 16 pull-up and open-drain 22 other words, a subnode that lists a mux function but no pin configuration 25 information about e.g. the mux function. 29 Definition of mux function groups: 31 Required subnode-properties: 32 - lantiq,groups : An array of strings. Each string contains the name of a group. [all …]
|
| D | brcm,ns-pinmux.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/brcm,ns-pinmux.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Broadcom Northstar pins mux controller 10 - Rafał Miłecki <rafal@milecki.pl> 14 mux controller. This binding allows describing mux controller and listing 23 - brcm,bcm4708-pinmux 24 - brcm,bcm4709-pinmux 25 - brcm,bcm53012-pinmux [all …]
|
| D | lantiq,pinctrl-xway.txt | 4 - compatible: "lantiq,<chip>-pinctrl", where <chip> is: 10 - reg: Should contain the physical address and length of the gpio/pinmux 13 Please refer to pinctrl-bindings.txt in this directory for details of the 20 mux function to select on those group(s), and two pin configuration parameters: 21 pull-up and open-drain 27 other words, a subnode that lists a mux function but no pin configuration 30 information about e.g. the mux function. 34 Definition of mux function groups: 36 Required subnode-properties: 37 - lantiq,groups : An array of strings. Each string contains the name of a group. [all …]
|
| D | mediatek,mt7986-pinctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/mediatek,mt7986-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Sean Wang <sean.wang@kernel.org> 18 - mediatek,mt7986a-pinctrl 19 - mediatek,mt7986b-pinctrl 25 reg-names: 27 - const: gpio 28 - const: iocfg_rt [all …]
|
| D | mediatek,mt7981-pinctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/mediatek,mt7981-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Daniel Golle <daniel@makrotopia.org> 18 - mediatek,mt7981-pinctrl 24 reg-names: 26 - const: gpio 27 - const: iocfg_rt 28 - const: iocfg_rm [all …]
|
| D | pinctrl-vt8500.txt | 1 VIA VT8500 and Wondermedia WM8xxx-series pinmux/gpio controller 4 either a GPIO in, GPIO out or as an alternate function (I2C, SPI etc). 7 - compatible: "via,vt8500-pinctrl", "wm,wm8505-pinctrl", "wm,wm8650-pinctrl", 8 "wm8750-pinctrl" or "wm,wm8850-pinctrl" 9 - reg: Should contain the physical address of the module's registers. 10 - interrupt-controller: Marks the device node as an interrupt controller. 11 - #interrupt-cells: Should be two. 12 - gpio-controller: Marks the device node as a GPIO controller. 13 - #gpio-cells : Should be two. The first cell is the pin number and the 15 bit 0 - active low [all …]
|
| D | brcm,nsp-pinmux.txt | 3 The NSP IOMUX controller supports group based mux configuration. In 7 - compatible: 8 Must be "brcm,nsp-pinmux" 10 - reg: 15 - function: 16 The mux function to select 18 - groups: 22 Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt 27 compatible = "brcm,nsp-pinmux"; 32 pinctrl-names = "default"; [all …]
|
| D | sunplus,sp7021-pinctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/pinctrl/sunplus,sp7021-pinctrl.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Dvorkin Dmitry <dvorkin@tibbo.com> 12 - Wells Lu <wellslutw@gmail.com> 16 refer to pinctrl-bindings.txt in this directory for details of the common 23 (1) function-group pins: 24 Ex 1 (SPI-NOR flash): 25 If control-field SPI_FLASH_SEL is set to 1, GPIO 83, 84, 86 and 87 [all …]
|
| D | ralink,rt2880-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/ralink,rt2880-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 20 const: ralink,rt2880-pinctrl 23 '-pins$': 28 '^(.*-)?pinmux$': 31 $ref: pinmux-node.yaml# [all …]
|
| D | ralink,rt305x-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/ralink,rt305x-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 20 const: ralink,rt305x-pinctrl 23 '-pins$': 28 '^(.*-)?pinmux$': 31 $ref: pinmux-node.yaml# [all …]
|
| D | ralink,rt5350-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/ralink,rt5350-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 20 const: ralink,rt5350-pinctrl 23 '-pins$': 28 '^(.*-)?pinmux$': 31 $ref: pinmux-node.yaml# [all …]
|
| D | mediatek,mt7620-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/mediatek,mt7620-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 20 const: ralink,mt7620-pinctrl 23 '-pins$': 28 '^(.*-)?pinmux$': 31 $ref: pinmux-node.yaml# [all …]
|
| D | mediatek,mt7621-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/mediatek,mt7621-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 20 const: ralink,mt7621-pinctrl 23 '-pins$': 28 '^(.*-)?pinmux$': 31 $ref: pinmux-node.yaml# [all …]
|
| D | ralink,rt3352-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/ralink,rt3352-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 20 const: ralink,rt3352-pinctrl 23 '-pins$': 28 '^(.*-)?pinmux$': 31 $ref: pinmux-node.yaml# [all …]
|
| D | pinmux-node.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/pinmux-node.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Linus Walleij <linus.walleij@linaro.org> 34 spi { 50 For cases like this, the pin controller driver may use pinctrl-pin-array helper 55 #pinctrl-cells = <2>; 58 pinctrl-pin-array = < 67 Above #pinctrl-cells specifies the number of value cells in addition to the [all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,gsbi.yaml | 1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Andy Gross <agross@kernel.org> 11 - Bjorn Andersson <bjorn.andersson@linaro.org> 12 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 16 representing a serial sub-node device that is mux'd as part of the GSBI 21 devices. These serial devices can be a QCOM UART, I2C controller, spi 26 const: qcom,gsbi-v1.0.0 28 '#address-cells': [all …]
|
| /Documentation/devicetree/bindings/mux/ |
| D | adi,adgs1408.txt | 1 Bindings for Analog Devices ADGS1408/1409 8:1/Dual 4:1 Mux 4 - compatible : Should be one of 7 * Standard mux-controller bindings as described in mux-controller.yaml 10 - gpio-controller : if present, #gpio-cells is required. 11 - #gpio-cells : should be <2> 12 - First cell is the GPO line number, i.e. 0 to 3 14 - Second cell is used to specify active high (0) 18 - idle-state : if present, the state that the mux controller will have 28 * One mux controller. 29 * Mux state set to idle as is (no idle-state declared) [all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | ti,ads131e08.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Texas Instruments ADS131E0x 4-, 6- and 8-Channel ADCs 10 - Jonathan Cameron <jic23@kernel.org> 14 24-bit, delta-sigma, analog-to-digital converters (ADCs) with a 15 built-in programmable gain amplifier (PGA), internal reference 17 The communication with ADC chip is via the SPI bus (mode 1). 24 - ti,ads131e04 25 - ti,ads131e06 [all …]
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 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, 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 24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with 29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from 31 off/on, for an actual PWM waveform, see pwm-gpio below.) 33 - pwm-gpio: drivers/pwm/pwm-gpio.c is used to toggle a GPIO with a high [all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | ti,lmk04832.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Liam Beguin <liambeguin@gmail.com> 21 - ti,lmk04832 26 '#address-cells': 29 '#size-cells': 32 '#clock-cells': 35 spi-max-frequency: 40 - description: PLL2 reference clock. [all …]
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | adi,ltc2672.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Michael Hennerich <michael.hennerich@analog.com> 11 - Kim Seer Paller <kimseer.paller@analog.com> 14 Analog Devices LTC2672 5 channel, 12-/16-Bit, 300mA DAC 15 https://www.analog.com/media/en/technical-documentation/data-sheets/ltc2672.pdf 20 - adi,ltc2672 25 spi-max-frequency: 28 vcc-supply: [all …]
|
| /Documentation/driver-api/ |
| D | pin-control.rst | 9 - Enumerating and naming controllable pins 11 - Multiplexing of pins, pads, fingers (etc) see below for details 13 - Configuration of pins, pads, fingers (etc), such as software-controlled 14 biasing and driving mode specific pins, such as pull-up, pull-down, open drain, 17 Top-level interface 22 - A PIN CONTROLLER is a piece of hardware, usually a set of registers, that 26 - PINS are equal to pads, fingers, balls or whatever packaging input or 30 be sparse - i.e. there may be gaps in the space with numbers where no 60 .. code-block:: c 97 See ``arch/arm/mach-ux500/Kconfig`` for an example. [all …]
|
12