Searched +full:regulator +full:- +full:pull +full:- +full:down (Results 1 – 12 of 12) sorted by relevance
| /Documentation/devicetree/bindings/regulator/ |
| D | tps62360-regulator.txt | 4 - compatible: Must be one of the following. 9 - reg: I2C slave address 12 - ti,enable-vout-discharge: Enable output discharge. This is boolean value. 13 - ti,enable-pull-down: Enable pull down. This is boolean value. 14 - ti,vsel0-gpio: GPIO for controlling VSEL0 line. 17 - ti,vsel1-gpio: Gpio for controlling VSEL1 line. 20 - ti,vsel0-state-high: Initial state of vsel0 input is high. 22 - ti,vsel1-state-high: Initial state of vsel1 input is high. 25 Any property defined as part of the core regulator binding, defined in 26 regulator.txt, can also be used. [all …]
|
| D | st,stpmic1-regulator.txt | 3 Regulator Nodes are optional depending on needs. 6 - buck1 for Buck BUCK1 7 - buck2 for Buck BUCK2 8 - buck3 for Buck BUCK3 9 - buck4 for Buck BUCK4 10 - ldo1 for LDO LDO1 11 - ldo2 for LDO LDO2 12 - ldo3 for LDO LDO3 13 - ldo4 for LDO LDO4 14 - ldo5 for LDO LDO5 [all …]
|
| D | regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/regulator/regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Liam Girdwood <lgirdwood@gmail.com> 11 - Mark Brown <broonie@kernel.org> 14 regulator-name: 15 description: A string used as a descriptive name for regulator outputs 18 regulator-min-microvolt: 21 regulator-max-microvolt: [all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qcom-rpm.txt | 8 - compatible: 12 "qcom,rpm-apq8064" 13 "qcom,rpm-msm8660" 14 "qcom,rpm-msm8960" 15 "qcom,rpm-ipq8064" 16 "qcom,rpm-mdm9615" 18 - reg: 20 Value type: <prop-encoded-array> 23 - interrupts: 25 Value type: <prop-encoded-array> [all …]
|
| D | as3722.txt | 4 ------------------- 5 - compatible: Must be "ams,as3722". 6 - reg: I2C device address. 7 - interrupt-controller: AS3722 has internal interrupt controller which takes the 8 interrupt request from internal sub-blocks like RTC, regulators, GPIOs as well 10 - #interrupt-cells: Should be set to 2 for IRQ number and flags. 12 of AS3722 are defined at dt-bindings/mfd/as3722.h 14 interrupts.txt, using dt-bindings/irq. 17 -------------------- 18 - ams,enable-internal-int-pullup: Boolean property, to enable internal pullup on [all …]
|
| D | st,stpmic1.txt | 4 - compatible: : "st,stpmic1" 5 - reg: : The I2C slave address for the STPMIC1 chip. 6 - interrupts: : The interrupt line the device is connected to. 7 - #interrupt-cells: : Should be 1. 8 - interrupt-controller: : Marks the device node as an interrupt controller. 10 dt-bindings/mfd/st,stpmic1.h. 12 STPMIC1 consists in a varied group of sub-devices. 13 Each sub-device binding is be described in own documentation file. 16 ------ ------------ 17 st,stpmic1-onkey : Power on key, see ../input/st,stpmic1-onkey.txt [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | everest,es7241.txt | 4 - compatible : "everest,es7241" 5 - VDDP-supply: regulator phandle for the VDDA supply 6 - VDDA-supply: regulator phandle for the VDDP supply 7 - VDDD-supply: regulator phandle for the VDDD supply 10 - reset-gpios: gpio connected to the reset pin 11 - m0-gpios : gpio connected to the m0 pin 12 - m1-gpios : gpio connected to the m1 pin 13 - everest,sdout-pull-down: 15 the sdout. If the sdout is pulled down, leftj format is used. 21 linein: audio-codec@2 { [all …]
|
| D | wm8994.txt | 8 - compatible : One of "wlf,wm1811", "wlf,wm8994" or "wlf,wm8958". 10 - reg : the I2C address of the device for I2C, the chip select 13 - gpio-controller : Indicates this device is a GPIO controller. 14 - #gpio-cells : Must be 2. The first cell is the pin number and the 17 - AVDD2-supply, DBVDD1-supply, DBVDD2-supply, DBVDD3-supply, CPVDD-supply, 18 SPKVDD1-supply, SPKVDD2-supply : power supplies for the device, as covered 19 in Documentation/devicetree/bindings/regulator/regulator.txt 23 - interrupts : The interrupt line the IRQ signal for the device is 26 - interrupt-controller : These devices contain interrupt controllers 29 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2. [all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | allwinner,sunxi-pinctrl.txt | 6 the pins includes drive strength and pull-up. 9 - compatible: Should be one of the following (depending on your SoC): 10 "allwinner,sun4i-a10-pinctrl" 11 "allwinner,sun5i-a10s-pinctrl" 12 "allwinner,sun5i-a13-pinctrl" 13 "allwinner,sun6i-a31-pinctrl" 14 "allwinner,sun6i-a31s-pinctrl" 15 "allwinner,sun6i-a31-r-pinctrl" 16 "allwinner,sun7i-a20-pinctrl" 17 "allwinner,sun8i-a23-pinctrl" [all …]
|
| D | img,pistachio-pinctrl.txt | 8 each. The GPIO banks are represented as sub-nodes of the pad controller node. 10 Please refer to pinctrl-bindings.txt, ../gpio/gpio.txt, and 11 ../interrupt-controller/interrupts.txt for generic information regarding 15 -------------------------------------------- 16 - compatible: "img,pistachio-system-pinctrl". 17 - reg: Address range of the pinctrl registers. 19 Required properties for GPIO bank sub-nodes: 20 -------------------------------------------- 21 - interrupts: Interrupt line for the GPIO bank. 22 - gpio-controller: Indicates the device is a GPIO controller. [all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | ci-hdrc-usb2.txt | 4 - compatible: should be one of: 5 "fsl,imx23-usb" 6 "fsl,imx27-usb" 7 "fsl,imx28-usb" 8 "fsl,imx6q-usb" 9 "fsl,imx6sl-usb" 10 "fsl,imx6sx-usb" 11 "fsl,imx6ul-usb" 12 "fsl,imx7d-usb" 13 "fsl,imx7ulp-usb" [all …]
|
| /Documentation/driver-api/ |
| D | pinctl.rst | 9 - Enumerating and naming controllable pins 11 - Multiplexing of pins, pads, fingers (etc) see below for details 13 - Configuration of pins, pads, fingers (etc), such as software-controlled 14 biasing and driving mode specific pins, such as pull-up/down, open drain, 17 Top-level interface 22 - A pin controller is a piece of hardware, usually a set of registers, that 28 - PINS are equal to pads, fingers, balls or whatever packaging input or 32 be sparse - i.e. there may be gaps in the space with numbers where no 98 See for example arch/arm/mach-u300/Kconfig for an example. 197 the groups is up to the driver, this is just a simple example - in practice you [all …]
|