Home
last modified time | relevance | path

Searched +full:gpio +full:- +full:open +full:- +full:drain (Results 1 – 25 of 36) sorted by relevance

12

/Documentation/devicetree/bindings/i2c/
Di2c-gpio.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Bindings for GPIO bitbanged I2C
10 - Wolfram Sang <wolfram@the-dreams.de>
13 - $ref: /schemas/i2c/i2c-controller.yaml#
18 - const: i2c-gpio
20 sda-gpios:
22 gpio used for the sda signal, this should be flagged as
[all …]
/Documentation/driver-api/gpio/
Dintro.rst6 GPIO Interfaces
13 Due to the history of GPIO interfaces in the kernel, there are two different
16 - The descriptor-based interface is the preferred way to manipulate GPIOs,
17 and is described by all the files in this directory excepted gpio-legacy.txt.
18 - The legacy integer-based interface which is considered deprecated (but still
19 usable for compatibility reasons) is documented in gpio-legacy.txt.
21 The remainder of this document applies to the new descriptor-based interface.
22 gpio-legacy.txt contains the same information applied to the legacy
23 integer-based interface.
26 What is a GPIO?
[all …]
Dconsumer.rst2 GPIO Descriptor Consumer Interface
5 This document describes the consumer interface of the GPIO framework. Note that
6 it describes the new descriptor-based interface. For a description of the
7 deprecated integer-based GPIO interface please refer to gpio-legacy.txt.
13 Drivers that can't work without standard GPIO calls should have Kconfig entries
17 #include <linux/gpio/consumer.h>
23 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that
27 - Truly optional GPIOLIB support - where the driver does not really make use
28 of the GPIOs on certain compile-time configurations for certain systems, but
29 will use it under other compile-time configurations. In this case the
[all …]
Ddriver.rst2 GPIO Driver Interface
5 This document serves as a guide for writers of GPIO chip drivers.
7 Each GPIO controller driver needs to include the following header, which defines
8 the structures used to define a GPIO driver:
10 #include <linux/gpio/driver.h>
16 A GPIO chip handles one or more GPIO lines. To be considered a GPIO chip, the
18 line is not general purpose, it is not GPIO and should not be handled by a
19 GPIO chip. The use case is the indicative: certain lines in a system may be
20 called GPIO but serve a very particular purpose thus not meeting the criteria
22 GPIO and should therefore still be handled by a GPIO chip driver.
[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
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
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
32 - Output values are writable (high=1, low=0). Some chips also have
[all …]
Dboard.rst2 GPIO Mappings
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
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
20 -----------
22 exact way to do it depends on the GPIO controller providing the GPIOs, see the
26 <function>-gpios, where <function> is the function the driver will request
[all …]
/Documentation/devicetree/bindings/w1/
Dw1-gpio.txt1 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>;
/Documentation/devicetree/bindings/regulator/
Dfixed-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/fixed-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
16 expected to have the regulator-min-microvolt and regulator-max-microvolt
20 - $ref: "regulator.yaml#"
26 const: regulator-fixed-clock
28 - clocks
[all …]
Dgpio-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO controlled regulators
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
18 - $ref: "regulator.yaml#"
22 const: regulator-gpio
24 regulator-name: true
[all …]
/Documentation/devicetree/bindings/mfd/
Dstmfx.txt1 STMicroelectonics Multi-Function eXpander (STMFX) Core bindings
3 ST Multi-Function eXpander (STMFX) is a slave controller using I2C for
4 communication with the main MCU. Its main features are GPIO expansion, main
9 - compatible: should be "st,stmfx-0300".
10 - reg: I2C slave address of the device.
11 - interrupts: interrupt specifier triggered by MFX_IRQ_OUT signal.
12 Please refer to ../interrupt-controller/interrupt.txt
15 - drive-open-drain: configure MFX_IRQ_OUT as open drain.
16 - vdd-supply: phandle of the regulator supplying STMFX.
21 compatible = "st,stmfx-0300";
[all …]
Das3722.txt4 -------------------
5 - compatible: Must be "ams,as3722".
6 - reg: I2C device address.
7 - interrupt-controller: AS3722 has internal interrupt controller which takes the
8 interrupt request from internal sub-blocks like RTC, regulators, GPIOs as well
10 - #interrupt-cells: Should be set to 2 for IRQ number and flags.
12 of AS3722 are defined at dt-bindings/mfd/as3722.h
14 interrupts.txt, using dt-bindings/irq.
17 --------------------
18 - ams,enable-internal-int-pullup: Boolean property, to enable internal pullup on
[all …]
/Documentation/devicetree/bindings/iio/gyroscope/
Dnxp,fxas21002c.txt3 http://www.nxp.com/products/sensors/gyroscopes/3-axis-digital-gyroscope:FXAS21002C
6 - compatible : should be "nxp,fxas21002c"
7 - reg : the I2C address of the sensor or SPI chip select number for the
9 - vdd-supply: phandle to the regulator that provides power to the sensor.
10 - vddio-supply: phandle to the regulator that provides power to the bus.
13 - reset-gpios : gpio used to reset the device, see gpio/gpio.txt
14 - interrupts : device support 2 interrupts, INT1 and INT2,
16 See interrupt-controller/interrupts.txt
17 - interrupt-names: should contain "INT1" or "INT2", the gyroscope interrupt
19 - drive-open-drain: the interrupt/data ready line will be configured
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-sx150x.txt1 SEMTECH SX150x GPIO expander bindings
3 Please refer to pinctrl-bindings.txt, ../gpio/gpio.txt, and
4 ../interrupt-controller/interrupts.txt for generic information regarding
5 pin controller, GPIO, and interrupt bindings.
8 - compatible: should be one of :
19 - reg: The I2C slave address for this device.
21 - #gpio-cells: Should be 2. The first cell is the GPIO number and the
25 - gpio-controller: Marks the device as a GPIO controller.
28 - interrupts: Interrupt specifier for the controllers interrupt.
30 - interrupt-controller: Marks the device as a interrupt controller.
[all …]
Dpinctrl-palmas.txt4 the configuration for Pull UP/DOWN, open drain etc.
7 - compatible: It must be one of following:
8 - "ti,palmas-pinctrl" for Palma series of the pincontrol.
9 - "ti,tps65913-pinctrl" for Palma series device TPS65913.
10 - "ti,tps80036-pinctrl" for Palma series device TPS80036.
12 Please refer to pinctrl-bindings.txt in this directory for details of the
19 those pin(s), and various pin configuration parameters, such as pull-up,
20 open drain.
32 - ti,palmas-enable-dvfs1: Enable DVFS1. Configure pins for DVFS1 mode.
35 - ti,palmas-enable-dvfs2: Enable DVFS2. Configure pins for DVFS2 mode.
[all …]
Dpinctrl-stmfx.txt1 STMicroelectronics Multi-Function eXpander (STMFX) GPIO expander bindings
3 ST Multi-Function eXpander (STMFX) offers up to 24 GPIOs expansion.
7 - compatible: should be "st,stmfx-0300-pinctrl".
8 - #gpio-cells: should be <2>, the first cell is the GPIO number and the second
9 cell is the gpio flags in accordance with <dt-bindings/gpio/gpio.h>.
10 - gpio-controller: marks the device as a GPIO controller.
11 - #interrupt-cells: should be <2>, the first cell is the GPIO number and the
13 <dt-bindings/interrupt-controller/irq.h>.
14 - interrupt-controller: marks the device as an interrupt controller.
15 - gpio-ranges: specifies the mapping between gpio controller and pin
[all …]
Dcirrus,madera-pinctrl.txt3 The Cirrus Logic Madera codecs provide a number of GPIO functions for
5 Certain groups of GPIO pins also have an alternate function, normally as an
19 Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
22 - pinctrl-names : must be "default"
23 - pinctrl-0 : a phandle to the node containing the subnodes containing default
32 - groups : name of one pin group to configure. One of:
42 - function : name of function to assign to this group. One of:
45 io, dsp-gpio, irq1, irq2,
46 fll1-clk, fll1-lock, fll2-clk, fll2-lock, fll3-clk, fll3-lock,
47 fllao-clk, fllao-lock,
[all …]
Dlantiq,pinctrl-xway.txt4 - compatible: "lantiq,pinctrl-xway", (DEPRECATED: Use "lantiq,pinctrl-danube")
5 "lantiq,pinctrl-xr9", (DEPRECATED: Use "lantiq,xrx100-pinctrl" or
6 "lantiq,xrx200-pinctrl")
7 "lantiq,pinctrl-ase", (DEPRECATED: Use "lantiq,ase-pinctrl")
8 "lantiq,<chip>-pinctrl", where <chip> is:
14 - reg: Should contain the physical address and length of the gpio/pinmux
17 Please refer to pinctrl-bindings.txt in this directory for details of the
25 pull-up and open-drain
40 Required subnode-properties:
41 - lantiq,groups : An array of strings. Each string contains the name of a group.
[all …]
Dqcom,pmic-gpio.txt1 Qualcomm PMIC GPIO block
3 This binding describes the GPIO block(s) found in the 8xxx series of
6 - compatible:
10 "qcom,pm8005-gpio"
11 "qcom,pm8018-gpio"
12 "qcom,pm8038-gpio"
13 "qcom,pm8058-gpio"
14 "qcom,pm8916-gpio"
15 "qcom,pm8917-gpio"
16 "qcom,pm8921-gpio"
[all …]
Dpinctrl-mcp23s08.txt2 8-/16-bit I/O expander with serial interface (I2C/SPI)
5 - compatible : Should be
6 - "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,mcp23s18" for 16 GPIO SPI version
14 - "microchip,mcp23008" for 8 GPIO I2C version or
[all …]
Datmel,at91-pio4-pinctrl.txt7 - compatible: "atmel,sama5d2-pinctrl".
8 - reg: base address and length of the PIO controller.
9 - interrupts: interrupt outputs from the controller, one for each bank.
10 - interrupt-controller: mark the device node as an interrupt controller.
11 - #interrupt-cells: should be two.
12 - gpio-controller: mark the device node as a gpio controller.
13 - #gpio-cells: should be two.
15 Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for
16 a general description of GPIO and interrupt bindings.
18 Please refer to pinctrl-bindings.txt in this directory for details of the
[all …]
Dpinctrl-max77620.txt3 Device has 8 GPIO pins which can be configured as GPIO as well as the
6 Please refer file <devicetree/bindings/pinctrl/pinctrl-bindings.txt>
11 --------------------------
14 - pinctrl-names: A pinctrl state named per <pinctrl-bindings.txt>.
15 - pinctrl[0...n]: Properties to contain the phandle for pinctrl states per
16 <pinctrl-bindings.txt>.
19 sub-node have following properties:
22 ------------------
23 - pins: List of pins. Valid values of pins properties are:
27 -------------------
[all …]
/Documentation/devicetree/bindings/gpio/
Dibm,ppc4xx-gpio.txt1 * IBM/AMCC/APM GPIO Controller for PowerPC 4XX series and compatible SoCs
3 All GPIOs are pin-shared with other functions. DCRs control whether a
4 particular pin that has GPIO capabilities acts as a GPIO or is used for
5 another purpose. GPIO outputs are separately programmable to emulate
6 an open-drain driver.
9 - compatible: must be "ibm,ppc4xx-gpio"
10 - reg: address and length of the register set for the device
11 - #gpio-cells: must be set to 2. The first cell is the pin number
12 and the second cell is used to specify the gpio polarity:
15 - gpio-controller: marks the device node as a gpio controller.
[all …]
/Documentation/devicetree/bindings/media/
Dcec-gpio.txt1 * HDMI CEC GPIO driver
3 The HDMI CEC GPIO module supports CEC implementations where the CEC line
4 is hooked up to a pull-up GPIO line and - optionally - the HPD line is
5 hooked up to another GPIO line.
9 when connecting them to a GPIO line.
12 - compatible: value must be "cec-gpio".
13 - cec-gpios: gpio that the CEC line is connected to. The line should be
14 tagged as open drain.
19 - hdmi-phandle - phandle to the HDMI controller, see also cec.txt.
24 - hpd-gpios: gpio that the HPD line is connected to.
[all …]
/Documentation/devicetree/bindings/power/supply/
Dlt3651-charger.txt1 Analog Devices LT3651 Charger Power Supply bindings: lt3651-charger
4 - compatible: Should contain one of the following:
5 * "lltc,ltc3651-charger", (DEPRECATED: Use "lltc,lt3651-charger")
6 * "lltc,lt3651-charger"
7 - lltc,acpr-gpios: Connect to ACPR output. See remark below.
10 - lltc,fault-gpios: Connect to FAULT output. See remark below.
11 - lltc,chrg-gpios: Connect to CHRG output. See remark below.
13 The lt3651 outputs are open-drain type and active low. The driver assumes the
14 GPIO reports "active" when the output is asserted, so if the pins have been
15 connected directly, the GPIO flags should be set to active low also.
[all …]
/Documentation/devicetree/bindings/iio/accel/
Dlis302.txt8 - compatible: should be set to "st,lis3lv02d-spi"
9 - reg: the chipselect index
10 - spi-max-frequency: maximal bus speed, should be set to 1000000 unless
12 - interrupts: the interrupt generated by the device
15 - compatible: should be set to "st,lis3lv02d"
16 - reg: i2c slave address
17 - Vdd-supply: The input supply for Vdd
18 - Vdd_IO-supply: The input supply for Vdd_IO
23 - st,click-single-{x,y,z}: if present, tells the device to issue an
26 - st,click-double-{x,y,z}: if present, tells the device to issue an
[all …]

12