Home
last modified time | relevance | path

Searched refs:GPIO (Results 1 – 200 of 575) sorted by relevance

123

/linux-4.4.14/Documentation/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-4.4.14/drivers/pinctrl/
Dpinctrl-lpc18xx.c226 LPC_P(0,0, GPIO, SSP1, ENET, SGPIO, R, R, I2S0_TX_WS,I2S1, 0, ND);
227 LPC_P(0,1, GPIO, SSP1,ENET_ALT,SGPIO, R, R, ENET, I2S1, 0, ND);
228 LPC_P(1,0, GPIO, CTIN, EMC, R, R, SSP0, SGPIO, R, 0, ND);
229 LPC_P(1,1, GPIO, CTOUT, EMC, SGPIO, R, SSP0, R, R, 0, ND);
230 LPC_P(1,2, GPIO, CTOUT, EMC, SGPIO, R, SSP0, R, R, 0, ND);
231 LPC_P(1,3, GPIO, CTOUT, SGPIO, EMC, USB0, SSP1, R, SDMMC, 0, ND);
232 LPC_P(1,4, GPIO, CTOUT, SGPIO, EMC, USB0, SSP1, R, SDMMC, 0, ND);
233 LPC_P(1,5, GPIO, CTOUT, R, EMC, USB0, SSP1, SGPIO, SDMMC, 0, ND);
234 LPC_P(1,6, GPIO, CTIN, R, EMC, R, R, SGPIO, SDMMC, 0, ND);
235 LPC_P(1,7, GPIO, UART1, CTOUT, EMC, USB0, R, R, R, 0, ND);
[all …]
Dpinctrl-xway.c111 MFP_XWAY(GPIO0, GPIO, EXIN, NONE, TDM),
112 MFP_XWAY(GPIO1, GPIO, EXIN, NONE, NONE),
113 MFP_XWAY(GPIO2, GPIO, CGU, EXIN, GPHY),
114 MFP_XWAY(GPIO3, GPIO, CGU, NONE, PCI),
115 MFP_XWAY(GPIO4, GPIO, STP, NONE, ASC),
116 MFP_XWAY(GPIO5, GPIO, STP, NONE, GPHY),
117 MFP_XWAY(GPIO6, GPIO, STP, GPT, ASC),
118 MFP_XWAY(GPIO7, GPIO, CGU, PCI, GPHY),
119 MFP_XWAY(GPIO8, GPIO, CGU, NMI, NONE),
120 MFP_XWAY(GPIO9, GPIO, ASC, SPI, EXIN),
[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 …]
Dpinctrl-palmas.c311 FUNCTION_GROUP(gpio, GPIO), \
414 PULL_UP_DN(gpio0, GPIO, PALMAS_PU_PD_GPIO_CTRL1, 0x04, 0, -1, 1);
415 PULL_UP_DN(gpio1, GPIO, PALMAS_PU_PD_GPIO_CTRL1, 0x0C, 0, 0x8, 0x4);
416 PULL_UP_DN(gpio2, GPIO, PALMAS_PU_PD_GPIO_CTRL1, 0x30, 0x0, 0x20, 0x10);
417 PULL_UP_DN(gpio3, GPIO, PALMAS_PU_PD_GPIO_CTRL1, 0x40, 0x0, -1, 0x40);
418 PULL_UP_DN(gpio4, GPIO, PALMAS_PU_PD_GPIO_CTRL2, 0x03, 0x0, 0x2, 0x1);
419 PULL_UP_DN(gpio5, GPIO, PALMAS_PU_PD_GPIO_CTRL2, 0x0c, 0x0, 0x8, 0x4);
420 PULL_UP_DN(gpio6, GPIO, PALMAS_PU_PD_GPIO_CTRL2, 0x30, 0x0, 0x20, 0x10);
421 PULL_UP_DN(gpio7, GPIO, PALMAS_PU_PD_GPIO_CTRL2, 0x40, 0x0, -1, 0x40);
422 PULL_UP_DN(gpio9, GPIO, PALMAS_PU_PD_GPIO_CTRL3, 0x0C, 0x0, 0x8, 0x4);
[all …]
DKconfig38 bool "Pinctrl and GPIO driver for ams AS3722 PMIC"
43 AS3722 device supports the configuration of GPIO pins for different
45 open drain configuration for the GPIO pins of AS3722 devices. It also
46 supports the GPIO functionality through gpiolib.
82 bool "AMD GPIO pin control"
88 driver for memory mapped GPIO functionality on AMD platforms
221 bool "ST-Ericsson U300 COH 901 335/571 GPIO"
225 Say yes here to support GPIO interface on ST-Ericsson U300.
228 ports of 8 GPIO pins each.
/linux-4.4.14/drivers/gpio/
DKconfig2 # GPIO infrastructure and drivers
35 bool "GPIO Support"
38 This enables GPIO support through the generic GPIO library.
40 one or more of the GPIO drivers below.
63 bool "Debug GPIO calls"
66 Say Y here to add some extra checks and diagnostics to GPIO calls.
83 a given GPIO from the kernel, if no kernel driver requested it.
85 Kernel drivers may also request that a particular GPIO be
97 menu "Memory mapped GPIO drivers"
100 tristate "GPIO driver for 74xx-ICs with MMIO access"
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Drenesas,gpio-rcar.txt1 * Renesas R-Car GPIO Controller
6 - "renesas,gpio-r8a7778": for R8A7778 (R-Mobile M1) compatible GPIO controller.
7 - "renesas,gpio-r8a7779": for R8A7779 (R-Car H1) compatible GPIO controller.
8 - "renesas,gpio-r8a7790": for R8A7790 (R-Car H2) compatible GPIO controller.
9 - "renesas,gpio-r8a7791": for R8A7791 (R-Car M2-W) compatible GPIO controller.
10 - "renesas,gpio-r8a7793": for R8A7793 (R-Car M2-N) compatible GPIO controller.
11 - "renesas,gpio-r8a7794": for R8A7794 (R-Car E2) compatible GPIO controller.
12 - "renesas,gpio-r8a7795": for R8A7795 (R-Car H3) compatible GPIO controller.
13 - "renesas,gpio-rcar": for generic R-Car GPIO controller.
15 - reg: Base address and length of each memory resource used by the GPIO
[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.
83 1.1) GPIO specifier best practices
86 A gpio-specifier should contain a flag indicating the GPIO polarity; active-
91 GPIO controller that achieves (or represents, for inputs) a logically asserted
[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-trigger: 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
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
30 - interrupts: Interrupt mapping for GPIO IRQ.
31 - gpio-controller: Marks the port as GPIO controller.
34 - interrupt-controller: Empty boolean property which marks the GPIO
[all …]
Dcavium-octeon-gpio.txt1 * General Purpose Input Output (GPIO) bus.
8 - reg: The base address of the GPIO unit's register bank.
10 - gpio-controller: This is a GPIO controller.
12 - #gpio-cells: Must be <2>. The first cell is the GPIO pin.
14 - interrupt-controller: The GPIO controller is also an interrupt
18 - #interrupt-cells: Must be <2>. The first cell is the GPIO pin
36 * 1) GPIO pin number (0..15)
44 /* The GPIO pin connect to 16 consecutive CUI bits */
Dbrcm,kona-gpio.txt1 Broadcom Kona Family GPIO
4 This GPIO driver is used in the following Broadcom SoCs:
7 The Broadcom GPIO Controller IP can be configured prior to synthesis to
9 GPIO controller only supports edge, not level, triggering of interrupts.
16 - interrupts: The interrupt outputs from the controller. There is one GPIO
17 interrupt per GPIO bank. The number of interrupts listed depends on the
18 number of GPIO banks on the SoC. The interrupts must be ordered by bank,
25 - #interrupt-cells: Should be <2>. The first cell is the GPIO number. The
34 - gpio-controller: Marks the device node as a GPIO controller.
Dgpio-dsp-keystone.txt1 Keystone 2 DSP GPIO controller bindings
4 the DSP GPIO controller IP. It provides 28 IRQ signals per each DSP core.
7 For example TCI6638K2K SoC has 8 DSP GPIO controllers:
10 Keystone 2 DSP GPIO controller has specific features:
11 - each GPIO can be configured only as output pin;
12 - setting GPIO value to 1 causes IRQ generation on target DSP core;
24 Please refer to gpio.txt in this directory for details of the common GPIO
Dsodaville.txt1 GPIO controller on CE4100 / Sodaville SoCs
4 The bindings for CE4100's GPIO controller match the generic description
19 Example of the GPIO device and one user:
22 /* two cells for GPIO and interrupt */
33 /* It is an interrupt and GPIO controller itself */
41 /* User the 11th GPIO line as an active high triggered
46 /* Use this GPIO also with the gpio functions */
Dgpio-mxs.txt1 * Freescale MXS GPIO controller
3 The Freescale MXS GPIO controller is part of MXS PIN controller. The
6 As the GPIO controller is embedded in the PIN controller and all the
7 GPIO ports share the same IO space with PIN controller, the GPIO node
10 Required properties for GPIO node:
20 - #interrupt-cells : Should be 2. The first cell is the GPIO number.
27 Note: Each GPIO port should have an alias correctly numbered in "aliases"
Dgpio-vf610.txt1 * Freescale VF610 PORT/GPIO module
3 The Freescale PORT/GPIO modules are two adjacent modules providing GPIO
7 Required properties for GPIO node:
10 the GPIO module.
18 - #interrupt-cells : Should be 2. The first cell is the GPIO number.
25 Note: Each GPIO port should have an alias correctly numbered in "aliases"
Dgpio-poweroff.txt1 Driver a GPIO line that can be used to turn the power off.
6 not found, the GPIO line will be driven in the inactive
13 the GPIO is set to inactive, thus causing an active->inactive edge,
15 delay the GPIO is driver active again. If the power is still on and
20 - gpios : The GPIO to set high/low, see "gpios property" in
26 - input : Initially configure the GPIO line as an input. Only reconfigure
28 property is not specified, the GPIO is initialized as an output in its
Dgpio-xilinx.txt1 Xilinx plb/axi GPIO controller
3 Dual channel GPIO controller with configurable number of pins
13 - gpio-controller : Marks the device node as a GPIO controller.
16 - interrupts : Interrupt mapping for GPIO IRQ.
19 - xlnx,all-inputs : if n-th bit is setup, GPIO-n is input
20 - xlnx,dout-default : if n-th bit is 1, GPIO-n default value is 1
22 - xlnx,tri-default : if n-th bit is 1, GPIO-n is in tristate mode
Dgpio-omap.txt1 OMAP GPIO controller bindings
8 - gpio-controller : Marks the device node as a GPIO controller.
14 The first cell is the GPIO number.
23 - ti,hwmods: Name of the hwmod associated to the GPIO:
26 - ti,gpio-always-on: Indicates if a GPIO bank is always powered and
Dbrcm,brcmstb-gpio.txt1 Broadcom STB "UPG GIO" GPIO controller
14 the brcmstb GPIO controller registers
22 Specifies that the node is a GPIO controller.
25 Number of GPIO lines for each bank. Number of elements must
31 The interrupt shared by all GPIO lines for this controller.
39 'interrupt-parent'. Wakeup-capable GPIO controllers often route their
44 Should be <2>. The first cell is the GPIO number, the second should specify
Dgpio-restart.txt1 Drive a GPIO line that can be used to restart the system from a restart
6 handler. If the optional properties 'open-source' is not found, the GPIO line
14 reset. After a delay specified by active-delay, the GPIO is set to
16 triggered reset. After a delay specified by inactive-delay, the GPIO
22 - gpios : The GPIO to set high/low, see "gpios property" in
28 - open-source : Treat the GPIO as being open source and defer driving
30 specified, the GPIO is initialized as an output in its inactive state.
Dnxp,lpc1850-gpio.txt1 NXP LPC18xx/43xx GPIO controller Device Tree Bindings
8 - gpio-controller : Marks the device node as a GPIO controller.
10 - First cell is the GPIO line number
14 - gpio-ranges : Mapping between GPIO and pinctrl
Dgpio-xlp.txt1 Netlogic XLP Family GPIO
4 This GPIO driver is used for following Netlogic XLP SoCs:
19 - gpio-controller: Marks the device node as a GPIO controller.
20 - nr-gpios: Number of GPIO pins supported by the controller.
21 - interrupt-cells: Should be two. The first cell is the GPIO Number. The
Dgpio-mcp23s08.txt6 - "mcp,mcp23s08" (DEPRECATED) for 8 GPIO SPI version
7 - "mcp,mcp23s17" (DEPRECATED) for 16 GPIO SPI version
8 - "mcp,mcp23008" (DEPRECATED) for 8 GPIO I2C version or
9 - "mcp,mcp23017" (DEPRECATED) for 16 GPIO I2C version of the chip
11 - "microchip,mcp23s08" for 8 GPIO SPI version
12 - "microchip,mcp23s17" for 16 GPIO SPI version
13 - "microchip,mcp23008" for 8 GPIO I2C version or
14 - "microchip,mcp23017" for 16 GPIO I2C version of the chip
20 - gpio-controller : Marks the device node as a GPIO controller.
Dgpio-sx150x.txt1 SEMTECH SX150x GPIO expander bindings
16 - #gpio-cells: Should be 2. The first cell is the GPIO number and the
20 - gpio-controller: Marks the device as a GPIO controller.
24 The GPIO expander can optionally be used as an interrupt controller, in
Dgpio-atlas7.txt1 CSR SiRFatlas7 GPIO controller bindings
6 - interrupts : Interrupts used by every GPIO group
8 - gpio-controller : Indicates this device is a GPIO controller
11 The GPIO controller also acts as an interrupt controller. It uses the default
Dgpio-xgene-sb.txt1 APM X-Gene Standby GPIO controller bindings
5 There are 20 GPIO pins from 0..21. There is no GPIO_DS14 or GPIO_DS15,
10 - compatible: "apm,xgene-gpio-sb" for the X-Gene Standby GPIO controller
17 - gpio-controller: Marks the device node as a GPIO controller.
Dgpio-adnp.txt1 Avionic Design N-bit GPIO expander bindings
8 - #gpio-cells: Should be 2. The first cell is the GPIO number and the
11 - gpio-controller: Marks the device as a GPIO controller
14 The GPIO expander can optionally be used as an interrupt controller, in
Dpl061-gpio.txt1 ARM PL061 GPIO controller
8 - gpio-controller : Marks the device node as a GPIO controller.
9 - interrupts : Interrupt mapping for GPIO IRQ.
Dgpio-zynq.txt1 Xilinx Zynq GPIO controller Device Tree Bindings
6 - First cell is the GPIO line number
11 - gpio-controller : Marks the device node as a GPIO controller.
16 - #interrupt-cells : Should be 2. The first cell is the GPIO number.
Dabilis,tb10x-gpio.txt1 * Abilis TB10x GPIO controller
10 - abilis,ngpio: the number of GPIO pins this driver controls.
15 - interrupts: Defines the interrupt line connecting this GPIO controller to
19 GPIO ranges are specified as described in
Dgpio-lp3943.txt1 TI/National Semiconductor LP3943 GPIO controller
5 - gpio-controller: Marks the device node as a GPIO controller.
10 Simple LED controls with LP3943 GPIO controller
Dgpio-davinci.txt1 Davinci/Keystone GPIO controller bindings
17 - interrupts: Array of GPIO interrupt number. Only banked or unbanked IRQs are
20 - ti,ngpio: The number of GPIO pins supported.
25 The GPIO controller also acts as an interrupt controller. It uses the default
Dzx296702-gpio.txt1 ZTE ZX296702 GPIO controller
8 - gpio-controller : Marks the device node as a GPIO controller.
9 - interrupts : Interrupt mapping for GPIO IRQ.
Dgpio-xgene.txt1 APM X-Gene SoC GPIO controller bindings
7 - compatible: "apm,xgene-gpio" for X-Gene GPIO controller
14 - gpio-controller: Marks the device node as a GPIO controller.
Dgpio-palmas.txt1 Palmas GPIO controller bindings
5 - "ti,palams-gpio" for palma series of the GPIO controller
14 - gpio-controller : Marks the device node as a GPIO controller.
Dgpio_atmel.txt1 * Atmel GPIO controller (PIO)
5 - reg: Should contain GPIO controller registers location and length
10 - gpio-controller: Marks the device node as a GPIO controller.
Dgpio-clps711x.txt1 Cirrus Logic CLPS711X GPIO controller
5 - reg: Physical base GPIO controller registers location and length.
14 Note: Each GPIO port should have an alias correctly numbered in "aliases"
Dgpio-tz1090-pdc.txt1 ImgTec TZ1090 PDC GPIO Controller
18 - GPIO number: a value in the range 0 to 6.
19 - GPIO flags: bit field of flags, as defined in <dt-bindings/gpio/gpio.h>.
Dnvidia,tegra20-gpio.txt1 NVIDIA Tegra GPIO controller
12 - gpio-controller : Marks the device node as a GPIO controller.
14 The first cell is the GPIO number.
Dgpio-stericsson-coh901.txt1 ST-Ericsson COH 901 571/3 GPIO controller
7 - interrupts: the 0...n interrupts assigned to the different GPIO ports/banks.
Dgpio-max732x.txt15 - gpio-controller: Marks the device node as a GPIO controller.
17 - first cell is the GPIO number
18 - second cell specifies GPIO flags, as defined in <dt-bindings/gpio/gpio.h>.
36 Please refer to gpio.txt in this directory for details of the common GPIO
Dgpio-tz1090.txt1 ImgTec TZ1090 GPIO Controller
27 - GPIO number: a value in the range 0 to 29.
28 - GPIO flags: bit field of flags, as defined in <dt-bindings/gpio/gpio.h>.
48 - GPIO number: a value in the range 0 to 29
Dgpio-zevio.txt1 Zevio GPIO controller
8 - gpio-controller: Marks the device node as a GPIO controller.
Dgpio-mvebu.txt1 * Marvell EBU GPIO controller
18 managed by this GPIO bank. There can be more than one interrupt
26 The first cell is the GPIO number.
Dgpio-mpc8xxx.txt1 * Freescale MPC512x/MPC8xxx/Layerscape GPIO controller
15 - little-endian : GPIO registers are used as little endian. If not
Dgpio-74xx-mmio.txt1 * 74XX MMIO GPIO driver
20 the second cell is used to specify the GPIO polarity:
Dgpio-nmk.txt1 Nomadik GPIO controller
15 - gpio-controller : Marks the device node as a GPIO controller.
Dgpio-ath79.txt1 Binding for Qualcomm Atheros AR7xxx/AR9xxx GPIO controller
9 - gpio-controller : Marks the device node as a GPIO controller.
Dfsl-imx-gpio.txt1 * Freescale i.MX/MXC GPIO controller
15 - #interrupt-cells : Should be 2. The first cell is the GPIO number.
/linux-4.4.14/drivers/pinctrl/bcm/
DKconfig16 framework. GPIO is provided by a separate GPIO driver.
24 bool "Broadcom Cygnus GPIO (with PINCONF) driver"
31 Say yes here to enable the Broadcom Cygnus GPIO driver.
33 The Broadcom Cygnus SoC has 3 GPIO controllers including the ASIU
34 GPIO controller (ASIU), the chipCommonG GPIO controller (CCM), and
35 the always-ON GPIO controller (CRMU/AON). All 3 GPIO controllers are
38 All 3 Cygnus GPIO controllers support basic PINCONF functions such
40 these pins are muxed to GPIO.
42 Pins from the ASIU GPIO can be individually muxed to GPIO function,
56 can be overrided to GPIO function
/linux-4.4.14/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 …]
Dste-hrefv60plus.dtsi51 /* SD card detect GPIO pin, extend default state */
70 * XENON Flashgun on image processor GPIO (controlled from image
71 * processor firmware), mux in these image processor GPIO lines 0
73 * LED on IP GPIO 4 (XENON_EN2) on altfunction C, that need bias
165 /* Audio Amplifier HF enable GPIO */
186 /* MSP : HDTV INTERFACE GPIO line */
196 * Touch screen uses GPIO 143 for RST1, GPIO 146 for RST2 and
197 * GPIO 67 for interrupts. Pull-up the IRQ line and drive both
213 * Display Interface 1 uses GPIO 65 for RST (reset).
214 * Display Interface 2 uses GPIO 66 for RST (reset).
[all …]
Ddove-sbc-a510.dts46 * SBC-A510 comprises a PCA9555 I2C GPIO expander its GPIO lines connected to
104 * USB port 0 can be powered and monitored by I2C GPIO expander:
122 * - GPIO expander, NXP PCA9555, 0x20
142 /* NXP PCA9555 GPIO expander */
170 * SDIO0 is connected to a MMC/SD/SDIO socket, I2C GPIO expander has
Dste-nomadik-s8815.dts56 /* CD input GPIO */
61 /* CD GPIO biasing */
116 /* GPIO I2C connected to the USB portions of the STw4811 only */
Domap3-panel-sharp-ls037v7dw01.dtsi5 * at minimum the GPIO enable-gpios for display, and
19 /* 3.3V GPIO controlled regulator for LCD_ENVDD */
Domap3-overo-tobiduo-common.dtsi24 interrupts = <16 IRQ_TYPE_LEVEL_LOW>; /* GPIO 176 */
59 interrupts = <1 IRQ_TYPE_LEVEL_LOW>; /* GPIO 65 */
Dorion5x-maxtor-shared-storage-2.dts162 * GPIO 22: USB port 1 fuse (0 = Fail, 1 = Ok)
163 * GPIO 23: Blue front LED off
164 * GPIO 24: Inhibit board power off (0 = Disabled, 1 = Enabled)
Dsama5d3xmb.dtsi136 …<AT91_PIOD 17 AT91_PERIPH_GPIO AT91_PINCTRL_PULL_UP_DEGLITCH>; /* PD17 GPIO with pullup deglitch */
141 …<AT91_PIOD 18 AT91_PERIPH_GPIO AT91_PINCTRL_PULL_UP_DEGLITCH>; /* PD18 GPIO with pullup deglitch */
166 <AT91_PIOD 29 AT91_PERIPH_GPIO AT91_PINCTRL_DEGLITCH>; /* PD29 GPIO with deglitch */
/linux-4.4.14/Documentation/gpio/
Ddriver.txt1 GPIO Descriptor Driver Interface
4 This document serves as a guide for GPIO chip drivers writers. Note that it
6 deprecated integer-based GPIO interface please refer to gpio-legacy.txt.
8 Each GPIO controller driver needs to include the following header, which defines
9 the structures used to define a GPIO driver:
17 Inside a GPIO driver, individual GPIOs are identified by their hardware number,
20 GPIO descriptor is never made visible outside of the driver.
22 On top of this internal number, each GPIO also need to have a global number in
23 the integer GPIO namespace so that it can be used with the legacy GPIO
25 assigned), and for each GPIO the global number will be (base + hardware number).
[all …]
Dboard.txt1 GPIO Mappings
6 description of the deprecated integer-based GPIO interface please refer to
9 corresponding GPIO.
11 Platforms that make use of GPIOs must select ARCH_REQUIRE_GPIOLIB (if GPIO usage
12 is mandatory) or ARCH_WANT_OPTIONAL_GPIOLIB (if GPIO support can be omitted) in
20 exact way to do it depends on the GPIO controller providing the GPIOs, see the
42 "led" function, and GPIO 1 as the "power" GPIO:
52 The led GPIOs will be active-high, while the power GPIO will be active-low (i.e.
56 the <function>-prefix of the GPIO suffixes ("gpios" or "gpio", automatically
60 Internally, the GPIO subsystem prefixes the GPIO suffix ("gpios" or "gpio")
[all …]
Dconsumer.txt1 GPIO Descriptor Consumer Interface
4 This document describes the consumer interface of the GPIO framework. Note that
6 deprecated integer-based GPIO interface please refer to gpio-legacy.txt.
12 Drivers that can't work without standard GPIO calls should have Kconfig entries
18 All the functions that work with the descriptor-based GPIO interface are
29 device that will use the GPIO and the function the requested GPIO is supposed to
46 for the GPIO. Values can be:
48 * GPIOD_ASIS or 0 to not initialize the GPIO at all. The direction must be set
50 * GPIOD_IN to initialize the GPIO as input.
51 * GPIOD_OUT_LOW to initialize the GPIO as output with a value of 0.
[all …]
Ddrivers-on-gpio.txt1 Subsystem drivers using GPIO
4 Note that standard kernel drivers exist for common GPIO tasks and will provide
9 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 i.e. a LED will turn on/off in response to a GPIO line going high or low
16 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 GPIO line cannot generate interrupts, so it needs to be periodically polled
25 mouse cable and connect the wires to GPIO lines or solder a mouse connector
29 an external speaker connected to a GPIO line.
32 detection switches using GPIO, which is useful for your homebrewn pinball
38 HDMI connector. It will provide a better userspace sysfs interface than GPIO.
[all …]
Dsysfs.txt1 GPIO Sysfs Interface for Userspace
6 debugfs interface, since it provides control over GPIO direction and
11 know for example that GPIO #23 controls the write protect line used to
13 may need to temporarily remove that protection, first importing a GPIO,
15 the write protection. In normal use, GPIO #23 would never be touched,
19 userspace GPIO can be used to determine system configuration data that
21 GPIO drivers could be all that the system really needs.
36 - GPIO controllers ("gpio_chip" instances).
45 a GPIO to userspace by writing its number to this file.
48 for GPIO #19, if that's not requested by kernel code.
[all …]
Dgpio-legacy.txt1 GPIO Interfaces
3 This provides an overview of GPIO access conventions on Linux.
9 What is a GPIO?
11 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
13 to Linux developers working with embedded and custom hardware. Each GPIO
20 non-dedicated pin can be configured as a GPIO; and most chips have at least
24 also "GPIO Expander" chips that connect using the I2C or SPI serial busses.
25 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
37 cases (to support bidirectional signaling). GPIO controllers may have
44 - Usually a GPIO will be configurable as either input or output, as needed
[all …]
Dgpio.txt1 GPIO Interfaces
8 Due to the history of GPIO interfaces in the kernel, there are two different
21 What is a GPIO?
24 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
26 to Linux developers working with embedded and custom hardware. Each GPIO
33 non-dedicated pin can be configured as a GPIO; and most chips have at least
37 also "GPIO Expander" chips that connect using the I2C or SPI serial buses.
38 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
50 cases (to support bidirectional signaling). GPIO controllers may have
57 - Usually a GPIO will be configurable as either input or output, as needed
[all …]
D00-INDEX8 - How to write a GPIO driver
10 - Drivers in other subsystems that can use GPIO to provide more
15 - Information about the GPIO sysfs interface
17 - Historical documentation of the deprecated GPIO integer interface
/linux-4.4.14/Documentation/blackfin/
Dbfin-gpio-notes.txt20 1. Blackfin GPIO introduction
22 There are many GPIO pins on Blackfin. Most of these pins are muxed to
23 multi-functions. They can be configured as peripheral, or just as GPIO,
38 - Use the pin as GPIO,
41 - Use the pin as GPIO interrupt,
55 - Kernel permit the identical GPIO be requested both as GPIO and GPIO
59 bfin-gpio: GPIO 24 is already reserved by gpio-keys: BTN0, and you are
63 identical GPIO, one of them use it as GPIO, the other use it as
64 GPIO interrupt. This will really cause resource conflict. So if
68 - Kernel permit the identical GPIO be requested from the same driver twice.
Dbfin-spi-notes.txt11 timing, you can utilize the GPIO controlled SPI Slave Select option instead.
12 In this case, you should use GPIO based CS for all of your slaves and not just
16 but use it as a GPIO instead.
/linux-4.4.14/Documentation/i2c/muxes/
Di2c-mux-gpio9 from a master I2C bus and a hardware MUX controlled through GPIO pins.
17 | Linux | GPIO 1..N | MUX |--------------- Devices
24 according to the settings of the GPIO pins 1..N.
32 bus, the number of bus segments to create and the GPIO pins used
36 controlled through 3 GPIO pins:
67 If you don't know the absolute GPIO pin numbers at registration time,
68 you can instead provide a chip name (.chip_name) and relative GPIO pin
70 including deferred probing if the GPIO chip isn't immediately
77 of any GPIO pin it uses as the device ID. This guarantees that every
83 GPIO pin numbers at registration time, this is even the only option.
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dbrcm,bcm2835-gpio.txt1 Broadcom BCM2835 GPIO (and pinmux) controller
3 The BCM2835 GPIO module is a combined GPIO controller, (GPIO) interrupt
8 - reg: Should contain the physical address of the GPIO module's registers.
9 - gpio-controller: Marks the device node as a GPIO controller.
17 The first cell is the GPIO number.
26 Please refer to ../gpio/gpio.txt for a general description of GPIO bindings.
41 are the integer GPIO IDs; 0==GPIO0, 1==GPIO1, ... 53==GPIO53.
45 0: GPIO in
46 1: GPIO out
Dbrcm,cygnus-gpio.txt1 Broadcom Cygnus GPIO/PINCONF Controller
11 GPIO/PINCONF controller registers
14 Must be two. The first cell is the GPIO pin number (within the
19 Specifies that the node is a GPIO controller
33 2. GPIO base pin offset.
90 * Touchscreen that uses the CCM GPIO 0 and 1
99 /* Bluetooth that uses the ASIU GPIO 5, with polarity inverted */
Dpinctrl-vt8500.txt3 These SoCs contain a combined Pinmux/GPIO module. Each pin may operate as
4 either a GPIO in, GPIO out or as an alternate function (I2C, SPI etc).
12 - gpio-controller: Marks the device node as a GPIO controller.
17 Please refer to ../gpio/gpio.txt for a general description of GPIO bindings.
35 0: GPIO in
36 1: GPIO out
Dimg,pistachio-pinctrl.txt4 The pin controllers on Pistachio are a combined GPIO controller, (GPIO)
8 each. The GPIO banks are represented as sub-nodes of the pad controller node.
12 pin controller, GPIO, and interrupt bindings.
19 Required properties for GPIO bank sub-nodes:
21 - interrupts: Interrupt line for the GPIO bank.
22 - gpio-controller: Indicates the device is a GPIO controller.
23 - #gpio-cells: Must be two. The first cell is the GPIO pin number and the
27 - #interrupt-cells: Must be two. The first cell is the GPIO pin number and
31 Note that the N GPIO bank sub-nodes *must* be named gpio0, gpio1, ... gpioN-1.
Drenesas,pfc-pinctrl.txt1 * Renesas Pin Function Controller (GPIO and Pin Mux/Config)
4 R8A73A4 and R8A7740 it also acts as a GPIO controller.
30 - #gpio-range-cells: Mandatory when the PFC doesn't handle GPIO, forbidden
80 GPIO
83 On SH73A0, R8A73A4 and R8A7740 the PFC node is also a GPIO controller node.
89 - #gpio-cells: Should be 2. The first cell is the GPIO number and the second
90 cell specifies GPIO flags, as defined in <dt-bindings/gpio/gpio.h>. Only the
100 On other mach-shmobile platforms GPIO is handled by the gpio-rcar driver.
102 for documentation of the GPIO device tree bindings on those platforms.
127 Example 2: A GPIO LED node that references a GPIO
Dpinctrl-sirf.txt6 - interrupts : Interrupts used by every GPIO group
7 - gpio-controller : Indicates this device is a GPIO controller
10 - sirf,pullups : if n-th bit of m-th bank is set, set a pullup on GPIO-n of bank m
11 - sirf,pulldowns : if n-th bit of m-th bank is set, set a pulldown on GPIO-n of bank m
Dabilis,tb10x-iomux.txt25 - GPIO ports: gpioa, gpiob, gpioc, gpiod, gpioe, gpiof, gpiog,
42 GPIO ranges definition
45 The named pin groups of GPIO ports can be used to define GPIO ranges as
Dfsl,imx27-pinctrl.txt23 2 - GPIO
24 Registers: GIUS (GPIO In Use), GPR (General Purpose Register)
33 have any effect unless GPIO function is selected. A/B/C_IN are output
44 B. GPIO function should be selected if this is configured.
Dallwinner,sunxi-pinctrl.txt5 the first two functions being GPIO in and out. The configuration on
74 GPIO and interrupt controller
77 This hardware also acts as a GPIO controller and an interrupt
83 inside that bank, and finally the flags for the GPIO/interrupts.
Dpinctrl-st.txt4 PIO multiplexing block. Each pin supports GPIO functionality (ALT0)
8 When a pin is in GPIO mode, Output Enable (OE), Open Drain(OD), and
14 GPIO bank can have one of the two possible types of interrupt-wirings.
50 GPIO controller/bank node.
52 - gpio-controller : Indicates this device is a GPIO controller
61 - interrupt-controller : Indicates this device is a interrupt controller. GPIO
Dqcom,pmic-gpio.txt1 Qualcomm PMIC GPIO block
3 This binding describes the GPIO block(s) found in the 8xxx series of
22 Definition: Register base of the GPIO block and length.
28 each available GPIO
33 Definition: Mark the device node as a GPIO controller
43 a general description of GPIO and interrupt bindings.
Drockchip,pinctrl.txt6 muxing options with option 0 being the use as a GPIO.
46 - #gpio-cells: number of cells in GPIO specifier. Since the generic GPIO
48 GPIO binding documentation for description of particular cells.
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-gpio7 As a Kconfig option, individual GPIO signals may be accessed from
9 "export" operation. If a given GPIO is not claimed for use by
17 /export ... asks the kernel to export a GPIO to userspace
18 /unexport ... to return a GPIO to the kernel
19 /gpioN ... for each exported GPIO #N OR
20 /<LINE-NAME> ... for a properly named GPIO line
24 /gpiochipN ... for each gpiochip; #N is its first GPIO
/linux-4.4.14/Documentation/devicetree/bindings/net/ieee802154/
Dcc2520.txt10 - fifo-gpio: GPIO spec for the FIFO pin
11 - fifop-gpio: GPIO spec for the FIFOP pin
12 - sfd-gpio: GPIO spec for the SFD pin
13 - cca-gpio: GPIO spec for the CCA pin
14 - vreg-gpio: GPIO spec for the VREG pin
15 - reset-gpio: GPIO spec for the RESET pin
Dat86rf230.txt13 - reset-gpio: GPIO spec for the rstn pin
14 - sleep-gpio: GPIO spec for the slp_tr pin
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dgpio-control-nand.txt1 GPIO assisted NAND flash
3 The GPIO assisted NAND flash uses a memory mapped interface to
4 read/write the NAND commands and data and GPIO pins for the control
14 - gpios : Specifies the GPIO pins to control the NAND device. The order of
15 GPIO references is: RDY, nCE, ALE, CLE, and an optional nWP.
24 the GPIO's and the NAND flash data bus. If present, then after changing
25 GPIO state and before and after command byte writes, this register will be
26 read to ensure that the GPIO accesses have completed.
/linux-4.4.14/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.
54 ACPI GPIO Mappings Provided by Drivers
63 to be sufficient to determine the meaning and purpose of all of the GPIO lines
67 to the GPIO lines it is going to use and provide the GPIO subsystem with a
68 mapping between those names and the ACPI GPIO resources corresponding to them.
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/leds/
Dleds-ns2.txt1 Binding for dual-GPIO LED found on Network Space v2 (and parents).
9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.
12 the corresponding cmd-gpio/slow-gpio values. All the GPIO values combinations
Dleds-gpio.txt1 LEDs connected to GPIO lines
10 - gpios : Should specify the LED's GPIO, see "gpios property" in
12 indicated using flags in the GPIO specifier.
/linux-4.4.14/Documentation/
Dbt8xxgpio.txt4 == A driver for a selfmade cheap BT8xx based PCI GPIO-card ==
11 A generic digital 24-port PCI GPIO card can be built out of an ordinary
16 The bt8xx chip does have 24 digital GPIO ports.
21 == How to physically access the GPIO pins ==
26 GPIO pin and solder that to some tiny wire. As the chip package really is tiny
30 The GPIO pins are marked with G00-G23
Dpinctrl.txt99 also consider matching of offsets to the GPIO ranges that may be handled by
278 Interaction with the GPIO subsystem
281 The GPIO drivers may want to perform operations of various types on the same
291 which pin controller handles control of a certain GPIO pin. Since a single
292 pin controller may be muxing several GPIO ranges (typically SoCs that have
293 one set of pins, but internally several GPIO silicon blocks, each modelled as
294 a struct gpio_chip) any number of GPIO ranges can be added to a pin controller
326 GPIO chips. "chip a" has 16 pins and "chip b" has 8 pins. The "chip a" and
328 GPIO range.
330 The GPIO range of "chip a" starts from the GPIO base of 32 and actual
[all …]
Dbtmrvl.txt17 bit 16:8 -- GPIO
19 where GPIO is the pin number of GPIO used to wake up the host.
20 It could be any valid GPIO pin# (e.g. 0-7) or 0xff (SDIO interface
31 # Use GPIO pin #3 to wake up the host and set GAP to 0xff:
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dgpio-regulator.txt1 GPIO controlled regulators
5 - states : Selection of available voltages and GPIO configs.
9 - enable-gpio : GPIO to use to enable/disable the regulator.
10 - gpios : GPIO group used to control voltage.
14 - enable-active-high : Polarity of GPIO is active high (default is low).
Dmax8973-regulator.txt17 -maxim,enable-gpio: GPIO for enable control. If the valid GPIO is provided
19 -maxim,dvs-gpio: GPIO which is connected to DVS pin of device.
20 -maxim,dvs-default-state: Default state of GPIO during initialisation.
Dtps62360-regulator.txt14 - ti,vsel0-gpio: GPIO for controlling VSEL0 line.
15 If this property is missing, then assume that there is no GPIO
18 If this property is missing, then assume that there is no GPIO
Darizona-regulator.txt11 - wlf,ldoena : GPIO specifier for the GPIO controlling LDOENA
Dfixed-regulator.txt9 - enable-active-high: Polarity of GPIO is Active high
11 - gpio-open-drain: GPIO is open drain type.
Ds5m8767-regulator.txt25 - s5m8767,pmic-buck-ds-gpios: GPIO specifiers for three host gpio's used
26 for selecting GPIO DVS lines. It is one-to-one mapped to dvs gpio lines.
54 - s5m8767,pmic-buck-dvs-gpios: GPIO specifiers for three host gpio's used
79 - s5m8767,pmic-ext-control-gpios: (optional) GPIO specifier for one
80 GPIO controlling this regulator (enable/disable); This is
Dmax8952.txt11 - max8952,vid-gpios: array of two GPIO pins used for DVS voltage selection
12 - max8952,en-gpio: GPIO used to control enable status of regulator
Dtps65090.txt20 If DCDCs are externally controlled and if it is from GPIO then GPIO
21 number should be provided. If it is externally controlled and no GPIO
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dvexpress-sysreg.txt12 Deprecated properties, replaced by GPIO subnodes (see below):
13 - gpio-controller : specifies that the node is a GPIO controller
14 - #gpio-cells : size of the GPIO specifier, should be 2:
15 - first cell is the pseudo-GPIO line number:
19 - second cell can take standard GPIO flags (currently ignored).
21 Control registers providing pseudo-GPIO lines must be represented
27 - gpio-controller : makes the node a GPIO controller
28 - #gpio-cells : size of the GPIO specifier, must be 2:
33 - second cell can take standard GPIO flags (currently ignored).
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Drt5677.txt13 - gpio-controller : Indicates this device is a GPIO controller.
20 - realtek,pow-ldo2-gpio : The GPIO that controls the CODEC's POW_LDO2 pin.
21 - realtek,reset-gpio : The GPIO that controls the CODEC's RESET pin.
32 Array of six 8bit elements that configures GPIO.
38 Configures GPIO Mic Jack detection 1.
43 Configures GPIO Mic Jack detection 2 and 3.
Dnokia,rx51.txt9 - tvout-selection-gpios: GPIO for tvout selection
10 - jack-detection-gpios: GPIO for jack detection
11 - eci-switch-gpios: GPIO for ECI (Enhancement Control Interface) switch
12 - speaker-amplifier-gpios: GPIO for speaker amplifier
Dnvidia,tegra20-ac97.txt18 - nvidia,codec-reset-gpio : The Tegra GPIO controller's phandle and the number
19 of the GPIO used to reset the external AC97 codec
20 - nvidia,codec-sync-gpio : The Tegra GPIO controller's phandle and the number
21 of the GPIO corresponding with the AC97 DAP _FS line
Dwm8903.txt11 - gpio-controller : Indicates this device is a GPIO controller.
26 - gpio-cfg : A list of GPIO configuration register values. The list must
28 performed. If any entry has the value 0xffffffff, that GPIO's
65 0x0000 /* GPIO, output, low */
Dnvidia,tegra-audio-wm8903.txt26 - nvidia,spkr-en-gpios : The GPIO that enables the speakers
27 - nvidia,hp-mute-gpios : The GPIO that mutes the headphones
28 - nvidia,hp-det-gpios : The GPIO that detect headphones are plugged in
29 - nvidia,int-mic-en-gpios : The GPIO that enables the internal microphone
30 - nvidia,ext-mic-en-gpios : The GPIO that enables the external microphone
Dnvidia,tegra-audio-rt5677.txt30 - nvidia,hp-det-gpios : The GPIO that detects headphones are plugged in
31 - nvidia,hp-en-gpios : The GPIO that enables headphone amplifier
32 - nvidia,mic-present-gpios: The GPIO that mic jack is plugged in
33 - nvidia,dmic-clk-en-gpios : The GPIO that gates DMIC clock signal
Dwm8804.txt18 - wlf,reset-gpio: A GPIO specifier for the GPIO controlling the reset pin
Dwm8994.txt13 - gpio-controller : Indicates this device is a GPIO controller.
39 - wlf,gpio-cfg : A list of GPIO configuration register values. If absent,
47 - wlf,ldo1ena : GPIO specifier for control of LDO1ENA input to device.
48 - wlf,ldo2ena : GPIO specifier for control of LDO2ENA input to device.
Dwm8962.txt19 - gpio-cfg : A list of GPIO configuration register values. The list must
22 Any other value is regarded as setting the GPIO register by its reset
Dadi,adau1701.txt11 - reset-gpio: A GPIO spec to define which pin is connected to the
14 - adi,pll-mode-gpios: An array of two GPIO specs to describe the GPIOs
Dtas571x.txt15 - reset-gpios: GPIO specifier for the TAS571x's active low reset line
16 - pdn-gpios: GPIO specifier for the TAS571x's active low powerdown line
Dcs42l52.txt11 - cirrus,reset-gpio : GPIO controller's phandle and the number
12 of the GPIO used to reset the codec.
Dnvidia,tegra-audio-max98090.txt28 - nvidia,hp-det-gpios : The GPIO that detect headphones are plugged in
29 - nvidia,mic-det-gpios : The GPIO that detect microphones are plugged in
/linux-4.4.14/Documentation/devicetree/bindings/iio/temperature/
Dmlx90614.txt12 - wakeup-gpios: device tree identifier of the GPIO connected to the SDA line
14 GPIO is set as input and will not interfere in I2C communication. There
15 is no need for a GPIO driving the SCL line. If no GPIO is given, power
/linux-4.4.14/Documentation/devicetree/bindings/spi/
Dspi-gpio.txt1 SPI-GPIO devicetree bindings
8 - gpio-sck: GPIO spec for the SCK line to use
9 - gpio-miso: GPIO spec for the MISO line to use
10 - gpio-mosi: GPIO spec for the MOSI line to use
Dspi-davinci.txt19 GPIO chip selects.
30 For example to have 3 internal CS and 2 GPIO CS, user could define
32 where first three are internal CS and last two are GPIO CS.
/linux-4.4.14/drivers/pinctrl/intel/
DKconfig6 bool "Intel Baytrail GPIO pin control"
10 driver for memory mapped GPIO functionality on Intel Baytrail
18 tristate "Intel Cherryview/Braswell pinctrl and GPIO driver"
38 tristate "Intel Broxton pinctrl and GPIO driver"
46 tristate "Intel Sunrisepoint pinctrl and GPIO driver"
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Dnxp,sc16is7xx.txt19 - gpio-controller: Marks the device node as a GPIO controller.
20 - #gpio-cells: Should be two. The first cell is the GPIO number and
21 the second cell is used to specify the GPIO polarity:
55 - gpio-controller: Marks the device node as a GPIO controller.
56 - #gpio-cells: Should be two. The first cell is the GPIO number and
57 the second cell is used to specify the GPIO polarity:
Dmaxim,max310x.txt20 - gpio-controller: Marks the device node as a GPIO controller.
21 - #gpio-cells: Should be two. The first cell is the GPIO number and
22 the second cell is used to specify the GPIO polarity:
/linux-4.4.14/Documentation/hwmon/
Dltc424575 in9_input GPIO voltage data (see note 1)
76 in10_input GPIO voltage data (see note 1)
77 in11_input GPIO voltage data (see note 1)
88 If you have NOT configured the driver to sample all GPIO pins as analog
90 created. The driver will sample the GPIO pin that is currently connected to the
93 If you have configured the driver to sample all GPIO pins as analog voltages,
98 The LTC4245 chip can be configured to sample all GPIO pins with two methods:
102 The default mode of operation is to sample a single GPIO pin.
Dadm102619 List of GPIO pins (0-16) to program as inputs
21 List of GPIO pins (0-16) to program as outputs
23 List of GPIO pins (0-16) to program as inverted
25 List of GPIO pins (0-16) to program as normal/non-inverted
27 List of GPIO pins (0-7) to program as fan tachs
91 GPIO lines. Unfortunately, the chip may not be connected to the VID lines
/linux-4.4.14/Documentation/arm/pxa/
Dmfp.txt12 Unlike the GPIO alternate function settings on PXA25x and PXA27x, a new MFP
14 out of the GPIO controller. In addition to pin-mux configurations, the MFP
21 | GPIO | |
22 | |--(GPIO...) |
43 can be routed from GPIO19 of the GPIO controller.
45 To better understand the change from PXA25x/PXA27x GPIO alternate function
48 1. GPIO controller on PXA3xx is now a dedicated controller, same as other
50 which can be routed to external through one or more MFPs (e.g. GPIO<0>
54 2. Alternate function configuration is removed from this GPIO controller,
55 the remaining functions are pure GPIO-specific, i.e.
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dtc3589x.txt26 - GPIO
27 This GPIO module inside the TC3589x has 24 (TC35890, TC35892) or 20
28 (other models) GPIO lines.
33 TC3589x GPIO interrupt controller, the second cell is the interrupt flags
41 - gpio-controller : marks the device node as a GPIO controller
42 - #gpio-cells : should be <2>, the first cell is the GPIO offset on this
43 GPIO controller, the second cell is the flags.
Darizona.txt29 - gpio-controller : Indicates this device is a GPIO controller.
46 - wlf,reset : GPIO specifier for the GPIO controlling /RESET
48 - wlf,gpio-defaults : A list of GPIO configuration register values. Defines
Das3722.txt27 Pinmux and GPIO:
29 Device has 8 GPIO pins which can be configured as GPIO as well as the special IO
36 Following are properties which is needed if GPIO and pinmux functionality
40 - gpio-controller: Marks the device node as a GPIO controller.
41 - #gpio-cells: Number of GPIO cells. Refer to binding document
/linux-4.4.14/Documentation/arm/Samsung/
DGPIO.txt1 Samsung GPIO implementation
7 This outlines the Samsung GPIO implementation and the architecture
14 See Documentation/arm/Samsung-S3C24XX/GPIO.txt for more information
26 GPIO numbering is synchronised between the Samsung and gpiolib system.
/linux-4.4.14/Documentation/w1/masters/
Dw1-gpio10 GPIO 1-wire bus master driver. The driver uses the GPIO API to control the
11 wire and the GPIO pin can be specified using platform data.
/linux-4.4.14/Documentation/devicetree/bindings/pps/
Dpps-gpio.txt1 Device-Tree Bindings for a PPS Signal on GPIO
4 a GPIO pin.
8 - gpios: one PPS GPIO in the format described by ../gpio/gpio.txt
/linux-4.4.14/Documentation/devicetree/bindings/net/nfc/
Ds3fwrn5.txt7 - interrupts: GPIO interrupt to which the chip is connected
8 - s3fwrn5,en-gpios: Output GPIO pin used for enabling/disabling the chip
9 - s3fwrn5,fw-gpios: Output GPIO pin used to enter firmware mode and
Dpn544.txt8 - interrupts: GPIO interrupt to which the chip is connected
9 - enable-gpios: Output GPIO pin used for enabling/disabling the PN544
10 - firmware-gpios: Output GPIO pin used to enter firmware download mode
Dnxp-nci.txt8 - interrupts: GPIO interrupt to which the chip is connected
9 - enable-gpios: Output GPIO pin used for enabling/disabling the chip
10 - firmware-gpios: Output GPIO pin used to enter firmware download mode
Dst-nci-spi.txt7 - interrupts: GPIO interrupt to which the chip is connected
8 - reset-gpios: Output GPIO pin used to reset the ST21NFCB
Dst-nci-i2c.txt8 - interrupts: GPIO interrupt to which the chip is connected
9 - reset-gpios: Output GPIO pin used to reset the ST21NFCB
Dst21nfca.txt8 - interrupts: GPIO interrupt to which the chip is connected
9 - enable-gpios: Output GPIO pin used for enabling/disabling the ST21NFCA
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dusb-nop-xceiv.txt18 - reset-gpios: Should specify the GPIO for reset.
20 - vbus-detect-gpio: should specify the GPIO detecting a VBus insertion
40 hsusb1_vcc_regulator provides power to the PHY and GPIO 7 controls RESET.
41 GPIO 13 detects VBus insertion, and accordingly notifies the vbus-regulator.
Dusb3503.txt9 - connect-gpios: Should specify GPIO for connect.
14 - intn-gpios: Should specify GPIO for interrupt.
15 - reset-gpios: Should specify GPIO for reset.
/linux-4.4.14/arch/arc/boot/dts/
Daxc003.dtsi33 * this GPIO block ORs all interrupts on CPU card (creg,..)
76 * DT "invisible" DW APB GPIO block, configured to simply pass thru
80 * ABPG GPIO. Thus set "interrupts = <24>" (DW APB GPIO to core)
81 * instead of "interrupts = <12>" (DW APB ICTL to DW APB GPIO)
Dabilis_tb101.dtsi51 pctl_gpio_a: pctl-gpio-a { /* GPIO bank A */
64 pctl_gpio_c: pctl-gpio-c { /* GPIO bank C */
77 pctl_gpio_e: pctl-gpio-e { /* GPIO bank E */
90 pctl_gpio_g: pctl-gpio-g { /* GPIO bank G */
97 pctl_gpio_j: pctl-gpio-j { /* GPIO bank J */
100 pctl_gpio_k: pctl-gpio-k { /* GPIO bank K */
138 pctl_gpio_l: pctl-gpio-l { /* GPIO bank L */
141 pctl_gpio_m: pctl-gpio-m { /* GPIO bank M */
Dabilis_tb100.dtsi51 pctl_gpio_a: pctl-gpio-a { /* GPIO bank A */
64 pctl_gpio_c: pctl-gpio-c { /* GPIO bank C */
77 pctl_gpio_e: pctl-gpio-e { /* GPIO bank E */
90 pctl_gpio_g: pctl-gpio-g { /* GPIO bank G */
97 pctl_gpio_j: pctl-gpio-j { /* GPIO bank J */
100 pctl_gpio_k: pctl-gpio-k { /* GPIO bank K */
132 pctl_gpio_l: pctl-gpio-l { /* GPIO bank L */
135 pctl_gpio_m: pctl-gpio-m { /* GPIO bank M */
Daxc001.dtsi34 * this GPIO block ORs all interrupts on CPU card (creg,..)
73 * This INTC is actually connected to DW APB GPIO
75 * GPIO INTC is configured in platform init code
Daxc003_idu.dtsi51 * this GPIO block ORs all interrupts on CPU card (creg,..)
98 * This INTC is actually connected to DW APB GPIO
100 * GPIO INTC is configured in platform init code
/linux-4.4.14/arch/arm/mach-davinci/
Dboard-neuros-osd2.c133 { .name = "led1_green", .gpio = GPIO(10), },
134 { .name = "led1_red", .gpio = GPIO(11), },
135 { .name = "led2_green", .gpio = GPIO(12), },
136 { .name = "led2_red", .gpio = GPIO(13), },
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dmdio-mux-gpio.txt1 Properties for an MDIO bus multiplexer/switch controlled by GPIO pins.
3 This is a special case of a MDIO bus multiplexer. One or more GPIO
9 - gpios : GPIO specifiers for each GPIO line. One or more must be specified.
24 pair of GPIO lines. Child busses 2 and 3 populated with 4
Dsmsc-lan91c111.txt14 - power-gpios: GPIO to control the PWRDWN pin
15 - reset-gpios: GPIO to control the RESET pin
Dbroadcom-bcm87xx.txt25 * GPIO[1] Tx/Rx
26 * GPIO[0] R64 Sync Acquired
/linux-4.4.14/Documentation/devicetree/bindings/extcon/
Dextcon-palmas.txt14 it performs id-detection using GPIO else using OTG core.
16 - id-gpio: gpio for GPIO ID detection. See gpio binding.
17 - debounce-delay-ms: debounce delay for GPIO ID pin in milliseconds.
Dextcon-usb-gpio.txt1 USB GPIO Extcon device
4 connected to a GPIO pin.
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dgpio-matrix-keypad.txt1 * GPIO driven matrix keypad device tree bindings
3 GPIO driven matrix keypad is used to interface a SoC with a matrix keypad.
6 keypad can sense a key-press and key-release by means of GPIO lines and
7 report the event using GPIO interrupts to the cpu.
Dgpio-beeper.txt1 * GPIO beeper device tree bindings
3 Register a beeper connected to GPIO pin.
Dcypress,cyapa.txt30 interrupts = <2 IRQ_TYPE_EDGE_FALLING>; /* GPIO 2 */
39 interrupts = <2 IRQ_TYPE_EDGE_FALLING>; /* GPIO 2 */
Dgpio-keys.txt40 label = "GPIO Key UP";
45 label = "GPIO Key DOWN";
/linux-4.4.14/drivers/i2c/muxes/
DKconfig9 tristate "GPIO-based I2C arbitration"
16 a GPIO.
22 tristate "GPIO-based I2C multiplexer"
26 GPIO based I2C multiplexer. This driver provides access to
28 through GPIO pins.
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DGPIO.txt1 S3C24XX GPIO Control
8 manipulate the state of the GPIO pins, and find out other
12 of the s3c2410 GPIO system, please read the Samsung provided
15 See Documentation/arm/Samsung/GPIO.txt for the core implementation.
22 of the GPIO functions such as reading and writing a pin will
47 1) If your board is exclusively using an GPIO, say to control peripheral
89 of GPIO pins, and the configuration values for them. This
98 the GPIO functions which pin is to be used.
138 A large proportion of the GPIO pins on the S3C2410 can have weak
/linux-4.4.14/Documentation/devicetree/bindings/power/reset/
Dltc2952-poweroff.txt10 - watchdog-gpios: phandle + gpio-specifier for the GPIO connected to the
12 - kill-gpios: phandle + gpio-specifier for the GPIO connected to the
16 - trigger-gpios: phandle + gpio-specifier for the GPIO connected to the
/linux-4.4.14/Documentation/devicetree/bindings/watchdog/
Dgpio-wdt.txt1 * GPIO-controlled Watchdog
9 the WDT counter. The watchdog timer is disabled when GPIO is
13 by the GPIO flags.
/linux-4.4.14/Documentation/devicetree/bindings/leds/backlight/
Dpwm-backlight.txt18 - enable-gpios: contains a single GPIO specifier for the GPIO which enables
19 and disables the backlight (see GPIO binding[1])
/linux-4.4.14/drivers/w1/masters/
DKconfig12 using Matrox's G400 GPIO pins.
51 tristate "GPIO 1-wire busmaster"
55 GPIO pins. This driver uses the GPIO API to control the wire.
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-mux-gpio.txt1 GPIO-based I2C Bus Mux
11 | +------+ | +------+ child bus A, on GPIO value set to 0
13 | +------+ | +--+---+ child bus B, on GPIO value set to 1
16 | | GPIO |-|-----+ +-----+ +-----+ +-----+
Di2c-s3c2410.txt12 on EXYNOS5440 which does not need GPIO configuration.
21 - Samsung GPIO variant (deprecated):
45 /* Samsung GPIO variant begins here */
48 /* Samsung GPIO variant ends here */
Di2c-arb-gpio-challenge.txt1 GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
3 This uses GPIO lines and a challenge & response mechanism to arbitrate who is
44 - our-claim-gpio: The GPIO that we use to claim the bus.
51 - slew-delay-us: microseconds to wait for a GPIO to go high. Default is 10 us.
/linux-4.4.14/drivers/pps/clients/
DKconfig33 tristate "PPS client using GPIO"
37 GPIO. To be useful you must also register a platform device
38 specifying the GPIO pin and other options, usually in your board
/linux-4.4.14/drivers/extcon/
DKconfig39 tristate "GPIO extcon support"
42 Say Y here to enable GPIO based extcon support. Note that GPIO
114 tristate "USB GPIO extcon support"
117 Say Y here to enable GPIO based USB cable detection extcon support.
118 Used typically if GPIO is used for USB ID pin detection.
/linux-4.4.14/arch/arm/mach-omap1/
Dams-delta-fiq-handler.S113 cmp r10, #INT_GPIO_BANK1 @ is it GPIO bank interrupt?
125 gpio: @ GPIO bank interrupt handler
126 ldr r12, omap1510_gpio_base @ set base pointer to GPIO bank
128 ldr r11, [r12, #OMAP1510_GPIO_INT_MASK] @ fetch GPIO interrupts mask
149 ldr r8, [r12, #OMAP1510_GPIO_DATA_INPUT] @ fetch GPIO input
165 @ Mask other GPIO line interrupts till key done
174 @ r8 still contains GPIO input bits
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dgpio-ir-receiver.txt1 Device-Tree bindings for GPIO IR receiver
5 - gpios: specifies GPIO used for IR signal reception.
/linux-4.4.14/Documentation/devicetree/bindings/display/panel/
Dsharp,ls037v7dw01.txt9 - enable-gpios: a GPIO spec for the optional enable pin.
11 - reset-gpios: a GPIO spec for the optional reset pin.
13 - mode-gpios: a GPIO
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dgpio.txt1 Every GPIO controller node must have #gpio-cells property defined,
15 - gpio-controller : Marks the port as GPIO controller.
17 Example of three SOC GPIO banks defined as gpio-controller nodes:
/linux-4.4.14/drivers/watchdog/
Dit87_wdt.c68 #define GPIO 0x07 macro
275 superio_select(GPIO); in wdt_keepalive()
288 superio_select(GPIO); in wdt_start()
306 superio_select(GPIO); in wdt_stop()
342 superio_select(GPIO); in wdt_set_timeout()
370 superio_select(GPIO); in wdt_get_status()
658 superio_select(GPIO); in it87_wdt_init()
767 superio_select(GPIO); in it87_wdt_exit()
/linux-4.4.14/arch/sh/kernel/cpu/sh4a/
Dsetup-sh7763.c251 SCIF2, GPIO, enumerator
297 INTC_VECT(GPIO, 0xf80), INTC_VECT(GPIO, 0xfa0),
298 INTC_VECT(GPIO, 0xfc0), INTC_VECT(GPIO, 0xfe0),
308 { 0, 0, 0, 0, 0, 0, GPIO, 0,
330 { 0xffd4001c, 0, 32, 8, /* INT2PRI7 */ { SCIF2, GPIO } },
Dsetup-sh7780.c311 SCIF1, SIOF, HSPI, MMCIF, TMU3, TMU4, TMU5, SSI, FLCTL, GPIO, enumerator
350 INTC_VECT(GPIO, 0xf80), INTC_VECT(GPIO, 0xfa0),
351 INTC_VECT(GPIO, 0xfc0), INTC_VECT(GPIO, 0xfe0),
361 { 0, 0, 0, 0, 0, 0, GPIO, FLCTL,
378 { 0xffd4001c, 0, 32, 8, /* INT2PRI7 */ { FLCTL, GPIO } },
Dsetup-sh7785.c393 FLCTL, GPIO, enumerator
437 INTC_VECT(GPIO, 0xf80), INTC_VECT(GPIO, 0xfa0),
438 INTC_VECT(GPIO, 0xfc0), INTC_VECT(GPIO, 0xfe0),
461 { 0, 0, 0, GDTA, DU, SSI0, SSI1, GPIO,
482 { 0xffd40020, 0, 32, 8, /* INT2PRI8 */ { FLCTL, GPIO, SSI0, SSI1, } },
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
Dgpio-charger.txt5 - gpios : GPIO indicating the charger presence.
6 See GPIO binding in bindings/gpio/gpio.txt .
Dti,bq24735.txt10 - ti,ac-detect-gpios : This GPIO is optionally used to read the AC adapter
11 presence. This is a Host GPIO that is configured as an input and
/linux-4.4.14/Documentation/fmc/
Dcarrier.txt201 The method allows to configure a GPIO pin in the carrier, and read
202 its current value if it is configured as input. See *note The GPIO
221 The GPIO Abstraction
224 Support for GPIO pins in the fmc-bus environment is not very
230 driver can request to configure carrier-specific GPIO pins, numbered
252 the SPEC and the SVEC may request configuration of two different GPIO
256 If, however, your GPIO pin has a specific known role, you can pass a
266 Use of virtual GPIO numbers (anything but FMC_GPIO_RAW) is allowed
269 between virtual and physical GPIO numbers. The carrier may then use the
280 suitable GPIO pins. Clearly, the person running the drivers will know
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dpixcir_i2c_ts.txt7 - attb-gpio: GPIO connected to the ATTB line of the chip
12 - reset-gpio: GPIO connected to the RESET line of the chip
Dedt-ft5x06.txt30 - reset-gpios: GPIO specification for the RESET input
31 - wake-gpios: GPIO specification for the WAKE input
/linux-4.4.14/Documentation/devicetree/bindings/board/
Dfsl-board.txt51 * Freescale BCSR GPIO banks
53 Some BCSR registers act as simple GPIO controllers, each such
58 - reg : Should contain the address and the length of the GPIO bank
62 - gpio-controller : Marks the port as GPIO controller.
/linux-4.4.14/drivers/power/reset/
DKconfig53 bool "GPIO power-off driver"
56 This driver supports turning off your board via a GPIO line.
57 If your board needs a GPIO high/low to power down, say Y and
61 bool "GPIO restart driver"
64 This driver supports restarting your board via a GPIO line.
65 If your board needs a GPIO high/low to restart, say Y and
/linux-4.4.14/drivers/media/pci/zoran/
Dzoran_card.c256 GPIO(zr, 4, 0); in dc10_init()
257 GPIO(zr, 5, 1); in dc10_init()
259 GPIO(zr, 7, 0); in dc10_init()
284 GPIO(zr, 2, 1); // Set Composite input/output in lml33_init()
297 GPIO(zr, 4, 1); /* Bt866 SLEEP on */ in avs6eyes_init()
300 GPIO(zr, 0, 1); /* ZR36060 /RESET on */ in avs6eyes_init()
301 GPIO(zr, 1, 0); /* ZR36060 /SLEEP on */ in avs6eyes_init()
302 GPIO(zr, 2, mux & 1); /* MUX S0 */ in avs6eyes_init()
303 GPIO(zr, 3, 0); /* /FRAME on */ in avs6eyes_init()
304 GPIO(zr, 4, 0); /* Bt866 SLEEP off */ in avs6eyes_init()
[all …]
/linux-4.4.14/drivers/net/wireless/mwifiex/
DREADME202 echo "<condition> [GPIO# [gap]]]" > hscfg
210 [GPIO#]: pin number of GPIO used to wakeup the host.
211 GPIO pin# (e.g. 0-7) or 0xff (interface, e.g. SDIO
215 acknowledge required) when GPIO is used to wakeup host.
220 Use GPIO and gap set previously
221 echo "2 3" > hscfg : Unicast data and GPIO 3;
223 echo "2 1 160" > hscfg : Unicast data, GPIO 1 and gap 160 ms
224 echo "2 1 0xff" > hscfg : Unicast data, GPIO 1; Wait for host
/linux-4.4.14/Documentation/devicetree/bindings/security/tpm/
Dst33zp24-spi.txt9 - interrupts: GPIO interrupt to which the chip is connected
10 - lpcpd-gpios: Output GPIO pin used for ST33ZP24 power management D1/D2 state.
Dst33zp24-i2c.txt10 - interrupts: GPIO interrupt to which the chip is connected
11 - lpcpd-gpios: Output GPIO pin used for ST33ZP24 power management D1/D2 state.
/linux-4.4.14/Documentation/video4linux/
Dhauppauge-wintv-cx88-ir.txt1 The controls for the mux are GPIO [0,1] for source, and GPIO 2 for muting.
9 GPIO 16(i believe) is tied to the IR port (if present).
/linux-4.4.14/Documentation/video4linux/cx88/
Dhauppauge-wintv-cx88-ir.txt1 The controls for the mux are GPIO [0,1] for source, and GPIO 2 for muting.
9 GPIO 16(i believe) is tied to the IR port (if present).
/linux-4.4.14/arch/powerpc/platforms/pasemi/
DKconfig35 tristate "MDIO support via GPIO"
38 Driver for MDIO via GPIO on PWRficient platforms
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dmmc-spi-slot.txt13 - gpios : may specify GPIOs in this order: Card-Detect GPIO,
14 Write-Protect GPIO. Note that this does not follow the
Dmmc-pwrseq-emmc.txt15 - reset-gpios : contains a GPIO specifier. The reset GPIO is asserted
/linux-4.4.14/Documentation/spi/
Dep93xx_spi5 selects are implemented with GPIO lines.
8 not work correctly (it cannot be controlled by software). Use GPIO lines
31 /* this is our GPIO line used for chip select */
/linux-4.4.14/sound/pci/ctxfi/
Dcthw20k1.c1417 gpioorg = (u16)hw_read_20kx(hw, GPIO); in hw_reset_dac()
1419 hw_write_20kx(hw, GPIO, gpioorg); in hw_reset_dac()
1421 hw_write_20kx(hw, GPIO, gpioorg | 0x2); in hw_reset_dac()
1440 gpioorg = (u16)hw_read_20kx(hw, GPIO); in hw_dac_init()
1443 hw_write_20kx(hw, GPIO, gpioorg); in hw_dac_init()
1448 gpioorg = (u16)hw_read_20kx(hw, GPIO); in hw_dac_init()
1450 hw_write_20kx(hw, GPIO, gpioorg); in hw_dac_init()
1485 gpioorg = (u16)hw_read_20kx(hw, GPIO); in hw_dac_init()
1487 hw_write_20kx(hw, GPIO, gpioorg); in hw_dac_init()
1503 data = hw_read_20kx(hw, GPIO); in is_adc_input_selected_SBx()
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/hsi/
Dnokia-modem.txt15 - gpios: Should provide a GPIO handler for each GPIO listed in
/linux-4.4.14/Documentation/devicetree/bindings/media/i2c/
Dov2640.txt13 - resetb-gpios: reference to the GPIO connected to the resetb pin, if any.
14 - pwdn-gpios: reference to the GPIO connected to the pwdn pin, if any.
Dtc358743.txt14 - reset-gpios: gpio phandle GPIO connected to the reset pin
15 - interrupts, interrupt-parent: GPIO connected to the interrupt pin
/linux-4.4.14/sound/pci/ca0106/
Dca0106_mixer.c87 val = inl(emu->port + GPIO) & ~0x101; in ca0106_spdif_enable()
88 outl(val, emu->port + GPIO); in ca0106_spdif_enable()
96 val = inl(emu->port + GPIO) | 0x101; in ca0106_spdif_enable()
97 outl(val, emu->port + GPIO); in ca0106_spdif_enable()
136 tmp = inl(emu->port+GPIO) & ~0x400; in ca0106_set_capture_mic_line_in()
138 outl(tmp, emu->port+GPIO); in ca0106_set_capture_mic_line_in()
142 tmp = inl(emu->port+GPIO) & ~0x400; in ca0106_set_capture_mic_line_in()
143 outl(tmp, emu->port+GPIO); in ca0106_set_capture_mic_line_in()
/linux-4.4.14/drivers/pinctrl/qcom/
DKconfig71 This is the GPIO driver for the TLMM block found on the
83 Qualcomm GPIO and MPP blocks found in the Qualcomm PMIC's chips,
95 Qualcomm GPIO and MPP blocks found in the Qualcomm PMIC's chips,
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/
Dedp.txt24 - panel-en-gpios: GPIO pin to supply power to panel.
25 - panel-hpd-gpios: GPIO pin used for eDP hpd.
/linux-4.4.14/drivers/staging/sm750fb/
Dddk750_power.c149 gate = FIELD_SET(gate, CURRENT_GATE, GPIO, ON); in enableGPIO()
151 gate = FIELD_SET(gate, CURRENT_GATE, GPIO, OFF); in enableGPIO()
Dddk750_hwi2c.c55 value = FIELD_SET(value, GPIO_MUX, 30, GPIO); in sm750_hw_i2c_close()
56 value = FIELD_SET(value, GPIO_MUX, 31, GPIO); in sm750_hw_i2c_close()

123