Home
last modified time | relevance | path

Searched +full:up +full:- +full:gpios (Results 1 – 25 of 157) sorted by relevance

1234567

/Documentation/devicetree/bindings/input/
Dgpio-mouse.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/gpio-mouse.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 to 5-7 GPIO lines.
14 - Anshul Dalal <anshulusr@gmail.com>
18 const: gpio-mouse
20 scan-interval-ms:
23 up-gpios:
26 down-gpios:
[all …]
Dgpio-keys.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
15 - gpio-keys
16 - gpio-keys-polled
23 poll-interval: true
26 …"^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switc…
30 gpios:
[all …]
/Documentation/devicetree/bindings/media/cec/
Dcec-gpio.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/media/cec/cec-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hans Verkuil <hverkuil-cisco@xs4all.nl>
14 hooked up to a pull-up GPIO line and - optionally - the HPD line is hooked up
23 const: cec-gpio
25 cec-gpios:
31 hpd-gpios:
37 v5-gpios:
[all …]
/Documentation/devicetree/bindings/net/can/
Dtcan4x5x.txt7 - compatible:
11 - reg: 0
12 - #address-cells: 1
13 - #size-cells: 0
14 - spi-max-frequency: Maximum frequency of the SPI bus the chip can
16 - interrupt-parent: the phandle to the interrupt controller which provides
18 - interrupts: interrupt specification for data-ready.
24 - reset-gpios: Hardwired output GPIO. If not defined then software
26 - device-state-gpios: Input GPIO that indicates if the device is in
29 - device-wake-gpios: Wake up GPIO to wake up the TCAN device. Not
[all …]
/Documentation/devicetree/bindings/display/bridge/
Dps8640.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nicolas Boichat <drinkcat@chromium.org>
13 The PS8640 is a low power MIPI-to-eDP video format converter supporting
14 mobile devices with embedded panel resolutions up to 2048 x 1536. The
15 device accepts a single channel of MIPI DSI v1.1, with up to four lanes
16 plus clock, at a transmission rate up to 1.5Gbit/sec per lane. The
17 device outputs eDP v1.4, one or two lanes, at a link rate of up to
28 powerdown-gpios:
[all …]
Dtoshiba,tc358775.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinay Simha BN <simhavcs@gmail.com>
15 MIPI DSI-RX Data 4-lane, CLK 1-lane with data rates up to 800 Mbps/lane.
17 Up to 1600x1200 24-bit/pixel resolution for single-link LVDS display panel
19 Up to WUXGA (1920x1200 24-bit pixels) resolution for dual-link LVDS display
25 - toshiba,tc358765
26 - toshiba,tc358775
32 vdd-supply:
[all …]
Dite,it6505.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Allen Chen <allen.chen@ite.com.tw>
13 - $ref: /schemas/sound/dai-common.yaml#
16 The IT6505 is a high-performance DisplayPort 1.1a transmitter,
18 The IT6505 supports color depth of up to 36 bits (12 bits/color)
19 and ensures robust transmission of high-quality uncompressed video
23 also encodes and transmits up to 8 channels of I2S digital audio,
24 with sampling rate up to 192kHz and sample size up to 24 bits.
[all …]
/Documentation/devicetree/bindings/phy/
Dphy-mapphone-mdm6600.txt4 - compatible Must be "motorola,mapphone-mdm6600"
5 - enable-gpios GPIO to enable the USB PHY
6 - power-gpios GPIO to power on the device
7 - reset-gpios GPIO to reset the device
8 - motorola,mode-gpios Two GPIOs to configure MDM6600 USB start-up mode for
10 - motorola,cmd-gpios Three GPIOs to control the power state of the MDM6600
11 - motorola,status-gpios Three GPIOs to read the power state of the MDM6600
15 usb-phy {
16 compatible = "motorola,mapphone-mdm6600";
17 enable-gpios = <&gpio3 31 GPIO_ACTIVE_LOW>;
[all …]
/Documentation/devicetree/bindings/gpio/
Dgpio-delay.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/gpio-delay.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alexander Stein <linux@ew.tq-group.com>
16 +----------+ +-----------+
23 | [IOx|-------| |--+-----|-----+ |
26 +----------+ --- C +-----------+
27 ---
29 -
[all …]
Dgpio-consumer-common.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/gpio/gpio-consumer-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartosz Golaszewski <brgl@bgdev.pl>
11 - Linus Walleij <linus.walleij@linaro.org>
14 Pay attention to using proper GPIO flag (e.g. GPIO_ACTIVE_LOW) for the GPIOs
20 enable-gpios:
25 reset-gpios:
27 GPIO (or GPIOs for power sequence) connected to the device reset pin
[all …]
Dgpio.txt4 1) gpios property
5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
9 for compatibility reasons (resolving to the "gpios" property), it is not allowed
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
15 cases should they contain more than one. If your device uses several GPIOs with
17 meaningful name. The only case where an array of GPIOs is accepted is when
18 several GPIOs serve the same function (e.g. a parallel data line).
20 The exact purpose of each gpios property must be documented in the device tree
[all …]
/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#
10 - Wolfram Sang <wsa@kernel.org>
13 - $ref: /schemas/i2c/i2c-controller.yaml#
18 - const: i2c-gpio
20 sda-gpios:
24 from <dt-bindings/gpio/gpio.h> since the signal is by definition
28 scl-gpios:
[all …]
/Documentation/devicetree/bindings/media/i2c/
Disil,isl79987.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Intersil ISL79987 Analog to MIPI CSI-2 decoder
10 - Michael Tretter <m.tretter@pengutronix.de>
11 - Marek Vasut <marex@denx.de>
14 The Intersil ISL79987 is an analog to MIPI CSI-2 decoder which is capable of
15 receiving up to four analog stream and multiplexing them into up to four MIPI
16 CSI-2 virtual channels, using one MIPI clock lane and 1/2 data lanes.
21 - isil,isl79987
[all …]
Dov2659.txt1 * OV2659 1/5-Inch 2Mp SOC Camera
3 The Omnivision OV2659 is a 1/5-inch SOC camera, with an active array size of
9 - compatible: Must be "ovti,ov2659"
10 - reg: I2C slave address
11 - clocks: reference to the xvclk input clock.
12 - clock-names: should be "xvclk".
13 - link-frequencies: target pixel clock frequency.
16 - powerdown-gpios: reference to the GPIO connected to the pwdn pin, if any.
18 - reset-gpios: reference to the GPIO connected to the resetb pin, if any.
19 Active low with internal pull up resistor.
[all …]
/Documentation/devicetree/bindings/iio/adc/
Davia-hx711.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/iio/adc/avia-hx711.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andreas Klinger <ak@it-klinger.de>
13 Bit-banging driver using two GPIOs:
14 - sck-gpio gives a clock to the sensor with 24 cycles for data retrieval
15 and up to 3 cycles for selection of the input channel and gain for the
17 - dout-gpio is the sensor data the sensor responds to the clock
25 - avia,hx711
[all …]
/Documentation/devicetree/bindings/sound/
Dasahi-kasei,ak5558.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/sound/asahi-kasei,ak5558.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: AK5558 8 channel differential 32-bit delta-sigma ADC
10 - Junichi Wakasugi <wakasugi.jb@om.asahi-kasei.co.jp>
11 - Mihai Serban <mihai.serban@nxp.com>
16 - asahi-kasei,ak5552
17 - asahi-kasei,ak5558
22 avdd-supply:
[all …]
Drockchip,rk3288-hdmi-analog.txt4 - compatible: "rockchip,rk3288-hdmi-analog"
5 - rockchip,model: The user-visible name of this sound complex
6 - rockchip,i2s-controller: The phandle of the Rockchip I2S controller that's
8 - rockchip,audio-codec: The phandle of the analog audio codec.
9 - rockchip,routing: A list of the connections between audio components.
16 - rockchip,hp-en-gpios = The phandle of the GPIO that power up/down the
18 - rockchip,hp-det-gpios = The phandle of the GPIO that detects the headphone
20 - pinctrl-names, pinctrl-0: Please refer to pinctrl-bindings.txt
25 compatible = "rockchip,rk3288-hdmi-analog";
27 rockchip,i2s-controller = <&i2s>;
[all …]
/Documentation/driver-api/gpio/
Dboard.rst5 This document explains how GPIOs can be assigned to given devices and functions.
9 Kconfig. Then, how GPIOs are mapped depends on what the platform uses to
14 -----------
15 GPIOs can easily be mapped to devices and functions in the device tree. The
16 exact way to do it depends on the GPIO controller providing the GPIOs, see the
19 GPIOs mappings are defined in the consumer device's node, in a property named
20 <function>-gpios, where <function> is the function the driver will request
26 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
30 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
33 Properties named <function>-gpio are also considered valid and old bindings use
[all …]
/Documentation/devicetree/bindings/w1/
Dw1-gpio.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/w1/w1-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Bitbanged GPIO 1-Wire Bus
10 - Daniel Mack <zonque@gmail.com>
14 const: w1-gpio
16 gpios:
19 - description: Data I/O pin
20 - description: Enable pin for an external pull-up resistor
[all …]
/Documentation/devicetree/bindings/input/touchscreen/
Degalax-ts.txt4 - compatible: must be "eeti,egalax_ts"
5 - reg: i2c slave address
6 - interrupts: touch controller interrupt
7 - wakeup-gpios: the gpio pin to be used for waking up the controller
15 interrupt-parent = <&gpio1>;
17 wakeup-gpios = <&gpio1 9 GPIO_ACTIVE_LOW>;
/Documentation/devicetree/bindings/media/
Dgpio-ir-receiver.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/media/gpio-ir-receiver.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
13 - $ref: rc.yaml#
17 const: gpio-ir-receiver
19 gpios:
22 linux,autosuspend-period:
26 wakeup-source:
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dstarfive,jh7100-pinctrl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/starfive,jh7100-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 Bindings for the JH7100 RISC-V SoC from StarFive Ltd.
15 interesting 2-layered approach to pin muxing best illustrated by the diagram
21 LCD output -----------------| |
22 CMOS Camera interface ------| |--- PAD_GPIO[0]
23 Ethernet PHY interface -----| MUX |--- PAD_GPIO[1]
25 | |--- PAD_GPIO[63]
[all …]
/Documentation/devicetree/bindings/mmc/
Dnvidia,tegra20-sdhci.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mmc/nvidia,tegra20-sdhci.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
18 mmc-controller.yaml and the properties for the Tegra SDHCI controller.
23 - enum:
24 - nvidia,tegra20-sdhci
25 - nvidia,tegra30-sdhci
[all …]
Dmmc-pwrseq-simple.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mmc/mmc-pwrseq-simple.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ulf Hansson <ulf.hansson@linaro.org>
19 const: mmc-pwrseq-simple
21 reset-gpios:
26 contains a list of GPIO specifiers. The reset GPIOs are asserted
27 at initialization and prior we start the power up procedure of the card.
28 They will be de-asserted right after the power has been provided to the
[all …]
/Documentation/devicetree/bindings/mfd/
Dti-lmu.txt6 ------ ---------------------------------
14 - compatible: Should be one of:
20 - reg: I2C slave address.
28 - enable-gpios: A GPIO specifier for hardware enable pin.
29 - ramp-up-us: Current ramping from one brightness level to
31 Range from 2048 us - 117.44 s
32 - ramp-down-us: Current ramping from one brightness level to
34 Range from 2048 us - 117.44 s
35 - ti,brightness-resolution - This determines whether to use 8 bit brightness
47 - backlight: All LMU devices have backlight child nodes.
[all …]

1234567