Searched +full:regulator +full:- +full:allowed +full:- +full:modes (Results 1 – 6 of 6) sorted by relevance
| /Documentation/devicetree/bindings/regulator/ |
| D | act8945a-regulator.txt | 1 Device-Tree bindings for regulators of Active-semi ACT8945A Multi-Function Device
4 - compatible: "active-semi,act8945a", please refer to ../mfd/act8945a.txt.
7 - active-semi,vsel-high: Indicates if the VSEL pin is set to logic-high.
8 If this property is missing, assume the VSEL pin is set to logic-low.
11 - vp1-supply: The input supply for REG_DCDC1
12 - vp2-supply: The input supply for REG_DCDC2
13 - vp3-supply: The input supply for REG_DCDC3
14 - inl45-supply: The input supply for REG_LDO1 and REG_LDO2
15 - inl67-supply: The input supply for REG_LDO3 and REG_LDO4
17 Any standard regulator properties can be used to configure the single regulator.
[all …]
|
| D | mcp16502-regulator.txt | 4 - compatible: "microchip,mcp16502"
5 - reg: I2C slave address
6 - lpm-gpios: GPIO for LPM pin. Note that this GPIO *must* remain high during
7 suspend-to-ram, keeping the PMIC into HIBERNATE mode.
8 - regulators: A node that houses a sub-node for each regulator within
9 the device. Each sub-node is identified using the node's
10 name. The content of each sub-node is defined by the
11 standard binding for regulators; see regulator.txt.
14 1) VDD_IO - Buck (1.2 - 3.7 V)
15 2) VDD_DDR - Buck (0.6 - 1.85 V)
[all …]
|
| D | act8865-regulator.txt | 2 -------------------
5 - compatible: "active-semi,act8846" or "active-semi,act8865" or "active-semi,act8600"
6 - reg: I2C slave address
9 - system-power-controller: Telling whether or not this pmic is controlling
10 the system power. See Documentation/devicetree/bindings/power/power-controller.txt .
11 - active-semi,vsel-high: Indicates the VSEL pin is high.
15 - for act8600:
16 - vp1-supply: The input supply for DCDC_REG1
17 - vp2-supply: The input supply for DCDC_REG2
18 - vp3-supply: The input supply for DCDC_REG3
[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 …]
|
| D | qcom,rpmh-regulator.txt | 3 rpmh-regulator devices support PMIC regulator management via the Voltage
4 Regulator Manager (VRM) and Oscillator Buffer (XOB) RPMh accelerators. The APPS
7 parameters for a given regulator: enable state, output voltage, and operating
8 mode. The XOB allows changing only a single parameter for a given regulator:
10 enable state of any PMIC peripheral. It is used for clock buffers, low-voltage
19 RPMh device node. The second level describes each regulator within the PMIC
23 The names used for regulator nodes must match those supported by a given PMIC.
24 Supported regulator node names:
25 PM8005: smps1 - smps4
26 PM8009: smps1 - smps2, ldo1 - ldo7
[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 …]
|