Searched +full:regulator +full:- +full:type (Results 1 – 25 of 58) sorted by relevance
123
| /Documentation/devicetree/bindings/regulator/ |
| 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 …]
|
| D | qcom,spmi-regulator.txt | 3 - compatible:
5 Value type: <string>
7 "qcom,pm8005-regulators"
8 "qcom,pm8841-regulators"
9 "qcom,pm8916-regulators"
10 "qcom,pm8941-regulators"
11 "qcom,pm8994-regulators"
12 "qcom,pmi8994-regulators"
13 "qcom,pms405-regulators"
15 - interrupts:
[all …]
|
| D | fixed-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/fixed-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.yaml, can also be used. However a fixed voltage regulator is
16 expected to have the regulator-min-microvolt and regulator-max-microvolt
20 - $ref: "regulator.yaml#"
[all …]
|
| D | gpio-regulator.yaml | 1 # 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 …]
|
| D | qcom,smd-rpm-regulator.txt | 1 QCOM SMD RPM REGULATOR
3 The Qualcomm RPM over SMD regulator is modelled as a subdevice of the RPM.
5 a subnode of the SMD. As such, the SMD-RPM regulator requires that the SMD and
11 Please refer to Documentation/devicetree/bindings/soc/qcom/qcom,smd-rpm.txt for
14 == Regulator
16 Regulator nodes are identified by their compatible:
18 - compatible:
20 Value type: <string>
22 "qcom,rpm-pm8841-regulators"
23 "qcom,rpm-pm8916-regulators"
[all …]
|
| D | sprd,sc2731-regulator.txt | 3 The SC2731 integrates low-voltage and low quiescent current DCDC/LDO.
5 their own bypass (power-down) control signals. External tantalum or MLCC
9 - compatible: should be "sprd,sc27xx-regulator".
12 its regulator type, BUCK_<name> and LDO_<name>. The definition for each
14 Documentation/devicetree/bindings/regulator/regulator.txt.
26 compatible = "sprd,sc27xx-regulator";
29 regulator-name = "vddarm0";
30 regulator-min-microvolt = <400000>;
31 regulator-max-microvolt = <1996875>;
32 regulator-ramp-delay = <25000>;
[all …]
|
| D | max8660.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/max8660.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Maxim MAX8660 voltage regulator
10 - Daniel Mack <zonque@gmail.com>
14 pattern: "pmic@[0-9a-f]{1,2}"
17 - maxim,max8660
18 - maxim,max8661
24 type: object
[all …]
|
| D | mt6380-regulator.txt | 1 MediaTek MT6380 Regulator
4 subnodes of the MT6380 regulators node. Each regulator is named according
5 to its regulator type, buck-<name> and ldo-<name>. The definition for each
7 Documentation/devicetree/bindings/regulator/regulator.txt.
11 buck-core1, buck-vcore, buck-vrf
13 ldo-vm ,ldo-va , ldo-vphy, ldo-vddr, ldo-vt
18 compatible = "mediatek,mt6380-regulator";
20 mt6380_vcpu_reg: buck-vcore1 {
21 regulator-name = "vcore1";
22 regulator-min-microvolt = < 600000>;
[all …]
|
| D | palmas-pmic.txt | 1 * palmas regulator IP block devicetree bindings
11 - compatible : Should be from the list
12 ti,twl6035-pmic
13 ti,twl6036-pmic
14 ti,twl6037-pmic
15 ti,tps65913-pmic
16 ti,tps65914-pmic
17 ti,tps65917-pmic
18 ti,tps659038-pmic
20 ti,palmas-pmic
[all …]
|
| D | mt6397-regulator.txt | 1 Mediatek MT6397 Regulator
4 - compatible: "mediatek,mt6397-regulator"
5 - mt6397regulator: List of regulators provided by this controller. It is named
6 according to its regulator type, buck_<name> and ldo_<name>.
8 for regulators at Documentation/devicetree/bindings/regulator/regulator.txt.
24 compatible = "mediatek,mt6397-regulator";
27 regulator-compatible = "buck_vpca15";
28 regulator-name = "vpca15";
29 regulator-min-microvolt = < 850000>;
30 regulator-max-microvolt = <1350000>;
[all …]
|
| D | mt6323-regulator.txt | 1 Mediatek MT6323 Regulator
5 PMIC's node. Each regulator is named according to its regulator type,
8 Documentation/devicetree/bindings/regulator/regulator.txt.
24 regulator-name = "vproc";
25 regulator-min-microvolt = < 700000>;
26 regulator-max-microvolt = <1350000>;
27 regulator-ramp-delay = <12500>;
28 regulator-always-on;
29 regulator-boot-on;
33 regulator-name = "vsys";
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qcom-rpm.txt | 8 - compatible:
10 Value type: <string>
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:
[all …]
|
| D | axp20x.txt | 4 axp152 (X-Powers)
5 axp202 (X-Powers)
6 axp209 (X-Powers)
7 axp221 (X-Powers)
8 axp223 (X-Powers)
9 axp803 (X-Powers)
10 axp806 (X-Powers)
11 axp809 (X-Powers)
12 axp813 (X-Powers)
20 - compatible: should be one of:
[all …]
|
| D | as3711.txt | 4 standard regulator properties, they must belong to a sub-node, called
9 - compatible : must be "ams,as3711"
10 - reg : specifies the I2C address
14 - su1-dev : framebuffer phandle
15 - su1-max-uA : maximum current
19 - su2-dev : framebuffer phandle
20 - su1-max-uA : maximum current
22 Additionally one of these properties must be provided to select the type of
24 - su2-feedback-voltage : voltage feedback is used
25 - su2-feedback-curr1 : CURR1 input used for current feedback
[all …]
|
| D | max8998.txt | 1 * Maxim MAX8998, National/TI LP3974 multi-function device
3 The Maxim MAX8998 is a multi-function device which includes voltage/current
5 other sub-blocks. It is interfaced using an I2C interface. Each sub-block
8 PMIC sub-block
9 --------------
11 The PMIC sub-block contains a number of voltage and current regulators,
17 - compatible: Should be one of the following:
18 - "maxim,max8998" for Maxim MAX8998
19 - "national,lp3974" or "ti,lp3974" for National/TI LP3974.
20 - reg: Specifies the i2c slave address of the pmic block. It should be 0x66.
[all …]
|
| D | ab8500.txt | 1 * AB8500 Multi-Functional Device (MFD)
4 - compatible : contains "stericsson,ab8500";
5 - interrupts : contains the IRQ line for the AB8500
6 - interrupt-controller : describes the AB8500 as an Interrupt Controller (has its own domain)
7 - #interrupt-cells : should be 2, for 2-cell format
8 - The first cell is the AB8500 local IRQ number
9 - The second cell is used to specify optional parameters
10 - bits[3:0] trigger type and level flags:
11 1 = low-to-high edge triggered
12 2 = high-to-low edge triggered
[all …]
|
| /Documentation/driver-api/ |
| D | regulator.rst | 1 .. Copyright 2007-2008 Wolfson Microelectronics
8 Voltage and current regulator API
20 The intention is to allow systems to dynamically control regulator power
27 ``Documentation/power/regulator``.
30 --------
32 The regulator API uses a number of terms which may not be familiar:
34 Regulator
42 Electronic device which consumes power provided by a regulator. These
44 requiring active management of the regulator at runtime.
48 The electronic circuit supplied by a given regulator, including the
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | qcom,usb-8x16-phy.txt | 3 - compatible:
5 Value type: <string>
6 Definition: Should contain "qcom,usb-8x16-phy".
8 - reg:
10 Value type: <prop-encoded-array>
13 - clocks:
15 Value type: <prop-encoded-array>
16 Definition: See clock-bindings.txt section "consumers". List of
20 - clock-names:
22 Value type: <string>
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smd-rpm.txt | 15 present and this subnode may contain children that designate regulator
18 - compatible:
20 Value type: <string>
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/ABI/testing/ |
| D | sysfs-class-regulator | 1 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
27 or microamps to determine configured regulator output levels.
30 What: /sys/class/regulator/.../status
32 Some regulator directories will contain a field called
33 "status". This reports the current regulator status, for
[all …]
|
| /Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,saw2.txt | 5 power-controller that transitions a piece of hardware (like a processor or
21 - compatible:
23 Value type: <string>
27 "qcom,apq8064-saw2-v1.1-cpu"
28 "qcom,msm8974-saw2-v2.1-cpu"
29 "qcom,apq8084-saw2-v2.1-cpu"
31 - reg:
33 Value type: <prop-encoded-array>
38 - regulator:
40 Value type: boolean
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | qcom_smbb.txt | 1 Qualcomm Switch-Mode Battery Charger and Boost
4 - compatible:
6 Value type: <stringlist>
8 - "qcom,pm8941-charger"
10 - reg:
12 Value type: <prop-encoded-array>
15 - interrupts:
17 Value type: <prop-encoded-array>
21 - charge done
22 - charge fast mode
[all …]
|
| /Documentation/devicetree/bindings/input/rmi4/ |
| D | rmi_i2c.txt | 10 - compatible: syna,rmi4-i2c
11 - reg: I2C address
12 - #address-cells: Set to 1 to indicate that the function child nodes
14 - #size-cells: Set to 0 to indicate that the function child nodes do not
18 - interrupts: interrupt which the rmi device is connected to.
19 See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
21 - syna,reset-delay-ms: The number of milliseconds to wait after resetting the
24 - syna,startup-delay-ms: The number of milliseconds to wait after powering on
27 - vdd-supply: VDD power supply.
28 See ../regulator/regulator.txt
[all …]
|
| /Documentation/devicetree/bindings/connector/ |
| D | usb-connector.txt | 8 - compatible: describes type of the connector, must be one of:
9 "usb-a-connector",
10 "usb-b-connector",
11 "usb-c-connector".
14 - label: symbolic name for the connector,
15 - type: size of the connector, should be specified in case of USB-A, USB-B
16 non-fullsize connectors: "mini", "micro".
17 - self-powered: Set this property if the usb device that has its own power
20 Optional properties for usb-b-connector:
21 - id-gpios: an input gpio for USB ID pin.
[all …]
|
123