Home
last modified time | relevance | path

Searched +full:regulator +full:- +full:state +full:- (Results 1 – 25 of 60) sorted by relevance

123

/Documentation/devicetree/bindings/regulator/
Dmcp16502-regulator.txt4 - 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 …]
Dregulator.yaml1 # 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 …]
Dtps62360-regulator.txt4 - 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.
21 If this property is missing, then assume the state as low (0).
22 - ti,vsel1-state-high: Initial state of vsel1 input is high.
23 If this property is missing, then assume the state as low (0).
[all …]
Dact8945a-regulator.txt1 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 …]
Dqcom,rpmh-regulator.txt3 rpmh-regulator devices support PMIC regulator management via the Voltage
4 Regulator Manager (VRM) and Oscillator Buffer (XOB) RPMh accelerators. The APPS
5 processor communicates with these hardware blocks via a Resource State
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:
9 its enable state. Despite its name, the XOB is capable of controlling the
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:
[all …]
Dgpio-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
14 Any property defined as part of the core regulator binding, defined in
15 regulator.txt, can also be used.
18 - $ref: "regulator.yaml#"
22 const: regulator-gpio
[all …]
Dmax77802.txt3 This is a part of device tree bindings of MAX77802 multi-function device.
6 The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout (LDO)
12 - inb1-supply: The input supply for BUCK1
13 - inb2-supply: The input supply for BUCK2
14 - inb3-supply: The input supply for BUCK3
15 - inb4-supply: The input supply for BUCK4
16 - inb5-supply: The input supply for BUCK5
17 - inb6-supply: The input supply for BUCK6
18 - inb7-supply: The input supply for BUCK7
19 - inb8-supply: The input supply for BUCK8
[all …]
Dlp872x.txt4 - compatible: "ti,lp8720" or "ti,lp8725"
5 - reg: I2C slave address. 0x7d = LP8720, 0x7a = LP8725
8 - ti,general-config: the value of LP872X_GENERAL_CFG register (u8)
27 - ti,update-config: define it when LP872X_GENERAL_CFG register should be set
28 - ti,dvs-gpio: GPIO specifier for external DVS pin control of LP872x devices.
29 - ti,dvs-vsel: DVS selector. 0 = SEL_V1, 1 = SEL_V2.
30 - ti,dvs-state: initial DVS pin state. 0 = DVS_LOW, 1 = DVS_HIGH.
31 - enable-gpios: GPIO specifier for EN pin control of LP872x devices.
37 (Documentation/devicetree/bindings/regulator/regulator.txt)
40 - LP8720: http://www.ti.com/lit/ds/symlink/lp8720.pdf
[all …]
Dregulator-max77620.txt1 Regulator DT binding for MAX77620 Power management IC from Maxim Semiconductor.
3 Device has multiple DCDC(sd[0-3] and LDOs(ldo[0-8]). The input supply
5 Details of regulator properties are defined as child node under
6 sub-node "regulators" which is child node of device node.
8 Please refer file <Documentation/devicetree/bindings/regulator/regulator.txt>
9 for common regulator bindings used by client.
14 -------------------
18 in-sd0-supply: Input supply for SD0, INA-SD0 or INB-SD0 pins.
19 in-sd1-supply: Input supply for SD1.
20 in-sd2-supply: Input supply for SD2.
[all …]
Drohm,bd71837-regulator.txt1 ROHM BD71837 and BD71847 Power Management Integrated Circuit regulator bindings
4 - regulator-name: should be "buck1", ..., "buck8" and "ldo1", ..., "ldo7" for
10 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
11 Regulator nodes should be named to BUCK_<number> and LDO_<number>. The
14 Documentation/devicetree/bindings/regulator/regulator.txt.
15 Note that if BD71837 starts at RUN state you probably want to use
16 regulator-boot-on at least for BUCK6 and BUCK7 so that those are not
21 The valid names for BD71837 regulator nodes are:
25 The valid names for BD71847 regulator nodes are:
30 - rohm,dvs-run-voltage : PMIC default "RUN" state voltage in uV.
[all …]
Dmax8973-regulator.txt1 * Maxim MAX8973 Voltage Regulator
5 - compatible: must be one of following:
8 - reg: the i2c slave address of the regulator. It should be 0x1b.
10 Any standard regulator properties can be used to configure the single max8973
15 -maxim,externally-enable: boolean, externally control the regulator output
17 -maxim,enable-gpio: GPIO for enable control. If the valid GPIO is provided
19 -maxim,dvs-gpio: GPIO which is connected to DVS pin of device.
20 -maxim,dvs-default-state: Default state of GPIO during initialisation.
22 -maxim,enable-remote-sense: boolean, enable reote sense.
23 -maxim,enable-falling-slew-rate: boolean, enable falling slew rate.
[all …]
Dact8865-regulator.txt2 -------------------
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 …]
/Documentation/ABI/testing/
Dsysfs-class-regulator1 What: /sys/class/regulator/.../state
6 Some regulator directories will contain a field called
7 state. This reports the regulator enable control, for
16 'enabled' means the regulator output is ON and is supplying
19 'disabled' means the regulator output is OFF and is not
20 supplying power to the system (unless some non-Linux
23 'unknown' means software cannot determine the state, or
24 the reported state is invalid.
27 or microamps to determine configured regulator output levels.
30 What: /sys/class/regulator/.../status
[all …]
/Documentation/devicetree/bindings/mfd/
Drohm,bd71837-pmic.txt4 single-core, dual-core, and quad-core SoCs such as NXP-i.MX 8M. They are
10 https://www.rohm.com/datasheet/BD71837MWV/bd71837mwv-e
12 https://www.rohm.com/datasheet/BD71847AMWV/bd71847amwv-e
15 - compatible : Should be "rohm,bd71837" for bd71837
17 - reg : I2C slave address.
18 - interrupt-parent : Phandle to the parent interrupt controller.
19 - interrupts : The interrupt line the device is connected to.
20 - clocks : The parent clock connected to PMIC. If this is missing
22 - #clock-cells : Should be 0.
23 - regulators: : List of child nodes that specify the regulators.
[all …]
Dtps65910.txt4 - compatible: "ti,tps65910" or "ti,tps65911"
5 - reg: I2C slave address
6 - interrupts: the interrupt outputs of the controller
7 - #gpio-cells: number of cells to describe a GPIO, this should be 2.
10 - gpio-controller: mark the device as a GPIO controller
11 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
14 Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
15 - regulators: This is the list of child nodes that specify the regulator
19 Documentation/devicetree/bindings/regulator/regulator.txt.
20 The regulator is matched with the regulator-compatible.
[all …]
Das3722.txt4 -------------------
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 …]
Dmax77620.txt4 -------------------
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.
21 - system-power-controller: Indicates that this PMIC is controlling the
[all …]
/Documentation/devicetree/bindings/iio/dac/
Dad5592r.txt4 - compatible: Must be "adi,ad5592r"
5 - reg: SPI chip select number for the device
6 - spi-max-frequency: Max SPI frequency to use (< 30000000)
7 - spi-cpol: The AD5592R requires inverse clock polarity (CPOL) mode
10 - compatible: Must be "adi,ad5593r"
11 - reg: I2C address of the device
14 - #address-cells: Should be 1.
15 - #size-cells: Should be 0.
16 - channel nodes:
22 can be found in <dt-bindings/iio/adi,ad5592r.h>.
[all …]
/Documentation/power/regulator/
Dconsumer.rst2 Regulator Consumer Driver Interface
5 This text describes the regulator interface for consumer device drivers.
9 1. Consumer Regulator Access (static & dynamic drivers)
12 A consumer driver can get access to its supply regulator by calling ::
14 regulator = regulator_get(dev, "Vcc");
17 then finds the correct regulator by consulting a machine specific lookup table.
19 regulator that supplies this consumer.
21 To release the regulator the consumer driver should call ::
23 regulator_put(regulator);
25 Consumers can be supplied by more than one regulator e.g. codec consumer with
[all …]
Ddesign.rst2 Regulator API design notes
6 of the design considerations which impact the regulator API design.
9 ------
11 - Errors in regulator configuration can have very serious consequences
13 - It is not possible to automatically determine the power configuration
14 of the system - software-equivalent variants of the same chip may
20 The API should make no changes to the hardware state unless it has
25 ------------------
27 - The overwhelming majority of devices in a system will have no
31 - Many of the power supplies in the system will be shared between many
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smd-rpm.txt5 for state of the system resources, such as clocks, regulators and bus
15 present and this subnode may contain children that designate regulator
18 - compatible:
22 "qcom,rpm-apq8084"
23 "qcom,rpm-msm8916"
24 "qcom,rpm-msm8974"
25 "qcom,rpm-msm8998"
26 "qcom,rpm-sdm660"
27 "qcom,rpm-qcs404"
29 - qcom,smd-channels:
[all …]
/Documentation/devicetree/bindings/sound/
Dadi,adau1977.txt4 http://www.analog.com/media/en/technical-documentation/data-sheets/ADAU1977.pdf
5 http://www.analog.com/media/en/technical-documentation/data-sheets/ADAU1978.pdf
6 http://www.analog.com/media/en/technical-documentation/data-sheets/ADAU1979.pdf
11 - compatible: Should contain one of the following:
16 - AVDD-supply: analog power supply for the device, please consult
17 Documentation/devicetree/bindings/regulator/regulator.txt
20 - reset-gpios: the reset pin for the chip, for more details consult
23 - DVDD-supply: supply voltage for the digital core, please consult
24 Documentation/devicetree/bindings/regulator/regulator.txt
26 - adi,micbias: configures the voltage setting for the MICBIAS pin.
[all …]
/Documentation/devicetree/bindings/display/msm/
Dhdmi.txt4 - compatible: one of the following
5 * "qcom,hdmi-tx-8996"
6 * "qcom,hdmi-tx-8994"
7 * "qcom,hdmi-tx-8084"
8 * "qcom,hdmi-tx-8974"
9 * "qcom,hdmi-tx-8660"
10 * "qcom,hdmi-tx-8960"
11 - reg: Physical base address and length of the controller's registers
12 - reg-names: "core_physical"
13 - interrupts: The interrupt signal from the hdmi block.
[all …]
/Documentation/devicetree/bindings/gnss/
Dmediatek.txt1 Mediatek-based GNSS Receiver DT binding
3 Mediatek chipsets are used in GNSS-receiver modules produced by several
11 - compatible : Must be
15 - vcc-supply : Main voltage regulator (pin name: VCC)
19 - current-speed : Default UART baud rate
20 - gnss-fix-gpios : GPIO used to determine device position fix state
22 - reset-gpios : GPIO used to reset the device (pin name: RESET, NRESET)
23 - timepulse-gpios : Time pulse GPIO (pin name: PPS1, 1PPS)
24 - vbackup-supply : Backup voltage regulator (pin name: VBAT, VBACKUP)
33 vcc-supply = <&vcc_3v3>;
/Documentation/devicetree/bindings/pwm/
Dnvidia,tegra20-pwm.txt4 - compatible: Must be:
5 - "nvidia,tegra20-pwm": for Tegra20
6 - "nvidia,tegra30-pwm", "nvidia,tegra20-pwm": for Tegra30
7 - "nvidia,tegra114-pwm", "nvidia,tegra20-pwm": for Tegra114
8 - "nvidia,tegra124-pwm", "nvidia,tegra20-pwm": for Tegra124
9 - "nvidia,tegra132-pwm", "nvidia,tegra20-pwm": for Tegra132
10 - "nvidia,tegra210-pwm", "nvidia,tegra20-pwm": for Tegra210
11 - "nvidia,tegra186-pwm": for Tegra186
12 - reg: physical base address and length of the controller's registers
13 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
[all …]

123