Home
last modified time | relevance | path

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

12345678910>>...43

/openbmc/skeleton/libopenbmc_intf/
H A Dgpio_configs.c9 * http://www.apache.org/licenses/LICENSE-2.0
29 * Loads the GPIO information into the gpios->power_gpio structure
32 * @param gpios - the structure where GpioConfigs.power_gpio will
34 * @param gpio_configs - cJSON pointer to the GPIO JSON
36 void read_power_gpios(GpioConfigs* gpios, const cJSON* gpio_configs) in read_power_gpios() argument
44 /* PGOOD - required */ in read_power_gpios()
49 gpios->power_gpio.power_good_in.name = g_strdup(pgood->valuestring); in read_power_gpios()
51 g_print("Power GPIO power good input: %s\n", in read_power_gpios()
52 gpios->power_gpio.power_good_in.name); in read_power_gpios()
54 /* Latch out - optional */ in read_power_gpios()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/phy/
H A 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 …]
/openbmc/linux/Documentation/driver-api/gpio/
H A Dboard.rst5 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 …]
/openbmc/linux/arch/arm/boot/dts/broadcom/
H A Dbcm4709-buffalo-wxr-1900dhp.dts1 // 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 …]
H A Dbcm4709-netgear-r7000.dts1 // 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 …]
H A Dbcm4708-smartrg-sr400ac.dts1 // 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 1 GPIO_ACTIVE_HIGH>;
34 linux,default-trigger = "default-on";
37 led-power-amber {
38 label = "bcm53xx:amber:power";
[all …]
/openbmc/linux/Documentation/devicetree/bindings/gpio/
H A 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 …]
/openbmc/docs/designs/
H A Ddevice-tree-gpio-naming.md12 subsystem. The replacement is a "descriptor-based" character device interface.
17 libgpiod provides a feature where you can access gpios by a name given to them
25 specific field used to name the GPIOs in the DTS is `gpio-line-names`. This
26 [patch][3] shows an example of naming the GPIOs for a system.
28 GPIOs are used for arbitrary things. It's pretty hard to have a coherent naming
29 scheme in the face of a universe of potential use-cases.
37 - Ensure common function GPIOs within OpenBMC use the same naming convention
44 for all common GPIOs.
46 This list below includes all common GPIOs within OpenBMC. Any OpenBMC system
47 which provides one of the below GPIOs must name it as listed in this document.
[all …]
/openbmc/linux/Documentation/devicetree/bindings/power/supply/
H A Dmaxim,max8903.yaml1 # 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 …]
/openbmc/linux/Documentation/devicetree/bindings/mfd/
H A Dsamsung,s5m8767.yaml1 # 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 …]
/openbmc/linux/arch/arm/boot/dts/marvell/
H A Dkirkwood-linkstation-6282.dtsi1 // 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 …]
H A Dkirkwood-linkstation-duo-6281.dtsi1 // 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 …]
H A Dkirkwood-lsxl.dtsi1 // 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 …]
H A Dkirkwood-iconnect.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
5 #include "kirkwood-6281.dtsi"
9 compatible = "iom,iconnect-1.1", "iom,iconnect", "marvell,kirkwood-88f6281", "marvell,kirkwood";
18 stdout-path = &uart0;
19 linux,initrd-start = <0x4500040>;
20 linux,initrd-end = <0x4800000>;
24 pinctrl: pin-controller@10000 {
25 pmx_button_reset: pmx-button-reset {
29 pmx_button_otb: pmx-button-otb {
[all …]
H A Dorion5x-linkstation-lschl.dts2 * Device Tree file for Buffalo Linkstation LS-CHLv3
5 * Copyright (C) 2015-2017
8 * This file is dual-licensed: you can use it either under the terms
47 /dts-v1/;
49 #include "orion5x-linkstation.dtsi"
50 #include "mvebu-linkstation-gpio-simple.dtsi"
51 #include "mvebu-linkstation-fan.dtsi"
52 #include <dt-bindings/gpio/gpio.h>
55 model = "Buffalo Linkstation LiveV3 (LS-CHL)";
56 compatible = "buffalo,lschl", "marvell,orion5x-88f5182", "marvell,orion5x";
[all …]
/openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-sequencing/
H A Dpower-sequencing.bb1 inherit obmc-phosphor-systemd
2 SUMMARY = "Power Sequencing for HPE RL300 Gen11"
4 SYSTEMD_SERVICE:${PN} = "monitor-ipmi-power-transition.service power-sequencing.service gpiosdown.s…
5 …-ipmi-power-transition.service file://ipmi-power-button-monitoring.sh file://rl300Start.sh file://…
7 LICENSE = "Apache-2.0"
8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
11 IMAGE_INSTALL += "power-sequencing "
13 FILES:${PN} = "/usr/share/gpios/* /usr/bin/* /etc/system/*"
16 install -d ${D}${sysconfdir}/system/
17 install -d ${D}/usr/share/gpios
[all …]
/openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-sequencing/
H A Dpower-sequencing.bb1 inherit obmc-phosphor-systemd
2 SUMMARY = "Power Sequencing for HPE DL360 Gen11"
4 SYSTEMD_SERVICE:${PN} = "monitor-ipmi-power-transition.service power-sequencing.service gpiosdown.s…
5 …-ipmi-power-transition.service file://ipmi-power-button-monitoring.sh file://dl360Start.sh file://…
7 LICENSE = "Apache-2.0"
8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
11 IMAGE_INSTALL += "power-sequencing "
13 FILES:${PN} = "/usr/share/gpios/* /usr/bin/* /etc/system/*"
16 install -d ${D}${sysconfdir}/system/
17 install -d ${D}/usr/share/gpios
[all …]
/openbmc/linux/arch/mips/boot/dts/ralink/
H A Dgardena_smart_gateway_mt7688.dts1 // 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 …]
/openbmc/linux/Documentation/devicetree/bindings/display/panel/
H A Dronbo,rb070d30.yaml1 # 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 …]
H A Djdi,lt070me05000.yaml1 # 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 …]
/openbmc/linux/drivers/gpu/drm/panel/
H A Dpanel-ronbo-rb070d30.c1 // 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 …]
/openbmc/u-boot/arch/arm/dts/
H A Dkirkwood-lsxl.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 #include "kirkwood-6281.dtsi"
8 stdout-path = &uart0;
16 pinctrl: pin-controller@10000 {
17 pmx_power_hdd: pmx-power-hdd {
21 pmx_usb_vbus: pmx-usb-vbus {
25 pmx_fan_high: pmx-fan-high {
29 pmx_fan_low: pmx-fan-low {
33 pmx_led_function_blue: pmx-led-function-blue {
37 pmx_led_alarm: pmx-led-alarm {
[all …]
H A Dkirkwood-iconnect.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
5 #include "kirkwood-6281.dtsi"
9 compatible = "iom,iconnect-1.1", "iom,iconnect", "marvell,kirkwood-88f6281", "marvell,kirkwood";
18 stdout-path = &uart0;
19 linux,initrd-start = <0x4500040>;
20 linux,initrd-end = <0x4800000>;
24 pinctrl: pin-controller@10000 {
25 pmx_button_reset: pmx-button-reset {
29 pmx_button_otb: pmx-button-otb {
[all …]
/openbmc/linux/Documentation/devicetree/bindings/mmc/
H A 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#
7 title: Simple MMC power sequence provider
10 - Ulf Hansson <ulf.hansson@linaro.org>
13 The purpose of the simple MMC power sequence provider is to supports a set
19 const: mmc-pwrseq-simple
21 reset-gpios:
26 contains a list of GPIO specifiers. The reset GPIOs are asserted
[all …]
/openbmc/linux/Documentation/devicetree/bindings/net/
H A Dsff,sfp.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Small Form Factor (SFF) Committee Small Form-factor Pluggable (SFP)
11 - Russell King <linux@armlinux.org.uk>
16 - sff,sfp # for SFP modules
17 - sff,sff # for soldered down SFF modules
19 i2c-bus:
24 maximum-power-milliwatt:
28 Maximum module power consumption Specifies the maximum power consumption
[all …]

12345678910>>...43