/openbmc/linux/Documentation/devicetree/bindings/leds/ |
H A D | leds-bcm6358.txt | 5 which can either be controlled by software (exporting the 74x164 as spi-gpio. 10 - compatible : should be "brcm,bcm6358-leds". 11 - #address-cells : must be 1. 12 - #size-cells : must be 0. 13 - reg : BCM6358 LED controller address and size. 16 - brcm,clk-div : SCK signal divider. Possible values are 1, 2, 4 and 8. 18 - brcm,clk-dat-low : Boolean, makes clock and data signals active low. 21 Each LED is represented as a sub-node of the brcm,bcm6358-leds device. 23 LED sub-node required properties: 24 - reg : LED pin number (only LEDs 0 to 31 are valid). [all …]
|
H A D | leds-bcm6328.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Álvaro Fernández Rojas <noltari@gmail.com> 17 as spi-gpio. See 21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware 29 explained later in brcm,link-signal-sources). Even if a LED is hardware 34 Each LED is represented as a sub-node of the brcm,bcm6328-leds device. 38 const: brcm,bcm6328-leds [all …]
|
/openbmc/u-boot/doc/device-tree-bindings/leds/ |
H A D | leds-bcm6358.txt | 5 which can either be controlled by software (exporting the 74x164 as spi-gpio. 6 See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or 10 - compatible : should be "brcm,bcm6358-leds". 11 - #address-cells : must be 1. 12 - #size-cells : must be 0. 13 - reg : BCM6358 LED controller address and size. 16 - brcm,clk-div : SCK signal divider. Possible values are 1, 2, 4 and 8. 18 - brcm,clk-dat-low : Boolean, makes clock and data signals active low. 21 Each LED is represented as a sub-node of the brcm,bcm6358-leds device. 23 LED sub-node required properties: [all …]
|
H A D | leds-bcm6328.txt | 7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or 10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware 14 - compatible : should be "brcm,bcm6328-leds". 15 - #address-cells : must be 1. 16 - #size-cells : must be 0. 17 - reg : BCM6328 LED controller address and size. 20 - brcm,serial-leds : Boolean, enables Serial LEDs. 22 - brcm,serial-mux : Boolean, enables Serial LEDs multiplexing. 24 - brcm,serial-clk-low : Boolean, makes clock signal active low. 26 - brcm,serial-dat-low : Boolean, makes data signal active low. [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/power/supply/ |
H A 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 …]
|
/openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
H A D | panel-common.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/display/panel/panel-common.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Thierry Reding <thierry.reding@gmail.com> 11 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> 24 width-mm: 29 height-mm: 43 non-descriptive information. For instance an LCD panel in a system that 55 panel-timing: [all …]
|
/openbmc/u-boot/arch/mips/dts/ |
H A D | netgear,dgnd3700v2.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 6 /dts-v1/; 19 stdout-path = "serial0:115200n8"; 22 gpio-leds { 23 compatible = "gpio-leds"; 36 label = "DGND3700v2:red:power"; 50 compatible = "brcm,enetsw-port"; 53 brcm,phy-id = <0xff>; 55 full-duplex; 56 bypass-link; [all …]
|
H A D | netgear,cg3100d.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 6 /dts-v1/; 19 stdout-path = "serial0:115200n8"; 22 gpio-leds { 23 compatible = "gpio-leds"; 36 label = "CG3100D:red:power"; 47 active-low; 48 label = "CG3100D:green:power"; 53 active-low; 59 active-low; [all …]
|
H A D | comtrend,ar-5315u.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 6 /dts-v1/; 11 model = "Comtrend AR-5315u"; 12 compatible = "comtrend,ar5315-un", "brcm,bcm6318"; 19 stdout-path = "serial0:115200n8"; 31 compatible = "brcm,enetsw-port"; 34 brcm,phy-id = <1>; 38 compatible = "brcm,enetsw-port"; 41 brcm,phy-id = <2>; 45 compatible = "brcm,enetsw-port"; [all …]
|
H A D | comtrend,vr-3032u.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 6 /dts-v1/; 11 model = "Comtrend VR-3032u"; 12 compatible = "comtrend,vr-3032u", "brcm,bcm63268"; 19 stdout-path = "serial0:115200n8"; 31 compatible = "brcm,enetsw-port"; 34 brcm,phy-id = <1>; 38 compatible = "brcm,enetsw-port"; 41 brcm,phy-id = <2>; 45 compatible = "brcm,enetsw-port"; [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/usb/ |
H A D | fsl,imx8mp-dwc3.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/usb/fsl,imx8mp-dwc3.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Li Jun <jun.li@nxp.com> 15 const: fsl,imx8mp-dwc3 19 - description: Address and length of the register set for HSIO Block Control 20 - description: Address and length of the register set for the wrapper of dwc3 core on the SOC. 22 "#address-cells": 25 "#size-cells": [all …]
|
H A D | pxa-usb.txt | 6 - compatible: Should be "marvell,pxa-ohci" for USB controllers 10 - "marvell,enable-port1", "marvell,enable-port2", "marvell,enable-port3" 12 - "marvell,port-mode" selects the mode of the ports: 16 - "marvell,power-sense-low" - power sense pin is low-active. 17 - "marvell,power-control-low" - power control pin is low-active. 18 - "marvell,no-oc-protection" - disable over-current protection. 19 - "marvell,oc-mode-perport" - enable per-port over-current protection. 20 - "marvell,power_on_delay" Power On to Power Good time - in ms. 25 compatible = "marvell,pxa-ohci"; 28 marvell,enable-port1; [all …]
|
/openbmc/linux/drivers/gpu/drm/panfrost/ |
H A D | panfrost_regs.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 6 * (C) COPYRIGHT 2010-2018 ARM Limited. All rights reserved. 54 #define GPU_PWR_KEY 0x50 /* (WO) Power manager key register */ 56 #define GPU_PWR_OVERRIDE0 0x54 /* (RW) Power manager override settings */ 57 #define GPU_PWR_OVERRIDE1 0x58 /* (RW) Power manager override settings */ 87 #define GPU_SHADER_PRESENT_LO 0x100 /* (RO) Shader core present bitmap, low word */ 89 #define GPU_TILER_PRESENT_LO 0x110 /* (RO) Tiler core present bitmap, low word */ 92 #define GPU_L2_PRESENT_LO 0x120 /* (RO) Level 2 cache present bitmap, low word */ 99 #define GPU_STACK_PRESENT_LO 0xE00 /* (RO) Core stack present bitmap, low word */ 102 #define SHADER_READY_LO 0x140 /* (RO) Shader core ready bitmap, low word */ [all …]
|
/openbmc/u-boot/drivers/video/ |
H A D | am335x-fb.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */ 3 * Copyright (C) 2013-2018 Hannes Schmelzer <oe5hpm@oevsv.at> - 4 * B&R Industrial Automation GmbH - http://www.br-automation.com 29 * 0 = DE is low-active 30 * 1 = DE is high-active 33 * 0 = pix-clk is high-active 34 * 1 = pic-clk is low-active 37 * 0 = HSYNC is active high 38 * 1 = HSYNC is avtive low 41 * 0 = VSYNC is active high [all …]
|
/openbmc/linux/Documentation/driver-api/gpio/ |
H A D | intro.rst | 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 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 40 provide GPIOs; multifunction chips like power managers, and audio codecs 43 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS 48 - Output values are writable (high=1, low=0). Some chips also have [all …]
|
H A D | board.rst | 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 20 ----------- 26 <function>-gpios, where <function> is the function the driver will request 32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */ 36 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>; 39 Properties named <function>-gpio are also considered valid and old bindings use 44 "led" function, and GPIO 1 as the "power" GPIO:: 46 struct gpio_desc *red, *green, *blue, *power; 52 power = gpiod_get(dev, "power", GPIOD_OUT_HIGH); [all …]
|
/openbmc/linux/drivers/regulator/ |
H A D | mcp16502.c | 1 // SPDX-License-Identifier: GPL-2.0 9 // Inspired from tps65086-regulator.c 29 * The PMIC has four sets of registers corresponding to four power modes: 30 * Performance, Active, Low-power, Hibernate. 33 * Each regulator has a register for each power mode. To access a register 41 * a low-power state while the PMIC is in Active mode. They are supposed to be 42 * configured at startup and then simply transition to/from a global low-power 43 * state by setting the GPIO lpm pin high/low. 45 * This driver keeps the PMIC in Active mode, Low-power state is set for the 48 * The PMIC's Low-power and Hibernate modes are used during standby/suspend. [all …]
|
/openbmc/linux/Documentation/admin-guide/pm/ |
H A D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0 5 Power Management Strategies 13 The Linux kernel supports two major high-level power management strategies. 15 One of them is based on using global low-power states of the whole system in 17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The 23 :doc:`system-wide power management <system-wide>`. 25 The other strategy, referred to as the :doc:`working-state power management 26 <working-state>`, is based on adjusting the power states of individual hardware 30 a metastate covering a range of different power states of the system in which 31 the individual components of it can be either ``active`` (in use) or [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | sff,sfp.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: 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 …]
|
/openbmc/linux/include/soc/at91/ |
H A D | at91sam9_ddrsdr.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */ 46 #define AT91_DDRSDRC_OCD (1 << 12) /* Off-Chip Driver [SAM9 Only] */ 48 #define AT91_DDRSDRC_ACTBST (1 << 18) /* Active Bank X to Burst Stop Read Access Bank Y [SAM9 Onl… 51 #define AT91_DDRSDRC_TRAS (0xf << 0) /* Active to Precharge delay */ 56 #define AT91_DDRSDRC_TRRD (0xf << 20) /* Active BankA to BankB */ 59 #define AT91_DDRSDRC_TMRD (0xf << 28) /* Load mode to active/refresh delay */ 63 #define AT91_DDRSDRC_TXSNR (0xff << 8) /* Exit self-refresh to non-read */ 64 #define AT91_DDRSDRC_TXSRD (0xff << 16) /* Exit self-refresh to read */ 65 #define AT91_DDRSDRC_TXP (0xf << 24) /* Exit power-down delay */ 68 #define AT91_DDRSDRC_TXARD (0xf << 0) /* Exit active power down delay to read command in mode "F… [all …]
|
/openbmc/linux/arch/arm/boot/dts/marvell/ |
H A D | dove-sbc-a510.dts | 2 * Device Tree file for Compulab SBC-A510 Single Board Computer 6 * This file is dual-licensed: you can use it either under the terms 46 * SBC-A510 comprises a PCA9555 I2C GPIO expander its GPIO lines connected to 48 * 0.0 USB0 VBUS_EN (active high) 51 * 0.3 DVI transmitter TI TFP410 PD# (active low power down) 52 * 0.4 LVDS transmitter DS90C365 PD# (active low power down) 53 * 0.5 LCD nRST (active low reset) 54 * 0.6 PCIe0 nRST (active low reset) 55 * 0.7 mini-PCIe slot W_DISABLE# 60 * 1.3 MMC VCC_EN (active high) and P21.7 [all …]
|
/openbmc/docs/designs/ |
H A D | device-tree-gpio-naming.md | 12 subsystem. The replacement is a "descriptor-based" character device interface. 25 specific field used to name the GPIOs in the DTS is `gpio-line-names`. This 29 scheme in the face of a universe of potential use-cases. 37 - Ensure common function GPIOs within OpenBMC use the same naming convention 52 Pattern: `*-button` 55 BMC-less machines use a button to trigger system behavior and in a BMC-managed 59 #### power-button 64 depends on the index of Host and the active state is high or low. 68 - `host*-ready`: Host ready, active high 69 - `host*-ready-n`: Host ready, active low [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/mfd/ |
H A D | max77620.txt | 1 MAX77620 Power management IC from Maxim Semiconductor. 4 ------------------- 5 - compatible: Must be one of 9 - reg: I2C device address. 12 ------------------- 13 - interrupts: The interrupt on the parent the controller is 15 - interrupt-controller: Marks the device node as an interrupt controller. 16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells 17 variant of <../interrupt-controller/interrupts.txt> 19 are defined at dt-bindings/mfd/max77620.h. [all …]
|
/openbmc/linux/arch/mips/boot/dts/brcm/ |
H A D | bcm63268-comtrend-vr-3032u.dts | 1 // SPDX-License-Identifier: GPL-2.0 2 /dts-v1/; 7 compatible = "comtrend,vr-3032u", "brcm,bcm63268"; 8 model = "Comtrend VR-3032u"; 17 stdout-path = &uart0; 23 brcm,serial-leds; 24 brcm,serial-dat-low; 25 brcm,serial-shift-inv; 29 brcm,hardware-controlled; 30 brcm,link-signal-sources = <0>; [all …]
|
/openbmc/linux/Documentation/driver-api/pm/ |
H A D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 Device Power Management Basics 10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc. 17 Most of the code in Linux is device drivers, so most of the Linux power 18 management (PM) code is also driver-specific. Most drivers will do very 22 This writeup gives an overview of how drivers interact with system-wide 23 power management goals, emphasizing the models and interfaces that are 25 background for the domain-specific work you'd do with any specific driver. 28 Two Models for Device Power Management 31 Drivers will use one or both of these models to put devices into low-power [all …]
|