Home
last modified time | relevance | path

Searched refs:GPIO (Results 1 – 25 of 874) sorted by relevance

12345678910>>...35

/Linux-v4.19/Documentation/translations/zh_CN/
Dgpio.txt27 GPIO 接口
29 本文档提供了一个在Linux下访问GPIO的公约概述。
35 什么是GPIO?
37 "通用输入/输出口"(GPIO)是一个灵活的由软件控制的数字信号。他们可
39 比较熟悉。每个GPIO 都代表一个连接到特定引脚或球栅阵列(BGA)封装中
40 “球珠”的一个位。电路板原理图显示了 GPIO 与外部硬件的连接关系。
43 片上系统 (SOC) 处理器对 GPIO 有很大的依赖。在某些情况下,每个
44 非专用引脚都可配置为 GPIO,且大多数芯片都最少有一些 GPIO。
45 可编程逻辑器件(类似 FPGA) 可以方便地提供 GPIO。像电源管理和
47 匮乏的 SOC。同时还有通过 I2C 或 SPI 串行总线连接的“GPIO扩展器”
[all …]
/Linux-v4.19/drivers/pinctrl/
Dpinctrl-xway.c119 MFP_XWAY(GPIO0, GPIO, EXIN, NONE, TDM),
120 MFP_XWAY(GPIO1, GPIO, EXIN, NONE, NONE),
121 MFP_XWAY(GPIO2, GPIO, CGU, EXIN, GPHY),
122 MFP_XWAY(GPIO3, GPIO, CGU, NONE, PCI),
123 MFP_XWAY(GPIO4, GPIO, STP, NONE, ASC),
124 MFP_XWAY(GPIO5, GPIO, STP, GPHY, NONE),
125 MFP_XWAY(GPIO6, GPIO, STP, GPT, ASC),
126 MFP_XWAY(GPIO7, GPIO, CGU, PCI, GPHY),
127 MFP_XWAY(GPIO8, GPIO, CGU, NMI, NONE),
128 MFP_XWAY(GPIO9, GPIO, ASC, SPI, EXIN),
[all …]
Dpinctrl-lpc18xx.c238 LPC_P(0,0, GPIO, SSP1, ENET, SGPIO, R, R, I2S0_TX_WS,I2S1, 0, ND);
239 LPC_P(0,1, GPIO, SSP1,ENET_ALT,SGPIO, R, R, ENET, I2S1, 0, ND);
240 LPC_P(1,0, GPIO, CTIN, EMC, R, R, SSP0, SGPIO, R, 0, ND);
241 LPC_P(1,1, GPIO, CTOUT, EMC, SGPIO, R, SSP0, R, R, 0, ND);
242 LPC_P(1,2, GPIO, CTOUT, EMC, SGPIO, R, SSP0, R, R, 0, ND);
243 LPC_P(1,3, GPIO, CTOUT, SGPIO, EMC, USB0, SSP1, R, SDMMC, 0, ND);
244 LPC_P(1,4, GPIO, CTOUT, SGPIO, EMC, USB0, SSP1, R, SDMMC, 0, ND);
245 LPC_P(1,5, GPIO, CTOUT, R, EMC, USB0, SSP1, SGPIO, SDMMC, 0, ND);
246 LPC_P(1,6, GPIO, CTIN, R, EMC, R, R, SGPIO, SDMMC, 0, ND);
247 LPC_P(1,7, GPIO, UART1, CTOUT, EMC, USB0, R, R, R, 0, ND);
[all …]
Dpinctrl-falcon.c114 MFP_FALCON(GPIO0, RST, GPIO, NONE, NONE),
115 MFP_FALCON(GPIO1, GPIO, GPIO, NONE, NONE),
116 MFP_FALCON(GPIO2, GPIO, GPIO, NONE, NONE),
117 MFP_FALCON(GPIO3, GPIO, GPIO, NONE, NONE),
118 MFP_FALCON(GPIO4, NTR, GPIO, NONE, NONE),
119 MFP_FALCON(GPIO5, NTR, GPIO, PPS, NONE),
120 MFP_FALCON(GPIO6, RST, GPIO, NONE, NONE),
121 MFP_FALCON(GPIO7, MDIO, GPIO, NONE, NONE),
122 MFP_FALCON(GPIO8, MDIO, GPIO, NONE, NONE),
123 MFP_FALCON(GPIO9, LED, GPIO, NONE, NONE),
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/gpio/
Drenesas,gpio-rcar.txt1 * Renesas R-Car GPIO Controller
6 - "renesas,gpio-r8a7743": for R8A7743 (RZ/G1M) compatible GPIO controller.
7 - "renesas,gpio-r8a7745": for R8A7745 (RZ/G1E) compatible GPIO controller.
8 - "renesas,gpio-r8a77470": for R8A77470 (RZ/G1C) compatible GPIO controller.
9 - "renesas,gpio-r8a7778": for R8A7778 (R-Car M1) compatible GPIO controller.
10 - "renesas,gpio-r8a7779": for R8A7779 (R-Car H1) compatible GPIO controller.
11 - "renesas,gpio-r8a7790": for R8A7790 (R-Car H2) compatible GPIO controller.
12 - "renesas,gpio-r8a7791": for R8A7791 (R-Car M2-W) compatible GPIO controller.
13 - "renesas,gpio-r8a7792": for R8A7792 (R-Car V2H) compatible GPIO controller.
14 - "renesas,gpio-r8a7793": for R8A7793 (R-Car M2-N) compatible GPIO controller.
[all …]
Dgpio.txt1 Specifying GPIO information for devices
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
19 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
23 GPIO properties can contain one or more GPIO phandles, but only in exceptional
32 The following example could be used to describe GPIO pins used as device enable
72 GPIO pin number, and GPIO flags as accepted by the "qe_pio_e" gpio-controller.
86 1.1) GPIO specifier best practices
89 A gpio-specifier should contain a flag indicating the GPIO polarity; active-
94 GPIO controller that achieves (or represents, for inputs) a logically asserted
[all …]
D8xxx_gpio.txt1 GPIO controllers on MPC8xxx SoCs
3 This is for the non-QE/CPM/GUTs GPIO controllers as found on
6 Every GPIO controller node must have #gpio-cells property defined,
8 See bindings/gpio/gpio.txt for details of how to specify GPIO
11 The GPIO module usually is connected to the SoC's internal interrupt
13 interrupt client nodes section) for details how to specify this GPIO
16 The GPIO module may serve as another interrupt controller (cascaded to
28 - interrupts: Interrupt mapping for GPIO IRQ.
29 - gpio-controller: Marks the port as GPIO controller.
32 - interrupt-controller: Empty boolean property which marks the GPIO
[all …]
Dnvidia,tegra186-gpio.txt1 NVIDIA Tegra186 GPIO controllers
3 Tegra186 contains two GPIO controllers; a main controller and an "AON"
9 The Tegra186 GPIO controller allows software to set the IO direction of, and
10 read/write the value of, numerous GPIO signals. Routing of GPIO signals to
14 a) Security registers, which allow configuration of allowed access to the GPIO
17 varies between the different GPIO controllers.
20 that wishes to configure access to the GPIO registers needs access to these
21 registers to do so. Code which simply wishes to read or write GPIO data does not
24 b) GPIO registers, which allow manipulation of the GPIO signals. In some GPIO
27 documentation for rationale. Any particular GPIO client is expected to access
[all …]
Dgpio-twl4030.txt1 twl4030 GPIO controller bindings
5 - "ti,twl4030-gpio" for twl4030 GPIO controller
9 - gpio-controller : Marks the device node as a GPIO controller.
12 The first cell is the GPIO number.
15 - ti,debounce : if n-th bit is set, debounces GPIO-n
16 - ti,mmc-cd : if n-th bit is set, GPIO-n controls VMMC(n+1)
17 - ti,pullups : if n-th bit is set, set a pullup on GPIO-n
18 - ti,pulldowns : if n-th bit is set, set a pulldown on GPIO-n
Dgpio-altera.txt1 Altera GPIO controller bindings
10 - gpio-controller : Marks the device node as a GPIO controller.
13 - The first cell is the GPIO offset number within the GPIO controller.
15 - altr,interrupt-type: Specifies the interrupt trigger type the GPIO
16 hardware is synthesized. This field is required if the Altera GPIO controller
18 but hardware synthesized. Required if GPIO is used as an interrupt
27 - altr,ngpio: Width of the GPIO bank. This defines how many pins the
28 GPIO device has. Ranges between 1-32. Optional and defaults to 32 if not
Dgpio_lpc32xx.txt1 NXP LPC32xx SoC GPIO controller
6 - gpio-controller: Marks the device node as a GPIO controller.
9 0: GPIO P0
10 1: GPIO P1
11 2: GPIO P2
12 3: GPIO P3
18 - reg: Index of the GPIO group
/Linux-v4.19/drivers/gpio/
DKconfig2 # GPIO infrastructure and drivers
14 bool "GPIO Support"
17 This enables GPIO support through the generic GPIO library.
19 one or more of the GPIO drivers below.
51 bool "Debug GPIO calls"
54 Say Y here to add some extra checks and diagnostics to GPIO calls.
71 a given GPIO from the kernel, if no kernel driver requested it.
73 Kernel drivers may also request that a particular GPIO be
86 menu "Memory mapped GPIO drivers"
90 tristate "GPIO driver for 74xx-ICs with MMIO access"
[all …]
/Linux-v4.19/drivers/pinctrl/bcm/
DKconfig17 framework. GPIO is provided by a separate GPIO driver.
27 bool "Broadcom iProc GPIO (with PINCONF) driver"
34 Say yes here to enable the Broadcom iProc GPIO driver.
37 same GPIO Controller IP hence this driver could be used for all.
39 The Broadcom Cygnus SoC has 3 GPIO controllers including the ASIU
40 GPIO controller (ASIU), the chipCommonG GPIO controller (CCM), and
41 the always-ON GPIO controller (CRMU/AON). All 3 GPIO controllers are
44 The Broadcom NSP has two GPIO controllers including the ChipcommonA
45 GPIO, the ChipcommonB GPIO. Later controller is supported by this
48 The Broadcom NS2 has two GPIO controller including the CRMU GPIO,
[all …]
/Linux-v4.19/arch/arm/boot/dts/
Dhi3620-hi4511.dts74 0x008 0x0 /* GPIO -- eFUSE_DOUT */
98 0x0f8 0x1 /* GPIO (IOMG61) */
99 0x0fc 0x1 /* GPIO (IOMG62) */
110 0x104 0x1 /* GPIO (IOMG96) */
111 0x108 0x1 /* GPIO (IOMG64) */
122 0x160 0x1 /* GPIO (IOMG85) */
123 0x164 0x1 /* GPIO (IOMG86) */
135 0x168 0x1 /* GPIO (IOMG87) */
136 0x16c 0x1 /* GPIO (IOMG88) */
137 0x170 0x1 /* GPIO (IOMG93) */
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/spi/
Dspi-gpio.txt1 SPI-GPIO devicetree bindings
3 This represents a group of 3-n GPIO lines used for bit-banged SPI on dedicated
4 GPIO lines.
11 - sck-gpios: GPIO spec for the SCK line to use
12 - miso-gpios: GPIO spec for the MISO line to use
13 - mosi-gpios: GPIO spec for the MOSI line to use
21 These legacy GPIO line bindings can alternatively be used to define the
22 GPIO lines used, they should not be used in new device trees.
24 - gpio-sck: GPIO spec for the SCK line to use
25 - gpio-miso: GPIO spec for the MISO line to use
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/input/
Dgpio-mouse.txt1 Device-Tree bindings for GPIO attached mice
3 This simply uses standard GPIO handles to define a simple mouse connected
4 to 5-7 GPIO lines.
9 - up-gpios: GPIO line phandle to the line indicating "up"
10 - down-gpios: GPIO line phandle to the line indicating "down"
11 - left-gpios: GPIO line phandle to the line indicating "left"
12 - right-gpios: GPIO line phandle to the line indicating "right"
15 - button-left-gpios: GPIO line handle to the left mouse button
16 - button-middle-gpios: GPIO line handle to the middle mouse button
17 - button-right-gpios: GPIO line handle to the right mouse button
/Linux-v4.19/Documentation/driver-api/gpio/
Dboard.rst2 GPIO Mappings
8 description of the deprecated integer-based GPIO interface please refer to
11 corresponding GPIO).
13 All platforms can enable the GPIO library, but if the platform strictly
14 requires GPIO functionality to be present, it needs to select GPIOLIB from its
22 exact way to do it depends on the GPIO controller providing the GPIOs, see the
44 "led" function, and GPIO 1 as the "power" GPIO::
54 The led GPIOs will be active high, while the power GPIO will be active low (i.e.
58 the <function>-prefix of the GPIO suffixes ("gpios" or "gpio", automatically
62 Internally, the GPIO subsystem prefixes the GPIO suffix ("gpios" or "gpio")
[all …]
Ddriver.rst2 GPIO Descriptor Driver Interface
5 This document serves as a guide for GPIO chip drivers writers. Note that it
7 deprecated integer-based GPIO interface please refer to gpio-legacy.txt.
9 Each GPIO controller driver needs to include the following header, which defines
10 the structures used to define a GPIO driver:
18 Inside a GPIO driver, individual GPIOs are identified by their hardware number,
21 GPIO descriptor is never made visible outside of the driver.
23 On top of this internal number, each GPIO also need to have a global number in
24 the integer GPIO namespace so that it can be used with the legacy GPIO
26 assigned), and for each GPIO the global number will be (base + hardware number).
[all …]
Dlegacy.rst2 Legacy GPIO Interfaces
5 This provides an overview of GPIO access conventions on Linux.
11 What is a GPIO?
13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
15 to Linux developers working with embedded and custom hardware. Each GPIO
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
26 also "GPIO Expander" chips that connect using the I2C or SPI serial busses.
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
39 cases (to support bidirectional signaling). GPIO controllers may have
46 - Usually a GPIO will be configurable as either input or output, as needed
[all …]
Ddrivers-on-gpio.rst2 Subsystem drivers using GPIO
5 Note that standard kernel drivers exist for common GPIO tasks and will provide
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
14 i.e. a LED will turn on/off in response to a GPIO line going high or low
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
21 GPIO line cannot generate interrupts, so it needs to be periodically polled
26 mouse cable and connect the wires to GPIO lines or solder a mouse connector
30 an external speaker connected to a GPIO line.
34 HDMI connector. It will provide a better userspace sysfs interface than GPIO.
37 the system by pulling a GPIO line and will register a restart handler so
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/serial/
Dserial.txt8 - cts-gpios: Must contain a GPIO specifier, referring to the GPIO pin to be
10 - dcd-gpios: Must contain a GPIO specifier, referring to the GPIO pin to be
12 - dsr-gpios: Must contain a GPIO specifier, referring to the GPIO pin to be
14 - dtr-gpios: Must contain a GPIO specifier, referring to the GPIO pin to be
16 - rng-gpios: Must contain a GPIO specifier, referring to the GPIO pin to be
18 - rts-gpios: Must contain a GPIO specifier, referring to the GPIO pin to be
/Linux-v4.19/Documentation/devicetree/bindings/pinctrl/
Dingenic,pinctrl.txt7 For the jz47xx SoCs, pin control is tightly bound with GPIO ports. All pins may
9 GPIO port configuration registers and it is typical to refer to pins using the
10 naming scheme "PxN" where x is a character identifying the GPIO port with
12 pin within that GPIO port. For example PA0 is the first pin in GPIO port A, and
13 PB31 is the last pin in GPIO port B. The jz4740 contains 4 GPIO ports, PA to
14 PD, for a total of 128 pins. The jz4780 contains 6 GPIO ports, PA to PF, for a
28 GPIO sub-nodes
31 The pinctrl node can have optional sub-nodes for the Ingenic GPIO driver;
/Linux-v4.19/arch/arm64/boot/dts/hisilicon/
Dhi3798cv200-poplar.dts109 gpio-line-names = "GPIO-E", "",
111 "", "GPIO-F",
112 "", "GPIO-J";
117 gpio-line-names = "GPIO-H", "GPIO-I",
118 "GPIO-L", "GPIO-G",
119 "GPIO-K", "",
127 "GPIO-C", "",
128 "", "GPIO-B";
135 "", "GPIO-D",
143 "", "GPIO-A",
/Linux-v4.19/Documentation/devicetree/bindings/fsi/
Dfsi-master-gpio.txt6 - clock-gpios = <gpio-descriptor>; : GPIO for FSI clock
7 - data-gpios = <gpio-descriptor>; : GPIO for FSI data signal
10 - enable-gpios = <gpio-descriptor>; : GPIO for enable signal
11 - trans-gpios = <gpio-descriptor>; : GPIO for voltage translator enable
12 - mux-gpios = <gpio-descriptor>; : GPIO for pin multiplexing with other
14 - no-gpio-delays; : Don't add extra delays between GPIO
16 GPIO block is running at a low enough
/Linux-v4.19/Documentation/acpi/
Dgpio-properties.txt1 _DSD Device Properties Related to GPIO
7 the corresponding GPIO, which is pretty error prone (it depends on
37 The format of the supported GPIO property is:
45 active_low - If 1 the GPIO is marked as active_low.
49 it to 1 marks the GPIO as active low.
52 resource, second pin in that resource with the GPIO number of 31.
63 ^GPIO, 19, 0, 0, // chip select 0: GPIO
65 ^GPIO, 20, 0, 0, // chip select 2: GPIO
73 _DSD device properties for GPIO controllers:
116 ACPI GPIO Mappings Provided by Drivers
[all …]

12345678910>>...35