| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7606.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Beniamin Bia <beniamin.bia@analog.com>
11 - Stefan Popa <stefan.popa@analog.com>
15 https://www.analog.com/media/en/technical-documentation/data-sheets/ad7606_7606-6_7606-4.pdf
16 https://www.analog.com/media/en/technical-documentation/data-sheets/AD7606B.pdf
17 https://www.analog.com/media/en/technical-documentation/data-sheets/AD7616.pdf
22 - adi,ad7605-4
23 - adi,ad7606-8
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | atmel-usart.txt | 4 - compatible: Should be one of the following:
5 - "atmel,at91rm9200-usart"
6 - "atmel,at91sam9260-usart"
7 - "microchip,sam9x60-usart"
8 - "atmel,at91rm9200-dbgu", "atmel,at91rm9200-usart"
9 - "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart"
10 - "microchip,sam9x60-dbgu", "microchip,sam9x60-usart"
11 - reg: Should contain registers location and length
12 - interrupts: Should contain interrupt
13 - clock-names: tuple listing input clock names.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/spi/ |
| D | spi-bus.txt | 9 - compatible - Name of SPI bus controller following generic names
14 - #address-cells - number of cells required to define a chip select
16 - #size-cells - should be zero.
19 - spi-slave - Empty property.
25 flexible and non-standardized, it is left out of this binding with the
31 - cs-gpios - gpios chip select.
32 - num-cs - total number of chipselects.
34 If cs-gpios is used the number of chip selects will be increased automatically
35 with max(cs-gpios > hw cs).
37 So if for example the controller has 2 CS lines, and the cs-gpios
[all …]
|
| /kernel/linux/linux-5.10/drivers/bus/ |
| D | ts-nbus.c | 2 * NBUS driver for TS-4600 based boards
4 * Copyright (c) 2016 - Savoir-faire Linux
11 * This driver implements a GPIOs bit-banged bus, called the NBUS by Technologic
13 * TS-4600 SoM.
24 #include <linux/ts-nbus.h>
33 struct gpio_descs *data; member
43 * request all gpios required by the bus.
48 ts_nbus->data = devm_gpiod_get_array(&pdev->dev, "ts,data", in ts_nbus_init_pdata()
50 if (IS_ERR(ts_nbus->data)) { in ts_nbus_init_pdata()
51 dev_err(&pdev->dev, "failed to retrieve ts,data-gpio from dts\n"); in ts_nbus_init_pdata()
[all …]
|
| /kernel/linux/linux-4.19/drivers/bus/ |
| D | ts-nbus.c | 2 * NBUS driver for TS-4600 based boards
4 * Copyright (c) 2016 - Savoir-faire Linux
11 * This driver implements a GPIOs bit-banged bus, called the NBUS by Technologic
13 * TS-4600 SoM.
24 #include <linux/ts-nbus.h>
33 struct gpio_descs *data; member
43 * request all gpios required by the bus.
48 ts_nbus->data = devm_gpiod_get_array(&pdev->dev, "ts,data", in ts_nbus_init_pdata()
50 if (IS_ERR(ts_nbus->data)) { in ts_nbus_init_pdata()
51 dev_err(&pdev->dev, "failed to retrieve ts,data-gpio from dts\n"); in ts_nbus_init_pdata()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/bridge/ |
| D | thine,thc63lvd1024.txt | 2 -------------------------------------------
5 to parallel data outputs. The chip supports single/dual input/output modes,
8 Single or dual operation mode, output data mapping and DDR output modes are
12 - compatible: Shall be "thine,thc63lvd1024"
13 - vcc-supply: Power supply for TTL output, TTL CLOCKOUT signal, LVDS input,
17 - powerdown-gpios: Power down GPIO signal, pin name "/PDWN". Active low
18 - oe-gpios: Output enable GPIO signal, pin name "OE". Active high
24 - port@0: First LVDS input port
25 - port@2: First digital CMOS/TTL parallel output
28 - port@1: Second LVDS input port
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 4 1) gpios property
5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
9 for compatibility reasons (resolving to the "gpios" property), it is not allowed
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
15 cases should they contain more than one. If your device uses several GPIOs with
17 meaningful name. The only case where an array of GPIOs is accepted is when
18 several GPIOs serve the same function (e.g. a parallel data line).
20 The exact purpose of each gpios property must be documented in the device tree
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/serial/ |
| D | atmel-usart.txt | 4 - compatible: Should be "atmel,<chip>-usart" or "atmel,<chip>-dbgu"
5 The compatible <chip> indicated will be the first SoC to support an
7 For the dbgu UART, use "atmel,<chip>-dbgu", "atmel,<chip>-usart"
8 - reg: Should contain registers location and length
9 - interrupts: Should contain interrupt
10 - clock-names: tuple listing input clock names.
12 - clocks: phandles to input clocks.
15 - atmel,use-dma-rx: use of PDC or DMA for receiving data
16 - atmel,use-dma-tx: use of PDC or DMA for transmitting data
17 - {rts,cts,dtr,dsr,rng,dcd}-gpios: specify a GPIO for RTS/CTS/DTR/DSR/RI/DCD line respectively.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 4 1) gpios property
5 -----------------
7 Nodes that makes use of GPIOs should specify them using one or more
8 properties, each containing a 'gpio-list':
10 gpio-list ::= <single-gpio> [gpio-list]
11 single-gpio ::= <gpio-phandle> <gpio-specifier>
12 gpio-phandle : phandle to gpio controller node
13 gpio-specifier : Array of #gpio-cells specifying specific gpio
16 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
17 of this GPIO for the device. While a non-existent <name> is considered valid
[all …]
|
| /kernel/linux/linux-4.19/drivers/spi/ |
| D | spi-ppc4xx.c | 44 #include <asm/dcr-regs.h>
46 /* bits in mode register - bit 0 is MSb */
49 * SPI_PPC4XX_MODE_SCP = 0 means "data latched on trailing edge of clock"
50 * SPI_PPC4XX_MODE_SCP = 1 means "data latched on leading edge of clock"
59 * SPI_PPC4XX_MODE_RD = 0 means "MSB first" - this is the normal mode
60 * SPI_PPC4XX_MODE_RD = 1 means "LSB first" - this is bit-reversed mode
108 * CDM = (OPBCLK/4*SCPClkOut) - 1
114 /* SPI Controller driver's private data. */
116 /* bitbang has to be first */
129 /* data buffers */
[all …]
|
| D | spi-fsl-spi.c | 23 #include <linux/dma-mapping.h>
42 #include "spi-fsl-lib.h"
43 #include "spi-fsl-cpm.h"
44 #include "spi-fsl-spi.h"
64 .data = &of_fsl_spi_fsl_config,
68 .data = &of_fsl_spi_grlib_config,
78 if (dev->of_node) { in fsl_spi_get_type()
79 match = of_match_node(of_fsl_spi_match, dev->of_node); in fsl_spi_get_type()
80 if (match && match->data) in fsl_spi_get_type()
81 return ((struct fsl_spi_match_data *)match->data)->type; in fsl_spi_get_type()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/ |
| D | exynos-dw-mshc.txt | 7 by synopsys-dw-mshc.txt and the properties used by the Samsung Exynos specific
13 - "samsung,exynos4210-dw-mshc": for controllers with Samsung Exynos4210
15 - "samsung,exynos4412-dw-mshc": for controllers with Samsung Exynos4412
17 - "samsung,exynos5250-dw-mshc": for controllers with Samsung Exynos5250
19 - "samsung,exynos5420-dw-mshc": for controllers with Samsung Exynos5420
21 - "samsung,exynos7-dw-mshc": for controllers with Samsung Exynos7
23 - "samsung,exynos7-dw-mshc-smu": for controllers with Samsung Exynos7
26 * samsung,dw-mshc-ciu-div: Specifies the divider value for the card interface
30 * samsung,dw-mshc-sdr-timing: Specifies the value of CIU clock phase shift value
32 data rate mode operation. Refer notes below for the order of the cells and the
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mmc/ |
| D | exynos-dw-mshc.txt | 7 by synopsys-dw-mshc.txt and the properties used by the Samsung Exynos specific
13 - "samsung,exynos4210-dw-mshc": for controllers with Samsung Exynos4210
15 - "samsung,exynos4412-dw-mshc": for controllers with Samsung Exynos4412
17 - "samsung,exynos5250-dw-mshc": for controllers with Samsung Exynos5250
19 - "samsung,exynos5420-dw-mshc": for controllers with Samsung Exynos5420
21 - "samsung,exynos7-dw-mshc": for controllers with Samsung Exynos7
23 - "samsung,exynos7-dw-mshc-smu": for controllers with Samsung Exynos7
26 * samsung,dw-mshc-ciu-div: Specifies the divider value for the card interface
30 * samsung,dw-mshc-sdr-timing: Specifies the value of CIU clock phase shift value
32 data rate mode operation. Refer notes below for the order of the cells and the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/ |
| D | thine,thc63lvd1024.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo+renesas@jmondi.org>
11 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
15 streams to parallel data outputs. The chip supports single/dual input/output
19 Single or dual operation mode, output data mapping and DDR output modes are
33 The device can operate in single-link mode or dual-link mode. In
34 single-link mode, all pixels are received on port@0, and port@1 shall not
35 contain any endpoint. In dual-link mode, even-numbered pixels are
[all …]
|
| /kernel/linux/linux-5.10/include/linux/gpio/ |
| D | driver.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
12 #include <linux/pinctrl/pinconf-generic.h>
29 * struct gpio_irq_chip - GPIO interrupt controller
66 * If non-NULL, will be set as the parent of this GPIO interrupt
78 * hardware IRQs correspond to the GPIO index 0..ngpio-1 (see the
86 * HWIRQ, return -EINVAL, but also make sure to fill in @valid_mask and
101 * &gpiochip_populate_parent_fwspec_twocell will be used. A four-cell
172 * Data associated, and passed to, the handler for the parent
219 * bits from 0..(ngpios-1) set to "1" as in valid. The callback can
230 * If not %NULL holds bitmask of GPIOs which are valid to be included
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/w1/ |
| D | w1-gpio.txt | 1 w1-gpio devicetree bindings
5 - compatible: "w1-gpio"
6 - gpios: one or two GPIO specs:
7 - the first one is used as data I/O pin
8 - the second one is optional. If specified, it is used as
13 - linux,open-drain: if specified, the data pin is considered in
14 open-drain mode.
21 compatible = "w1-gpio";
22 gpios = <&gpio 0 GPIO_ACTIVE_HIGH>;
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/w1/ |
| D | w1-gpio.txt | 1 w1-gpio devicetree bindings
5 - compatible: "w1-gpio"
6 - gpios: one or two GPIO specs:
7 - the first one is used as data I/O pin
8 - the second one is optional. If specified, it is used as
13 - linux,open-drain: if specified, the data pin is considered in
14 open-drain mode.
21 compatible = "w1-gpio";
22 gpios = <&gpio 0 GPIO_ACTIVE_HIGH>;
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
18 which GPIOs. Drivers can be written generically, so that board setup code
19 passes such pin configuration data to drivers.
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
24 provide GPIOs; multifunction chips like power managers, and audio codecs
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
30 The exact capabilities of GPIOs vary between systems. Common options:
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
[all …]
|
| D | board.rst | 5 This document explains how GPIOs can be assigned to given devices and functions.
7 Note that it only applies to the new descriptor-based interface. For a
8 description of the deprecated integer-based GPIO interface please refer to
9 gpio-legacy.txt (actually, there is no real mapping possible with the old
15 Kconfig. Then, how GPIOs are mapped depends on what the platform uses to
17 tree, ACPI, and platform data.
20 -----------
21 GPIOs can easily be mapped to devices and functions in the device tree. The
22 exact way to do it depends on the GPIO controller providing the GPIOs, see the
25 GPIOs mappings are defined in the consumer device's node, in a property named
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/gpio/ |
| D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
18 which GPIOs. Drivers can be written generically, so that board setup code
19 passes such pin configuration data to drivers.
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
24 provide GPIOs; multifunction chips like power managers, and audio codecs
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
30 The exact capabilities of GPIOs vary between systems. Common options:
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
[all …]
|
| /kernel/linux/linux-4.19/include/linux/gpio/ |
| D | driver.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
12 #include <linux/pinctrl/pinconf-generic.h>
25 * struct gpio_irq_chip - GPIO interrupt controller
85 * Data associated, and passed to, the handler for the parent
136 * If not %NULL holds bitmask of GPIOs which are valid to be included
142 * @first:
147 unsigned int first; member
157 * struct gpio_chip - abstract a GPIO controller
159 * number or the name of the SoC IP-block implementing it.
161 * @parent: optional parent device providing the GPIOs
[all …]
|
| /kernel/linux/linux-4.19/arch/mips/include/asm/mach-pmcs-msp71xx/ |
| D | msp_gpio_macros.h | 3 * Macros for external SMP-safe access to the PMC MSP71xx reference
6 * Copyright 2010 PMC-Sierra, Inc.
19 * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
41 /* -- GPIO Enumerations -- */
45 MSP_GPIO_NONE, /* Special - Means pin is out of range */
46 MSP_GPIO_TOGGLE, /* Special - Sets pin to opposite */
60 /* -- Static Tables -- */
62 /* Maps pins to data register */
64 /* GPIO 0 and 1 on the first register */
73 /* GPIO 16 - 23 on the first strange EXTENDED register */
[all …]
|
| /kernel/linux/linux-5.10/include/linux/platform_data/ |
| D | pcf857x.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
6 * struct pcf857x_platform_data - data to set up pcf857x driver
7 * @gpio_base: number of the chip's first GPIO
8 * @n_latch: optional bit-inverse of initial register value; if
11 * @setup: optional callback issued once the GPIOs are valid
12 * @teardown: optional callback issued before the GPIOs are invalidated
20 * The @setup callback may be used with the kind of board-specific glue
21 * which hands the (now-valid) GPIOs to other drivers, or which puts
22 * devices in their initial states using these GPIOs.
24 * These GPIO chips are only "quasi-bidirectional"; read the chip specs
|
| /kernel/linux/linux-4.19/include/linux/platform_data/ |
| D | pcf857x.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
6 * struct pcf857x_platform_data - data to set up pcf857x driver
7 * @gpio_base: number of the chip's first GPIO
8 * @n_latch: optional bit-inverse of initial register value; if
11 * @setup: optional callback issued once the GPIOs are valid
12 * @teardown: optional callback issued before the GPIOs are invalidated
20 * The @setup callback may be used with the kind of board-specific glue
21 * which hands the (now-valid) GPIOs to other drivers, or which puts
22 * devices in their initial states using these GPIOs.
24 * These GPIO chips are only "quasi-bidirectional"; read the chip specs
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mfd/ |
| D | madera.txt | 1 Cirrus Logic Madera class audio codecs Multi-Functional Device
7 bindings/pinctrl/cirrus,madera-pinctrl.txt
8 bindings/regulator/arizona-regulator.txt
13 - compatible : One of the following chip-specific strings:
20 - reg : I2C slave address when connected using I2C, chip select number when
23 - DCVDD-supply : Power supply for the device as defined in
28 - AVDD-supply, DBVDD1-supply, DBVDD2-supply, CPVDD1-supply, CPVDD2-supply :
31 - DBVDD3-supply, DBVDD4-supply : Power supplies for the device
34 - SPKVDDL-supply, SPKVDDR-supply : Power supplies for the device
37 - SPKVDD-supply : Power supply for the device
[all …]
|