| /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-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 …]
|
| D | nvidia,tegra186-gpio.txt | 21 registers to do so. Code which simply wishes to read or write GPIO data does not
30 Tegra HW documentation describes a unified naming convention for all GPIOs
32 a number of GPIOs. Thus, each GPIO is named according to an alphabetical port
37 implemented GPIOs within each port varies. GPIO registers within a controller
42 extremely non-linear. The header file <dt-bindings/gpio/tegra186-gpio.h>
43 describes the port-level mapping. In that file, the naming convention for ports
49 represents the aggregate status for all GPIOs within a set of ports. Thus, the
52 both the overall controller HW module and the sets-of-ports as "controllers".
56 interrupt signals generated by a set-of-ports. The intent is for each generated
59 per-port-set signals is reported via a separate register. Thus, a driver needs
[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 …]
|
| D | ti,sn65dsi86.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sandeep Panda <spanda@codeaurora.org>
23 enable-gpios:
27 suspend-gpios:
31 no-hpd:
37 vccio-supply:
40 vpll-supply:
43 vcca-supply:
[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 …]
|
| D | machine.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
22 * struct gpiod_lookup - lookup table
25 * so this will use the first match found!
29 * @idx: index of the GPIO in case several GPIOs share the same name
32 * gpiod_lookup is a lookup table for associating GPIOs to specific devices and
33 * functions using platform data.
50 * struct gpiod_hog - GPIO line hog table
73 * Use this macro if you need to have several GPIOs under the same con_id.
|
| /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-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-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-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 …]
|
| D | gpio-davinci.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
5 * Copyright (c) 2006-2007 David Brownell
22 #include <linux/platform_data/gpio-davinci.h>
26 #include <asm-generic/gpio.h>
46 #define BINTEN 0x8 /* GPIO Interrupt Per-Bank Enable Register */
83 /*--------------------------------------------------------------------------*/
96 g = d->regs[bank]; in __davinci_direction()
97 spin_lock_irqsave(&d->lock, flags); in __davinci_direction()
98 temp = readl_relaxed(&g->dir); in __davinci_direction()
101 writel_relaxed(mask, value ? &g->set_data : &g->clr_data); in __davinci_direction()
[all …]
|
| D | gpiolib-acpi.c | 1 // SPDX-License-Identifier: GPL-2.0
22 #include "gpiolib-acpi.h"
24 static int run_edge_events_on_boot = -1;
27 "Run edge _AEI event-handlers at boot: 0=no, 1=yes, -1=auto");
41 * struct acpi_gpio_event - ACPI GPIO event handler data
43 * @node: list-entry of the events list of the struct acpi_gpio_chip
73 * ACPICA requires that the first field of the context parameter
96 static int acpi_gpiochip_find(struct gpio_chip *gc, void *data) in acpi_gpiochip_find() argument
98 if (!gc->parent) in acpi_gpiochip_find()
101 return ACPI_HANDLE(gc->parent) == data; in acpi_gpiochip_find()
[all …]
|
| D | gpio-twl4030.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Access to GPIOs on TWL4030/TPS659x0 chips
5 * Copyright (C) 2006-2007 Texas Instruments, Inc.
8 * Code re-arranged and cleaned up by:
28 * The GPIO "subchip" supports 18 GPIOs which can be configured as
35 * There are also two LED pins used sometimes as output-only GPIOs.
50 /* Mask for GPIO registers when aggregated into a 32-bit integer */
64 /*----------------------------------------------------------------------*/
69 static inline int gpio_twl4030_write(u8 address, u8 data) in gpio_twl4030_write() argument
71 return twl_i2c_write_u8(TWL4030_MODULE_GPIO, data, address); in gpio_twl4030_write()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | davicom-dm9000.txt | 4 - compatible = "davicom,dm9000";
5 - reg : physical addresses and sizes of registers, must contain 2 entries:
6 first entry : address register,
7 second entry : data register.
8 - interrupts : interrupt specifier specific to interrupt controller
11 - davicom,no-eeprom : Configuration EEPROM is not available
12 - davicom,ext-phy : Use external PHY
13 - reset-gpios : phandle of gpio that will be used to reset chip during probe
14 - vcc-supply : phandle of regulator that will be used to enable power to chip
21 interrupt-parent = <&gpn>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | ssd1307fb.txt | 4 - compatible: Should be "solomon,<chip>fb-<bus>". The only supported bus for
7 - reg: Should contain address of the controller on the I2C bus. Most likely
9 - pwm: Should contain the pwm to use according to the OF device tree PWM
11 - solomon,height: Height in pixel of the screen driven by the controller
12 - solomon,width: Width in pixel of the screen driven by the controller
13 - solomon,page-offset: Offset of pages (band of 8 pixels) that the screen is
17 - reset-gpios: The GPIO used to reset the OLED display, if available. See
19 - vbat-supply: The supply for VBAT
20 - solomon,segment-no-remap: Display needs normal (non-inverted) data column
22 - solomon,col-offset: Offset of columns (COL/SEG) that the screen is mapped to.
[all …]
|
| /kernel/linux/linux-5.10/drivers/pinctrl/renesas/ |
| D | gpio.c | 1 // SPDX-License-Identifier: GPL-2.0
6 * Copyright (C) 2009 - 2012 Paul Mundt
41 return chip->pfc; in gpio_to_pfc()
48 int idx = sh_pfc_get_pin_index(chip->pfc, offset); in gpio_get_data_reg()
49 struct sh_pfc_gpio_pin *gpio_pin = &chip->pins[idx]; in gpio_get_data_reg()
51 *reg = &chip->regs[gpio_pin->dreg]; in gpio_get_data_reg()
52 *bit = gpio_pin->dbit; in gpio_get_data_reg()
58 phys_addr_t address = dreg->reg; in gpio_read_data_reg()
59 void __iomem *mem = address - chip->mem->phys + chip->mem->virt; in gpio_read_data_reg()
61 return sh_pfc_read_raw_reg(mem, dreg->reg_width); in gpio_read_data_reg()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | gpio-properties.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 allows names to be given to GPIOs (and other things as well) returned
13 With _DSD we can now query GPIOs using a name instead of an integer
16 // Bluetooth device with reset and shutdown GPIOs
31 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
34 Package () {"reset-gpios", Package() {^BTH, 1, 1, 0 }},
35 Package () {"shutdown-gpios", Package() {^BTH, 0, 0, 0 }},
61 In our Bluetooth example the "reset-gpios" refers to the second GpioIo()
75 assuming non-active (Polarity = !Pull Bias)
77 Down High as low, assuming non-active
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | davinci-mcasp-audio.txt | 4 - compatible :
5 "ti,dm646x-mcasp-audio" : for DM646x platforms
6 "ti,da830-mcasp-audio" : for both DA830 & DA850 platforms
7 "ti,am33xx-mcasp-audio" : for AM33xx platforms (AM33xx, AM43xx, TI81xx)
8 "ti,dra7-mcasp-audio" : for DRA7xx platforms
10 - reg : Should contain reg specifiers for the entries in the reg-names property.
11 - reg-names : Should contain:
13 existing software, it is recommended this is the first entry.
14 * "dat" for separate data port register access (optional).
15 - op-mode : I2S/DIT ops mode. 0 for I2S mode. 1 for DIT mode used for S/PDIF,
[all …]
|