Home
last modified time | relevance | path

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

12345

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/usb/
Dsmsc,usb3503.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: SMSC USB3503 High-Speed Hub Controller
10 - Dongjin Kim <tobetter@gmail.com>
15 - smsc,usb3503
16 - smsc,usb3503a
17 - smsc,usb3803
22 connect-gpios:
25 GPIO for connect
[all …]
/kernel/linux/linux-5.10/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
17 The driver will attempt to aquire interrupts for all GPIOs to detect changes in
24 charger: battery-charger {
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/
Dusb3503.txt1 SMSC USB3503 High-Speed Hub Controller
4 - compatible: Should be "smsc,usb3503" or "smsc,usb3503a".
7 - reg: Specifies the i2c slave address, it is required and should be 0x08
9 - connect-gpios: Should specify GPIO for connect.
10 - disabled-ports: Should specify the ports unused.
14 - intn-gpios: Should specify GPIO for interrupt.
15 - reset-gpios: Should specify GPIO for reset.
16 - initial-mode: Should specify initial mode.
18 - refclk: Clock used for driving REFCLK signal (optional, if not provided
22 clock-names in order to assign it
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst6 the right in-kernel and userspace APIs/ABIs for the job, and that these
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
25 up to three buttons by simply using GPIOs and no mouse port. You can cut the
26 mouse cable and connect the wires to GPIO lines or solder a mouse connector
29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
[all …]
Dintro.rst10 GPIOs in drivers, and how to write a driver for a device that provides GPIOs
14 ways to obtain and use GPIOs:
16 - The descriptor-based interface is the preferred way to manipulate GPIOs,
18 - The legacy integer-based interface which is considered deprecated (but still
21 The remainder of this document applies to the new descriptor-based interface.
23 integer-based interface.
29 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
34 which GPIOs. Drivers can be written generically, so that board setup code
37 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
38 non-dedicated pin can be configured as a GPIO; and most chips have at least
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/media/
Dcec.rst1 .. SPDX-License-Identifier: GPL-2.0
12 - Exynos4
13 - Exynos5
14 - STIH4xx HDMI CEC
15 - V4L2 adv7511 (same HW, but a different driver from the drm adv7511)
16 - stm32
17 - Allwinner A10 (sun4i)
18 - Raspberry Pi
19 - dw-hdmi (Synopsis IP)
20 - amlogic (meson ao-cec and ao-cec-g12a)
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst6 the right in-kernel and userspace APIs/ABIs for the job, and that these
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
25 up to three buttons by simply using GPIOs and no mouse port. You can cut the
26 mouse cable and connect the wires to GPIO lines or solder a mouse connector
29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
[all …]
Dintro.rst10 GPIOs in drivers, and how to write a driver for a device that provides GPIOs
14 ways to obtain and use GPIOs:
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.
29 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
[all …]
Dlegacy.rst13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
18 which GPIOs. Drivers can be written generically, so that board setup code
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
24 provide GPIOs; multifunction chips like power managers, and audio codecs
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
30 The exact capabilities of GPIOs vary between systems. Common options:
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/microchip/
Dat91-sama5d4ek.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * at91-sama5d4ek.dts - Device Tree file for SAMA5D4 Evaluation Kit
8 /dts-v1/;
12 model = "Atmel SAMA5D4-EK";
16 stdout-path = "serial0:115200n8";
25 clock-frequency = <32768>;
29 clock-frequency = <12000000>;
36 pinctrl-names = "default";
37 pinctrl-0 = <
45 /* The vref depends on JP22 of EK. If connect 1-2 then use 3.3V. connect 2-3 use 3.0V */
[all …]
Dat91-wb50n.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * at91-wb50n.dtsi - Device Tree include file for wb50n cpu module
12 model = "Laird Workgroup Bridge 50N - Atmel SAMA5D";
17 stdout-path = "serial0:115200n8";
38 clock-frequency = <32768>;
42 clock-frequency = <12000000>;
46 atmel,osc-bypass;
50 pinctrl-names = "default";
51 pinctrl-0 = <&pinctrl_mmc0_clk_cmd_dat0 &pinctrl_mmc0_dat1_3 &pinctrl_mmc0_cd>;
52 cd-gpios = <&pioC 26 GPIO_ACTIVE_LOW>;
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dat91-sama5d4ek.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * at91-sama5d4ek.dts - Device Tree file for SAMA5D4 Evaluation Kit
8 /dts-v1/;
12 model = "Atmel SAMA5D4-EK";
16 stdout-path = "serial0:115200n8";
25 clock-frequency = <32768>;
29 clock-frequency = <12000000>;
36 pinctrl-names = "default";
37 pinctrl-0 = <
45 /* The vref depends on JP22 of EK. If connect 1-2 then use 3.3V. connect 2-3 use 3.0V */
[all …]
Ddove-cubox.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
20 compatible = "gpio-leds";
21 pinctrl-0 = <&pmx_gpio_18>;
22 pinctrl-names = "default";
26 gpios = <&gpio0 18 1>;
27 default-state = "keep";
32 compatible = "simple-bus";
33 #address-cells = <1>;
34 #size-cells = <0>;
[all …]
Dat91-wb50n.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * at91-wb50n.dtsi - Device Tree include file for wb50n cpu module
12 model = "Laird Workgroup Bridge 50N - Atmel SAMA5D";
17 stdout-path = "serial0:115200n8";
38 clock-frequency = <32768>;
42 clock-frequency = <12000000>;
46 atmel,osc-bypass;
50 pinctrl-names = "default";
51 pinctrl-0 = <&pinctrl_mmc0_clk_cmd_dat0 &pinctrl_mmc0_dat1_3 &pinctrl_mmc0_cd>;
52 cd-gpios = <&pioC 26 GPIO_ACTIVE_LOW>;
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/
Dtoshiba,tc358767.txt4 - compatible: "toshiba,tc358767"
5 - reg: i2c address of the bridge, 0x68 or 0x0f, depending on bootstrap pins
6 - clock-names: should be "ref"
7 - clocks: OF device-tree clock specification for refclk input. The reference
11 - shutdown-gpios: OF device-tree gpio specification for SD pin
13 - reset-gpios: OF device-tree gpio specification for RSTX pin
15 - toshiba,hpd-pin: TC358767 GPIO pin number to which HPD is connected to (0 or 1)
16 - ports: the ports node can contain video interface port nodes to connect
18 - port@0: DSI input port
19 - port@1: DPI input port
[all …]
Dsii902x.txt4 - compatible: "sil,sii9022"
5 - reg: i2c address of the bridge
8 - interrupts: describe the interrupt line used to inform the host
10 - reset-gpios: OF device-tree gpio specification for RST_N pin.
11 - iovcc-supply: I/O Supply Voltage (1.8V or 3.3V)
12 - cvcc12-supply: Digital Core Supply Voltage (1.2V)
15 - #sound-dai-cells: <0> or <1>. <0> if only i2s or spdif pin
18 - sil,i2s-data-lanes: Array of up to 4 integers with values of 0-3
23 pins (SD0 - SD3). Any i2s pin can be connected to any fifo,
28 - clocks: phandle and clock specifier for each clock listed in
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/marvell/
Ddove-cubox.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
20 compatible = "gpio-leds";
21 pinctrl-0 = <&pmx_gpio_18>;
22 pinctrl-names = "default";
24 led-power {
26 gpios = <&gpio0 18 1>;
27 default-state = "keep";
31 usb_power: regulator-1 {
32 compatible = "regulator-fixed";
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/wireless/
Dmicrochip,wilc1000.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Adham Abozaeid <adham.abozaeid@microchip.com>
11 - Ajay Singh <ajay.kathat@microchip.com>
15 describes the binding to connect wilc devices.
30 clock-names:
33 enable-gpios:
35 description: Used by wilc1000-spi to determine the GPIO line
36 connected to the ENABLE line. If specified, reset-gpios
[all …]
/kernel/linux/linux-6.6/arch/arm64/boot/dts/renesas/
Dsalvator-xs.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree Source for the Salvator-X 2nd version board
5 * Copyright (C) 2015-2017 Renesas Electronics Corp.
8 #include "salvator-common.dtsi"
11 model = "Renesas Salvator-X 2nd version board";
12 compatible = "renesas,salvator-xs";
16 clock-frequency = <16640000>;
20 clock-frequency = <400000>;
22 versaclock6: clock-generator@6a {
25 #clock-cells = <1>;
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/
Dsmsc,lan91c111.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller
10 - Nicolas Pitre <nico@fluxnic.net>
13 - $ref: ethernet-controller.yaml#
25 reg-shift: true
27 reg-io-width:
31 reset-gpios:
35 power-gpios:
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/magnetometer/
Dyamaha,yas530.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 The Yamaha YAS530 magnetometers is a line of 3-axis magnetometers
20 pattern: '^magnetometer@[0-9a-f]+$'
24 - enum:
25 - yamaha,yas530
26 - yamaha,yas532
27 - yamaha,yas533
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/tilcdc/
Dpanel.txt1 Device-Tree bindings for tilcdc DRM generic panel output driver
4 - compatible: value should be "ti,tilcdc,panel".
5 - panel-info: configuration info to configure LCDC correctly for the panel
6 - ac-bias: AC Bias Pin Frequency
7 - ac-bias-intrpt: AC Bias Pin Transitions per Interrupt
8 - dma-burst-sz: DMA burst size
9 - bpp: Bits per pixel
10 - fdd: FIFO DMA Request Delay
11 - sync-edge: Horizontal and Vertical Sync Edge: 0=rising 1=falling
12 - sync-ctrl: Horizontal and Vertical Sync: Control: 0=ignore
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/tilcdc/
Dpanel.txt1 Device-Tree bindings for tilcdc DRM generic panel output driver
4 - compatible: value should be "ti,tilcdc,panel".
5 - panel-info: configuration info to configure LCDC correctly for the panel
6 - ac-bias: AC Bias Pin Frequency
7 - ac-bias-intrpt: AC Bias Pin Transitions per Interrupt
8 - dma-burst-sz: DMA burst size
9 - bpp: Bits per pixel
10 - fdd: FIFO DMA Request Delay
11 - sync-edge: Horizontal and Vertical Sync Edge: 0=rising 1=falling
12 - sync-ctrl: Horizontal and Vertical Sync: Control: 0=ignore
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/dsa/
Dqca8k.txt5 - compatible: should be one of:
9 - #size-cells: must be 0
10 - #address-cells: must be 1
14 - reset-gpios: GPIO to be used to reset the whole device
19 described in dsa/dsa.txt. If the QCA8K switch is connect to a SoC's external
20 mdio-bus each subnode describing a port needs to have a valid phandle
24 Don't use mixed external and internal mdio-bus configurations, as this is
31 - fixed-link : Fixed-link subnode describing a link to a non-MDIO
33 Documentation/devicetree/bindings/net/fixed-link.txt
36 For QCA8K the 'fixed-link' sub-node supports only the following properties:
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/renesas/
Dr8a77951-salvator-xs.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree Source for the Salvator-X 2nd version board with R-Car H3 ES2.0+
5 * Copyright (C) 2015-2017 Renesas Electronics Corp.
8 /dts-v1/;
10 #include "salvator-xs.dtsi"
13 model = "Renesas Salvator-X 2nd version board based on r8a77951";
14 compatible = "renesas,salvator-xs", "renesas,r8a7795";
47 clock-names = "du.0", "du.1", "du.2", "du.3",
67 remote-endpoint = <&hdmi0_con>;
73 remote-endpoint = <&rsnd_endpoint1>;
[all …]

12345