| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/ |
| D | phy-mapphone-mdm6600.txt | 4 - 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | phy-mapphone-mdm6600.txt | 4 - 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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | board.rst | 5 This document explains how GPIOs can be assigned to given devices and functions.
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
15 Kconfig. Then, how GPIOs are mapped depends on what the platform uses to
20 -----------
21 GPIOs can easily be mapped to devices and functions in the device tree. The
22 exact way to do it depends on the GPIO controller providing the GPIOs, see the
25 GPIOs mappings are defined in the consumer device's node, in a property named
26 <function>-gpios, where <function> is the function the driver will request
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | board.rst | 5 This document explains how GPIOs can be assigned to given devices and functions.
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
15 Kconfig. Then, how GPIOs are mapped depends on what the platform uses to
20 -----------
21 GPIOs can easily be mapped to devices and functions in the device tree. The
22 exact way to do it depends on the GPIO controller providing the GPIOs, see the
25 GPIOs mappings are defined in the consumer device's node, in a property named
26 <function>-gpios, where <function> is the function the driver will request
32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/broadcom/ |
| D | bcm4709-buffalo-wxr-1900dhp.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
4 * DTS for Buffalo WXR-1900DHP
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
15 compatible = "buffalo,wxr-1900dhp", "brcm,bcm4709", "brcm,bcm4708";
16 model = "Buffalo WXR-1900DHP";
29 compatible = "gpio-leds";
31 led-usb {
33 gpios = <&chipcommon 4 GPIO_ACTIVE_HIGH>;
36 led-power-amber {
[all …]
|
| D | bcm4709-netgear-r7000.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
29 compatible = "gpio-leds";
31 led-power-white {
32 label = "bcm53xx:white:power";
33 gpios = <&chipcommon 2 GPIO_ACTIVE_LOW>;
34 linux,default-trigger = "default-on";
37 led-power-amber {
38 label = "bcm53xx:amber:power";
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | bcm4709-buffalo-wxr-1900dhp.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
4 * DTS for Buffalo WXR-1900DHP
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
15 compatible = "buffalo,wxr-1900dhp", "brcm,bcm4709", "brcm,bcm4708";
16 model = "Buffalo WXR-1900DHP";
29 compatible = "gpio-leds";
33 gpios = <&chipcommon 4 GPIO_ACTIVE_HIGH>;
36 power-amber {
37 label = "bcm53xx:amber:power";
[all …]
|
| D | kirkwood-linkstation-6282.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Device Tree common file for kirkwood-6282 based Buffalo Linkstation
10 #include "kirkwood-6282.dtsi"
11 #include "kirkwood-linkstation.dtsi"
15 pinctrl: pin-controller@10000 {
16 pmx_power_hdd0: pmx-power-hdd0 {
20 pmx_usb_vbus: pmx-usb-vbus {
24 pmx_fan_high: pmx-fan-high {
28 pmx_fan_low: pmx-fan-low {
32 pmx_led_alarm: pmx-led-alarm {
[all …]
|
| D | kirkwood-linkstation-duo-6281.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Device Tree common file for kirkwood-6281 based 2-Bay Buffalo Linkstation
10 #include "kirkwood-6281.dtsi"
11 #include "kirkwood-linkstation.dtsi"
15 pinctrl: pin-controller@10000 {
16 pmx_power_hdd0: pmx-power-hdd0 {
20 pmx_power_hdd1: pmx-power-hdd1 {
24 pmx_usb_vbus: pmx-usb-vbus {
28 pmx_led_alarm: pmx-led-alarm {
32 pmx_led_function_red: pmx-led-function-red {
[all …]
|
| D | kirkwood-lsxl.dtsi | 1 // SPDX-License-Identifier: GPL-2.0
3 #include "kirkwood-6281.dtsi"
8 stdout-path = &uart0;
12 pinctrl: pin-controller@10000 {
13 /* Non-default UART pins */
14 pmx_uart0: pmx-uart0 {
18 pmx_power_hdd: pmx-power-hdd {
22 pmx_usb_vbus: pmx-usb-vbus {
26 pmx_fan_high: pmx-fan-high {
30 pmx_fan_low: pmx-fan-low {
[all …]
|
| D | bcm4709-netgear-r7000.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
29 compatible = "gpio-leds";
31 power-white {
32 label = "bcm53xx:white:power";
33 gpios = <&chipcommon 2 GPIO_ACTIVE_LOW>;
34 linux,default-trigger = "default-on";
37 power-amber {
38 label = "bcm53xx:amber:power";
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/gpio/ |
| D | gpio-consumer-common.yaml | 1 # 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/supply/ |
| D | maxim,max8903.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/supply/maxim,max8903.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
13 - $ref: power-supply.yaml#
19 dok-gpios:
21 description: Valid DC power has been detected (active low, input)
23 uok-gpios:
25 description: Valid USB power has been detected (active low, input)
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | samsung,s5m8767.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung S5M8767 Power Management IC
10 - Krzysztof Kozlowski <krzk@kernel.org>
13 This is a part of device tree bindings for S2M and S5M family of Power
16 The Samsung S5M8767 is a Power Management IC which includes voltage
17 and current regulators, RTC, clock outputs and other sub-blocks.
21 const: samsung,s5m8767-pmic
39 s5m8767,pmic-buck2-dvs-voltage:
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/marvell/ |
| D | kirkwood-linkstation-6282.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Device Tree common file for kirkwood-6282 based Buffalo Linkstation
10 #include "kirkwood-6282.dtsi"
11 #include "kirkwood-linkstation.dtsi"
15 pinctrl: pin-controller@10000 {
16 pmx_power_hdd0: pmx-power-hdd0 {
20 pmx_usb_vbus: pmx-usb-vbus {
24 pmx_fan_high: pmx-fan-high {
28 pmx_fan_low: pmx-fan-low {
32 pmx_led_alarm: pmx-led-alarm {
[all …]
|
| D | kirkwood-linkstation-duo-6281.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Device Tree common file for kirkwood-6281 based 2-Bay Buffalo Linkstation
10 #include "kirkwood-6281.dtsi"
11 #include "kirkwood-linkstation.dtsi"
15 pinctrl: pin-controller@10000 {
16 pmx_power_hdd0: pmx-power-hdd0 {
20 pmx_power_hdd1: pmx-power-hdd1 {
24 pmx_usb_vbus: pmx-usb-vbus {
28 pmx_led_alarm: pmx-led-alarm {
32 pmx_led_function_red: pmx-led-function-red {
[all …]
|
| D | kirkwood-lsxl.dtsi | 1 // SPDX-License-Identifier: GPL-2.0
3 #include "kirkwood-6281.dtsi"
8 stdout-path = &uart0;
12 pinctrl: pin-controller@10000 {
13 /* Non-default UART pins */
14 pmx_uart0: pmx-uart0 {
18 pmx_power_hdd: pmx-power-hdd {
22 pmx_usb_vbus: pmx-usb-vbus {
26 pmx_fan_high: pmx-fan-high {
30 pmx_fan_low: pmx-fan-low {
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/panel/ |
| D | panel-ronbo-rb070d30.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright (C) 2018-2019, Bridge Systems BV
4 * Copyright (C) 2018-2019, Bootlin
7 * This file based on panel-ilitek-ili9881c.c
16 #include <linux/media-bus-format.h>
33 struct gpio_desc *power; member
37 } gpios; member
50 ret = regulator_enable(ctx->supply); in rb070d30_panel_prepare()
52 dev_err(&ctx->dsi->dev, "Failed to enable supply: %d\n", ret); in rb070d30_panel_prepare()
57 gpiod_set_value(ctx->gpios.power, 1); in rb070d30_panel_prepare()
[all …]
|
| /kernel/linux/linux-6.6/arch/mips/boot/dts/ralink/ |
| D | gardena_smart_gateway_mt7688.dts | 1 // SPDX-License-Identifier: GPL-2.0
6 /dts-v1/;
10 #include <dt-bindings/gpio/gpio.h>
11 #include <dt-bindings/input/input.h>
14 compatible = "gardena,smart-gateway-mt7688", "ralink,mt7688a-soc",
15 "ralink,mt7628a-soc";
23 gpio-keys {
24 compatible = "gpio-keys";
26 pinctrl-names = "default";
27 pinctrl-0 = <&pinmux_gpio_gpio>; /* GPIO11 */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/panel/ |
| D | ronbo,rb070d30.yaml | 1 # SPDX-License-Identifier: (GPL-2.0+ OR X11)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Maxime Ripard <mripard@kernel.org>
17 description: MIPI-DSI virtual channel
19 power-gpios:
20 description: GPIO used for the power pin
23 reset-gpios:
27 shlr-gpios:
31 updn-gpios:
[all …]
|
| D | jdi,lt070me05000.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinay Simha BN <simhavcs@gmail.com>
13 - $ref: panel-common.yaml#
19 enable-gpios: true
21 reset-gpios: true
23 vddp-supply:
25 The regulator that provides the supply voltage Power IC supply (3-5V)
27 iovcc-supply:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/panel/ |
| D | ronbo,rb070d30.yaml | 1 # SPDX-License-Identifier: (GPL-2.0+ OR X11)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Maxime Ripard <mripard@kernel.org>
17 description: MIPI-DSI virtual channel
19 power-gpios:
20 description: GPIO used for the power pin
23 reset-gpios:
27 shlr-gpios:
31 updn-gpios:
[all …]
|
| D | jdi,lt070me05000.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinay Simha BN <simhavcs@gmail.com>
13 - $ref: panel-common.yaml#
19 enable-gpios: true
21 reset-gpios: true
23 vddp-supply:
25 The regulator that provides the supply voltage Power IC supply (3-5V)
27 iovcc-supply:
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/panel/ |
| D | panel-ronbo-rb070d30.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright (C) 2018-2019, Bridge Systems BV
4 * Copyright (C) 2018-2019, Bootlin
7 * This file based on panel-ilitek-ili9881c.c
15 #include <linux/media-bus-format.h>
33 struct gpio_desc *power; member
37 } gpios; member
50 ret = regulator_enable(ctx->supply); in rb070d30_panel_prepare()
52 dev_err(&ctx->dsi->dev, "Failed to enable supply: %d\n", ret); in rb070d30_panel_prepare()
57 gpiod_set_value(ctx->gpios.power, 1); in rb070d30_panel_prepare()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | sff,sfp.txt | 1 Small Form Factor (SFF) Committee Small Form-factor Pluggable (SFP)
6 - compatible : must be one of
10 - i2c-bus : phandle of an I2C bus controller for the SFP two wire serial
15 - mod-def0-gpios : GPIO phandle and a specifier of the MOD-DEF0 (AKA Mod_ABS)
19 - los-gpios : GPIO phandle and a specifier of the Receiver Loss of Signal
22 - tx-fault-gpios : GPIO phandle and a specifier of the Module Transmitter
25 - tx-disable-gpios : GPIO phandle and a specifier of the Transmitter Disable
28 - rate-select0-gpios : GPIO phandle and a specifier of the Rx Signaling Rate
32 - rate-select1-gpios : GPIO phandle and a specifier of the Tx Signaling Rate
36 - maximum-power-milliwatt : Maximum module power consumption
[all …]
|