| /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-6.6/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 - Michael Hennerich <michael.hennerich@analog.com>
14 https://www.analog.com/media/en/technical-documentation/data-sheets/ad7606_7606-6_7606-4.pdf
15 https://www.analog.com/media/en/technical-documentation/data-sheets/AD7606B.pdf
16 https://www.analog.com/media/en/technical-documentation/data-sheets/AD7616.pdf
21 - adi,ad7605-4
22 - adi,ad7606-8
23 - adi,ad7606-6
[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-6.6/drivers/bus/ |
| D | ts-nbus.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * NBUS driver for TS-4600 based boards
5 * Copyright (c) 2016 - Savoir-faire Linux
8 * This driver implements a GPIOs bit-banged bus, called the NBUS by Technologic
10 * TS-4600 SoM.
21 #include <linux/ts-nbus.h>
30 struct gpio_descs *data; member
40 * request all gpios required by the bus.
45 ts_nbus->data = devm_gpiod_get_array(&pdev->dev, "ts,data", in ts_nbus_init_pdata()
47 if (IS_ERR(ts_nbus->data)) { in ts_nbus_init_pdata()
[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-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-6.6/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
34 even-numbered pixels are received on port@0 and odd-numbered pixels on
37 When operating in single output mode all pixels are output from the first
45 description: First LVDS input port
[all …]
|
| /kernel/linux/linux-6.6/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-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-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 …]
|
| D | sii902x.txt | 4 - compatible: "sil,sii9022"
5 - reg: i2c address of the bridge
8 - interrupts: describe the interrupt line used to inform the host
10 - reset-gpios: OF device-tree gpio specification for RST_N pin.
11 - iovcc-supply: I/O Supply Voltage (1.8V or 3.3V)
12 - cvcc12-supply: Digital Core Supply Voltage (1.2V)
15 - #sound-dai-cells: <0> or <1>. <0> if only i2s or spdif pin
18 - sil,i2s-data-lanes: Array of up to 4 integers with values of 0-3
20 audio fifo. The first integer selects i2s audio pin for the
21 first audio fifo#0 (HDMI channels 1&2), second for fifo#1
[all …]
|
| /kernel/linux/linux-6.6/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
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
26 <function>-gpios, where <function> is the function the driver will request
[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-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-6.6/include/linux/gpio/ |
| D | driver.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
10 #include <linux/pinctrl/pinconf-generic.h>
46 * struct gpio_irq_chip - GPIO interrupt controller
76 * If non-NULL, will be set as the parent of this GPIO interrupt
88 * hardware IRQs correspond to the GPIO index 0..ngpio-1 (see the
96 * HWIRQ, return -EINVAL, but also make sure to fill in @valid_mask and
111 * &gpiochip_populate_parent_fwspec_twocell will be used. A four-cell
185 * single pointer used as the data associated with every
195 * different data for each parent. This cannot be NULL if
234 * sized array to be used as parent data.
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpio/ |
| D | gpio-syscon.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
20 /* SYSCON driver is designed to use 32-bit wide registers */
25 * struct syscon_gpio_data - Configuration for the device.
28 * GPIO_SYSCON_FEAT_IN: GPIOs supports input,
29 * GPIO_SYSCON_FEAT_OUT: GPIOs supports output,
30 * GPIO_SYSCON_FEAT_DIR: GPIOs supports switch direction.
31 * @bit_count: Number of bits used as GPIOs.
32 * @dat_bit_offset: Offset (in bits) to the first GPIO bit.
33 * @dir_bit_offset: Optional offset (in bits) to the first bit to switch
51 const struct syscon_gpio_data *data; member
[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
173 * Data associated, and passed to, the handler for the parent
217 * sized array to be used as parent data.
234 * bits from 0..(ngpios-1) set to "1" as in valid. The callback can
[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-6.6/Documentation/devicetree/bindings/mmc/ |
| D | arm,pl18x.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Ulf Hansson <ulf.hansson@linaro.org>
20 - $ref: /schemas/arm/primecell.yaml#
21 - $ref: mmc-controller.yaml#
29 - arm,pl180
30 - arm,pl181
31 - arm,pl18x
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpio/ |
| D | gpio-syscon.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
21 /* SYSCON driver is designed to use 32-bit wide registers */
26 * struct syscon_gpio_data - Configuration for the device.
29 * GPIO_SYSCON_FEAT_IN: GPIOs supports input,
30 * GPIO_SYSCON_FEAT_OUT: GPIOs supports output,
31 * GPIO_SYSCON_FEAT_DIR: GPIOs supports switch direction.
32 * @bit_count: Number of bits used as GPIOs.
33 * @dat_bit_offset: Offset (in bits) to the first GPIO bit.
34 * @dir_bit_offset: Optional offset (in bits) to the first bit to switch
53 const struct syscon_gpio_data *data; member
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/gpio/ |
| D | sysfs.rst | 7 Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS
16 ------------------------
18 configure a sysfs user interface to GPIOs. This is different from the
26 may need to temporarily remove that protection, first importing a GPIO,
27 then changing its output state, then updating the code before re-enabling
32 userspace GPIO can be used to determine system configuration data that
37 PLEASE READ THE DOCUMENT AT Documentation/driver-api/gpio/drivers-on-gpio.rst
41 --------------
44 - Control interfaces used to get userspace control over GPIOs;
46 - GPIOs themselves; and
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/gpio/ |
| D | sysfs.rst | 7 Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS
16 ------------------------
18 configure a sysfs user interface to GPIOs. This is different from the
26 may need to temporarily remove that protection, first importing a GPIO,
27 then changing its output state, then updating the code before re-enabling
32 userspace GPIO can be used to determine system configuration data that
37 PLEASE READ THE DOCUMENT AT Documentation/driver-api/gpio/drivers-on-gpio.rst
41 --------------
44 - Control interfaces used to get userspace control over GPIOs;
46 - GPIOs themselves; and
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/ |
| D | solomon,ssd1307fb.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Maxime Ripard <mripard@kernel.org>
11 - Javier Martinez Canillas <javierm@redhat.com>
17 - enum:
18 - solomon,ssd1305fb-i2c
19 - solomon,ssd1306fb-i2c
20 - solomon,ssd1307fb-i2c
21 - solomon,ssd1309fb-i2c
[all …]
|