Searched +full:voltage +full:- +full:microvolt (Results 1 – 25 of 640) sorted by relevance
12345678910>>...26
| /kernel/linux/linux-4.19/arch/arm64/boot/dts/qcom/ |
| D | msm8994-smd-rpm.dtsi | 17 pm8994-regulators {
19 vdd_l1-supply = <&pm8994_s1>;
20 vdd_l2_26_28-supply = <&pm8994_s3>;
21 vdd_l3_11-supply = <&pm8994_s3>;
22 vdd_l4_27_31-supply = <&pm8994_s3>;
23 vdd_l5_7-supply = <&pm8994_s3>;
24 vdd_l6_12_32-supply = <&pm8994_s5>;
25 vdd_l8_16_30-supply = <&vreg_vph_pwr>;
26 vdd_l9_10_18_22-supply = <&vreg_vph_pwr>;
27 vdd_l13_19_23_24-supply = <&vreg_vph_pwr>;
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/regulator/ |
| D | ltc3589.txt | 1 Linear Technology LTC3589, LTC3589-1, and LTC3589-2 8-output regulators
4 - compatible: "lltc,ltc3589", "lltc,ltc3589-1" or "lltc,ltc3589-2"
5 - reg: I2C slave address
8 - regulators: Contains eight regulator child nodes sw1, sw2, sw3, bb-out,
13 nodes for sw1, sw2, sw3, bb-out, ldo1, and ldo2 additionally need to specify
14 the resistor values of their external feedback voltage dividers:
17 - lltc,fb-voltage-divider: An array of two integers containing the resistor
18 values R1 and R2 of the feedback voltage divider in ohms.
21 0.3625 V to 0.75 V in 12.5 mV steps. The output voltage thus ranges between
22 0.3625 * (1 + R1/R2) V and 0.75 * (1 + R1/R2) V. Regulators bb-out and ldo1
[all …]
|
| D | ltc3676.txt | 1 Linear Technology LTC3676 8-output regulators
4 - compatible: "lltc,ltc3676"
5 - reg: I2C slave address
8 - regulators: Contains eight regulator child nodes sw1, sw2, sw3, sw4,
14 the resistor values of their external feedback voltage dividers:
17 - lltc,fb-voltage-divider: An array of two integers containing the resistor
18 values R1 and R2 of the feedback voltage divider in ohms.
21 412.5mV to 800mV in 12.5 mV steps. The output voltage thus ranges between
26 regulator can not be disabled and thus should have the regulator-always-on
37 regulator-min-microvolt = <674400>;
[all …]
|
| D | pwm-regulator.txt | 6 Voltage Table: When in this mode, a voltage table (See below) of
7 predefined voltage <=> duty-cycle values must be
10 Intermediary duty-cycle values which would normally
11 allow finer grained voltage selection are ignored and
13 the user if the assumptions made in continuous-voltage
16 Continuous Voltage: This mode uses the regulator's maximum and minimum
18 regulator-{min,max}-microvolt properties to calculate
19 appropriate duty-cycle values. This allows for a much
21 voltage-table mode above. This solution does make an
22 assumption that a %50 duty-cycle value will cause the
[all …]
|
| D | vctrl.txt | 1 Bindings for Voltage controlled regulators
5 --------------------
6 - compatible : must be "vctrl-regulator".
7 - regulator-min-microvolt : smallest voltage consumers may set
8 - regulator-max-microvolt : largest voltage consumers may set
9 - ctrl-supply : The regulator supplying the control voltage.
10 - ctrl-voltage-range : an array of two integer values describing the range
11 (min/max) of the control voltage. The values specify
12 the control voltage needed to generate the corresponding
13 regulator-min/max-microvolt output voltage.
[all …]
|
| D | regulator.txt | 1 Voltage/Current Regulators
4 - regulator-name: A string used as a descriptive name for regulator outputs
5 - regulator-min-microvolt: smallest voltage consumers may set
6 - regulator-max-microvolt: largest voltage consumers may set
7 - regulator-microvolt-offset: Offset applied to voltages to compensate for voltage drops
8 - regulator-min-microamp: smallest current consumers may set
9 - regulator-max-microamp: largest current consumers may set
10 - regulator-input-current-limit-microamp: maximum input current regulator allows
11 - regulator-always-on: boolean, regulator should never be disabled
12 - regulator-boot-on: bootloader/firmware enabled regulator
[all …]
|
| D | samsung,s5m8767.txt | 4 This is a part of device tree bindings for S5M family multi-function devices.
5 More information can be found in bindings/mfd/sec-core.txt file.
10 a sub-node named "regulators" with more sub-nodes for each regulator using the
12 - Documentation/devicetree/bindings/regulator/regulator.txt
16 - s5m8767,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
17 units for buck2 when changing voltage using gpio dvs. Refer to [1] below
20 - s5m8767,pmic-buck3-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
21 units for buck3 when changing voltage using gpio dvs. Refer to [1] below
24 - s5m8767,pmic-buck4-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
25 units for buck4 when changing voltage using gpio dvs. Refer to [1] below
[all …]
|
| D | max8997-regulator.txt | 1 * Maxim MAX8997 Voltage and Current Regulator
3 The Maxim MAX8997 is a multi-function device which includes voltage and
4 current regulators, rtc, charger controller and other sub-blocks. It is
5 interfaced to the host controller using a i2c interface. Each sub-block is
7 describes the bindings for 'pmic' sub-block of max8997.
10 - compatible: Should be "maxim,max8997-pmic".
11 - reg: Specifies the i2c slave address of the pmic block. It should be 0x66.
13 - max8997,pmic-buck1-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
14 units for buck1 when changing voltage using gpio dvs. Refer to [1] below
17 - max8997,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | ltc3589.txt | 1 Linear Technology LTC3589, LTC3589-1, and LTC3589-2 8-output regulators
4 - compatible: "lltc,ltc3589", "lltc,ltc3589-1" or "lltc,ltc3589-2"
5 - reg: I2C slave address
8 - regulators: Contains eight regulator child nodes sw1, sw2, sw3, bb-out,
13 nodes for sw1, sw2, sw3, bb-out, ldo1, and ldo2 additionally need to specify
14 the resistor values of their external feedback voltage dividers:
17 - lltc,fb-voltage-divider: An array of two integers containing the resistor
18 values R1 and R2 of the feedback voltage divider in ohms.
21 0.3625 V to 0.75 V in 12.5 mV steps. The output voltage thus ranges between
22 0.3625 * (1 + R1/R2) V and 0.75 * (1 + R1/R2) V. Regulators bb-out and ldo1
[all …]
|
| D | ltc3676.txt | 1 Linear Technology LTC3676 8-output regulators
4 - compatible: "lltc,ltc3676"
5 - reg: I2C slave address
8 - regulators: Contains eight regulator child nodes sw1, sw2, sw3, sw4,
14 the resistor values of their external feedback voltage dividers:
17 - lltc,fb-voltage-divider: An array of two integers containing the resistor
18 values R1 and R2 of the feedback voltage divider in ohms.
21 412.5mV to 800mV in 12.5 mV steps. The output voltage thus ranges between
26 regulator can not be disabled and thus should have the regulator-always-on
37 regulator-min-microvolt = <674400>;
[all …]
|
| D | pwm-regulator.txt | 6 Voltage Table: When in this mode, a voltage table (See below) of
7 predefined voltage <=> duty-cycle values must be
10 Intermediary duty-cycle values which would normally
11 allow finer grained voltage selection are ignored and
13 the user if the assumptions made in continuous-voltage
16 Continuous Voltage: This mode uses the regulator's maximum and minimum
18 regulator-{min,max}-microvolt properties to calculate
19 appropriate duty-cycle values. This allows for a much
21 voltage-table mode above. This solution does make an
22 assumption that a %50 duty-cycle value will cause the
[all …]
|
| D | nxp,pca9450-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/regulator/nxp,pca9450-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Robin Gong <yibin.gong@nxp.com>
18 https://www.nxp.com/docs/en/data-sheet/PCA9450DS.pdf
28 - nxp,pca9450a
29 - nxp,pca9450b
30 - nxp,pca9450c
44 "^LDO[1-5]$":
[all …]
|
| D | vctrl.txt | 1 Bindings for Voltage controlled regulators
5 --------------------
6 - compatible : must be "vctrl-regulator".
7 - regulator-min-microvolt : smallest voltage consumers may set
8 - regulator-max-microvolt : largest voltage consumers may set
9 - ctrl-supply : The regulator supplying the control voltage.
10 - ctrl-voltage-range : an array of two integer values describing the range
11 (min/max) of the control voltage. The values specify
12 the control voltage needed to generate the corresponding
13 regulator-min/max-microvolt output voltage.
[all …]
|
| D | regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Voltage/Current Regulators
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
14 regulator-name:
18 regulator-min-microvolt:
19 description: smallest voltage consumers may set
21 regulator-max-microvolt:
[all …]
|
| D | nvidia,tegra-regulators-coupling.txt | 4 NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators.
8 Tegra20 voltage coupling
9 ------------------------
13 and they both shall be higher than the CPU voltage by at least 120mV.
15 Tegra30 voltage coupling
16 ------------------------
20 voltage shall be higher than the CPU by N mV, where N depends on the CPU
21 voltage.
24 - nvidia,tegra-core-regulator: Boolean property that designates regulator
25 as the "Core domain" voltage regulator.
[all …]
|
| D | samsung,s5m8767.txt | 4 This is a part of device tree bindings for S5M family multi-function devices.
5 More information can be found in bindings/mfd/sec-core.txt file.
10 a sub-node named "regulators" with more sub-nodes for each regulator using the
12 - Documentation/devicetree/bindings/regulator/regulator.txt
16 - s5m8767,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
17 units for buck2 when changing voltage using gpio dvs. Refer to [1] below
20 - s5m8767,pmic-buck3-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
21 units for buck3 when changing voltage using gpio dvs. Refer to [1] below
24 - s5m8767,pmic-buck4-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
25 units for buck4 when changing voltage using gpio dvs. Refer to [1] below
[all …]
|
| D | max8997-regulator.txt | 1 * Maxim MAX8997 Voltage and Current Regulator
3 The Maxim MAX8997 is a multi-function device which includes voltage and
4 current regulators, rtc, charger controller and other sub-blocks. It is
5 interfaced to the host controller using a i2c interface. Each sub-block is
7 describes the bindings for 'pmic' sub-block of max8997.
10 - compatible: Should be "maxim,max8997-pmic".
11 - reg: Specifies the i2c slave address of the pmic block. It should be 0x66.
13 - max8997,pmic-buck1-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
14 units for buck1 when changing voltage using gpio dvs. Refer to [1] below
17 - max8997,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/ |
| D | battery.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
14 In smart batteries, these are typically stored in non-volatile memory
16 no appropriate non-volatile memory, or it is unprogrammed/incorrect.
27 Batteries must be referenced by chargers and/or fuel-gauges using a phandle.
28 The phandle's property should be named "monitored-battery".
32 const: simple-battery
34 over-voltage-threshold-microvolt:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd71837-pmic.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71837-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
13 BD71837MWV is programmable Power Management ICs for powering single-core,
14 dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is optimized for low
18 …/www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applica…
35 "#clock-cells":
48 # crucial regulators must have the regulator-always-on and regulator-boot-on
[all …]
|
| D | rohm,bd71847-pmic.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71847-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
14 single-core, dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is
18 …/www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applica…
19 …//www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applic…
24 - rohm,bd71847
25 - rohm,bd71850
[all …]
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/freescale/ |
| D | imx8mq-pico-pi.dts | 1 // SPDX-License-Identifier: GPL-2.0+
9 /dts-v1/;
12 #include <dt-bindings/interrupt-controller/irq.h>
15 model = "TechNexion PICO-PI-8M";
16 compatible = "technexion,pico-pi-imx8m", "fsl,imx8mq";
19 stdout-path = &uart1;
22 pmic_osc: clock-pmic {
23 compatible = "fixed-clock";
24 #clock-cells = <0>;
25 clock-frequency = <32768>;
[all …]
|
| D | imx8mq-phanbell.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
3 * Copyright 2017-2019 NXP
6 /dts-v1/;
9 #include <dt-bindings/interrupt-controller/irq.h>
13 compatible = "google,imx8mq-phanbell", "fsl,imx8mq";
16 stdout-path = &uart1;
24 pmic_osc: clock-pmic {
25 compatible = "fixed-clock";
26 #clock-cells = <0>;
27 clock-frequency = <32768>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/opp/ |
| D | allwinner,sun50i-h6-operating-points.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/opp/allwinner,sun50i-h6-operating-points.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <mripard@kernel.org>
14 For some SoCs, the CPU frequency subset and voltage value of each
16 Voltage Scaling Tables defines the voltage and frequency value based
18 sun50i-cpufreq-nvmem driver reads the efuse value from the SoC to
23 const: allwinner,sun50i-h6-operating-points
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/boot/dts/ |
| D | imx53-usbarmory.dts | 8 * This file is dual-licensed: you can use it either under the terms
47 /dts-v1/;
52 compatible = "inversepath,imx53-usbarmory", "fsl,imx53";
57 stdout-path = &uart1;
66 compatible = "gpio-leds";
67 pinctrl-names = "default";
68 pinctrl-0 = <&pinctrl_led>;
73 linux,default-trigger = "heartbeat";
83 operating-points = <
92 pinctrl-names = "default";
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | imx53-usbarmory.dts | 8 * This file is dual-licensed: you can use it either under the terms
47 /dts-v1/;
52 compatible = "inversepath,imx53-usbarmory", "fsl,imx53";
57 stdout-path = &uart1;
66 compatible = "gpio-leds";
67 pinctrl-names = "default";
68 pinctrl-0 = <&pinctrl_led>;
73 linux,default-trigger = "heartbeat";
83 operating-points = <
92 pinctrl-names = "default";
[all …]
|
12345678910>>...26