u-boot.git/drivers/power, branch v2019.01

power: regulator: Allow PWM regulator to be omitted from SPL.

2019-01-02T21:38:09+00:00

This patch allows to enable the PWM regulator driver
independent for U-Boot and SPL.

Signed-off-by: Christoph Muellner 
Reviewed-by: Philipp Tomsich

power: regulator: Return success on attempt to disable an always-on regulator

2018-12-27T12:48:31+00:00

commit 4f86a724e82c0 ("power: regulator: denied disable on always-on
regulator") throws an error when requested to disable an always-on
regulator. It is right that an always-on regulator should not be
attempted to be disabled. But at the same time regulator framework
should not return an error when such request is received. Instead
it should just return success without attempting to disable the
specified regulator. This is because the requesting driver will
not have the idea if the regulator is always-on or not. The
requesting driver will always try to enable/disable regulator as
per the required flow. So it is upto regulator framework to not
break such scenarios.

Fixes: 4f86a724e82c0 ("power: regulator: denied disable on always-on regulator")
Reported-by: Jean-Jacques Hiblot 
Reviewed-by: Faiz Abbas 
Signed-off-by: Lokesh Vutla

Merge tag 'for-master-20181210' of git://git.denx.de/u-boot-rockchip

2018-12-10T15:19:09+00:00

Improvements:
- init DRAM for RK322x in SPL
- add FAN53555 PMIC/regulator driver
- update MicroCrystal RV3029 driver to Kconfig and sync from Linux
- add bootcount uclass and first DM-driver for bootcount

power: add FAN53555 family support

2018-12-10T09:04:45+00:00

This adds a driver for the FAN53555 family of regulators and wraps it
in a PMIC implementation.

While these devices support a 'normal' and 'suspend' mode (controlled
via an external pin) to switch between two programmable voltages, this
incarnation of the driver assumes that the device is always operating
in 'normal' mode.

Only setting/reading the programmed voltage is supported at this time
and the following device functionality remains unsupported:
  - switching the selected voltage (via a GPIO)
  - disabling the voltage output via software-control
This matches the functionality of the Linux driver.

Tested on a RK3399-Q7 (with 'option 5' devices): setting voltages from
the U-Boot shell and verifying output voltages on the board.

Signed-off-by: Philipp Tomsich 
Tested-by: Klaus Goger

power: make most tps drivers and the twl4030 driver compatible with DM_I2C

2018-12-10T05:17:30+00:00

Those driver are not DM drivers per se (not using the PMIC/regulator
framework) and are using the legacy I2C API. Make them compatible with
the DM_I2C API.

This impacts the following drivers:
- palmas (used by am57xx/dra7xx evms)
- tps65218 (used by am43xx evms)
- tps65217 and tps65910 (used by am335x evms and am335x boneblack vboot)
- twl4030 (used by omap3_logicpd)
- tps65217 (used by brppt1)
- twl6030

Signed-off-by: Jean-Jacques Hiblot 
Reviewed-by: Tom Rini 
Reviewed-by: Heiko Schocher

power: axp209: Limit inrush current for broken boards

2018-12-07T16:54:33+00:00

Some boards feature a capacitance on LDO3's output that is too large,
causing inrush currents which as a result, shut down the AXP209. This
has been reported before, without knowing the actual cause.

A fix appeared to be done with
commit 0e6e34ac8dbb ("sunxi: Olimex A20 boards: Enable LDO3 and LDO4 regulators").

The description there is a bit misleading, the kernel does not hang
during AXP209 initialization, the PMIC shuts down, causing voltages to
drop and thus the whole system freezes.

While the AXP209 does have the ability to ramp up the voltage slowly, to
reduce these inrush currents, the voltage rate control (VRC) however is
not applicable when switching on the LDO3 output. Only when going from
an enabled lower voltage setting, to a higher voltage setting is the VRC
in effect.

To work around this problem, we set LDO3 to the lowest possible setting
of 0.7 V if it was not yet enabled, and then let the VRC (if enabled) do
its thing. It should be noted, that for some undocumented reason, there
is a short delay needed between setting the LDO3 voltage register and
enabling the power. One would expect that this delay ought to be just
after enabling the output power at 0.7 V, but this did not work.

Signed-off-by: Olliver Schinagl 
Signed-off-by: Priit Laes 
Acked-by: Maxime Ripard

power: axp209: Add support for voltage rate control on LDO3

2018-12-07T16:54:33+00:00

The AXP209 LDO3 regulator supports voltage rate control, or can set a
slew rate.

This allows for the power to gradually rise up to the desired voltage,
instead of spiking up as fast as possible. Reason to have this can be
to reduce the inrush currents for example.

There are 3 slopes to choose from, the default, 'none' is a voltage rise
of 0.0167 V/uS, a 1.6 mV/uS and a 0.8 mV/uS voltage rise.

In ideal world (where vendors follow the recommended design guidelines)
this setting should not be enabled by default. Unless of course AXP209
crashes instead of reporting overcurrent condition as it normally should
do in this case.

Signed-off-by: Olliver Schinagl 
Signed-off-by: Priit Laes 
Acked-by: Maxime Ripard

power: axp209: Reduce magic values by adding defines for LDO[234]

2018-12-07T16:54:33+00:00

The AXP209 has a few 'magisc-ish' values that are better served with
clear defines.

Signed-off-by: Olliver Schinagl 
Signed-off-by: Priit Laes 
Acked-by: Maxime Ripard

power: axp209: Define the chip version mask

2018-12-07T16:54:33+00:00

Use a define for the chip version mask on the axp209.

Signed-off-by: Olliver Schinagl 
Signed-off-by: Priit Laes 
Acked-by: Maxime Ripard

power: regulator: denied disable on always-on regulator

2018-12-05T13:06:44+00:00

Don't disable regulator which are tagged as "regulator-always-on" in DT.

Signed-off-by: Patrick Delaunay 
Reviewed-by: Simon Glass 
Reviewed-by: Jack Mitchell 
Tested-by: Jack Mitchell 
Signed-off-by: Patrice Chotard 
Reviewed-by: Richard Röjfors 
Tested-by: Richard Röjfors 
Reviewed-by: Felix Brack 
Tested-by: Felix Brack