2011-11-18 16:47:17 +05:30
Voltage/Current Regulators
Optional properties:
- regulator-name: A string used as a descriptive name for regulator outputs
- regulator-min-microvolt: smallest voltage consumers may set
- regulator-max-microvolt: largest voltage consumers may set
- regulator-microvolt-offset: Offset applied to voltages to compensate for voltage drops
- regulator-min-microamp: smallest current consumers may set
- regulator-max-microamp: largest current consumers may set
2015-06-11 17:37:06 -07:00
- regulator-input-current-limit-microamp: maximum input current regulator allows
2011-11-18 16:47:17 +05:30
- regulator-always-on: boolean, regulator should never be disabled
- regulator-boot-on: bootloader/firmware enabled regulator
2013-06-20 14:07:37 +05:30
- regulator-allow-bypass: allow the regulator to go into bypass mode
2015-08-18 15:14:06 -07:00
- regulator-allow-set-load: allow the regulator performance level to be configured
2011-11-18 16:47:17 +05:30
- <name>-supply: phandle to the parent supply/regulator node
2012-06-18 14:03:16 +08:00
- regulator-ramp-delay: ramp delay for regulator(in uV/uS)
2014-04-04 22:31:00 -04:00
For hardware which supports disabling ramp rate, it should be explicitly
2015-04-30 15:38:59 +05:30
initialised to zero (regulator-ramp-delay = <0>) for disabling ramp delay.
2013-09-18 18:18:02 +05:30
- regulator-enable-ramp-delay: The time taken, in microseconds, for the supply
rail to reach the target voltage, plus/minus whatever tolerance the board
design requires. This property describes the total system ramp time
required due to the combination of internal ramping of the regulator itself,
and board design issues such as trace capacitance and load on the supply.
2015-06-11 17:37:05 -07:00
- regulator-soft-start: Enable soft start so that voltage ramps slowly
2014-10-10 20:35:34 +09:00
- regulator-state-mem sub-root node for Suspend-to-RAM mode
: suspend to memory, the device goes to sleep, but all data stored in memory,
only some external interrupt can wake the device.
- regulator-state-disk sub-root node for Suspend-to-DISK mode
: suspend to disk, this state operates similarly to Suspend-to-RAM,
but includes a final step of writing memory contents to disk.
- regulator-state-[mem/disk] node has following common properties:
- regulator-on-in-suspend: regulator should be on in suspend state.
- regulator-off-in-suspend: regulator should be off in suspend state.
2014-10-31 20:52:57 -07:00
- regulator-suspend-microvolt: regulator should be set to this voltage
in suspend.
2014-11-10 14:43:51 +01:00
- regulator-mode: operating mode in the given suspend state.
The set of possible operating modes depends on the capabilities of
every hardware so the valid modes are documented on each regulator
device tree binding document.
- regulator-initial-mode: initial operating mode. The set of possible operating
modes depends on the capabilities of every hardware so each device binding
documentation explains which values the regulator supports.
2015-06-11 17:37:03 -07:00
- regulator-system-load: Load in uA present on regulator that is not captured by
any consumer request.
2015-06-11 17:37:04 -07:00
- regulator-pull-down: Enable pull down resistor when the regulator is disabled.
2015-07-17 14:41:54 -07:00
- regulator-over-current-protection: Enable over current protection.
2016-03-02 16:24:45 +05:30
- regulator-active-discharge: tristate, enable/disable active discharge of
regulators. The values are:
0: Disable active discharge.
1: Enable active discharge.
Absence of this property will leave configuration to default.
regulator: deprecate regulator-compatible DT property
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and
However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.
Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.
The code is changed such that old device trees continue to work.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-09-24 13:25:00 -06:00
Deprecated properties:
2012-07-05 12:53:04 +05:30
- regulator-compatible: If a regulator chip contains multiple
regulators, and if the chip's binding contains a child node that
describes each regulator, then this property indicates which regulator
regulator: deprecate regulator-compatible DT property
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and
However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.
Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.
The code is changed such that old device trees continue to work.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-09-24 13:25:00 -06:00
this child node is intended to configure. If this property is missing,
the node's name will be used instead.
2011-11-18 16:47:17 +05:30
Example:
xyzreg: regulator@0 {
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <2500000>;
regulator-always-on;
vin-supply = <&vin>;
2014-10-10 20:35:34 +09:00
regulator-state-mem {
regulator-on-in-suspend;
};
2011-11-18 16:47:17 +05:30
};
Regulator Consumers:
Consumer nodes can reference one or more of its supplies/
regulators using the below bindings.
- <name>-supply: phandle to the regulator node
These are the same bindings that a regulator in the above
example used to reference its own supply, in which case
its just seen as a special case of a regulator being a
consumer itself.
Example of a consumer device node (mmc) referencing two
2011-11-28 21:37:16 +08:00
regulators (twl_reg1 and twl_reg2),
2011-11-18 16:47:17 +05:30
2011-11-28 21:37:16 +08:00
twl_reg1: regulator@0 {
2011-11-18 16:47:17 +05:30
...
...
...
};
2011-11-28 21:37:16 +08:00
twl_reg2: regulator@1 {
2011-11-18 16:47:17 +05:30
...
...
...
};
mmc: mmc@0x0 {
...
...
2011-11-28 21:37:16 +08:00
vmmc-supply = <&twl_reg1>;
vmmcaux-supply = <&twl_reg2>;
2011-11-18 16:47:17 +05:30
};