linux.git/drivers/regulator/core.c, branch v4.13

Merge remote-tracking branches 'regulator/topic/settle', 'regulator/topic/tps65910' and 'regulator/topic/tps65917' into regulator-next

2017-07-03T15:52:21+00:00

Merge remote-tracking branch 'regulator/topic/core' into regulator-next

2017-07-03T15:52:16+00:00

regulator: core: Fix size limit of supply_map

2017-06-30T11:56:42+00:00

Now the debugfs file supply_map has a size limit PAGE_SIZE and the user
can not see the whole content of regulator_map_list when it is larger
than this limit.

This patch uses seq_file instead to make sure supply_map shows the full
information of regulator_map_list.

Signed-off-by: Haishan Zhou 
Signed-off-by: Mark Brown

regulator: core: Fix voltage change propagations to supply regulators

2017-06-28T19:39:36+00:00

Some regulators support get_voltage() and some support get_voltage_sel()
operations but currently we only propagate changes if the regulator has
a get_voltage() operation.  Also do this if we've got get_voltage_sel()

[Rewite commit message for clarity -- broonie]

Signed-off-by: Tirupathi Reddy 
Signed-off-by: Mark Brown

regulator: core: Prioritise consumer mappings over regulator name

2017-06-13T17:43:28+00:00

Currently, when looking up a regulator supply, the regulator name
takes priority over the consumer mappings. As there are a lot of
regulator names that are in fairly common use (VDD, MICVDD, etc.) this
can easily lead to obtaining the wrong supply, when a system contains
two regulators that share a name.

The explicit consumer mappings contain much less ambiguity as they
specify both a name and a consumer device. As such prioritise those if
one exists and only fall back to the regulator name if there are no
matching explicit mappings.

Signed-off-by: Charles Keepax 
Signed-off-by: Mark Brown

regulator: Allow for asymmetric settling times

2017-05-17T09:49:25+00:00

Some regulators have different settling times for voltage increases and
decreases. To avoid a time penalty on the faster transition allow for
different settings for up- and downward transitions.

Signed-off-by: Matthias Kaehlcke 
Acked-by: Laxman Dewangan 
Signed-off-by: Mark Brown

Merge remote-tracking branches 'regulator/topic/notifier', 'regulator/topic/pfuze100', 'regulator/topic/settle', 'regulator/topic/tps65132' and 'regulator/topic/twl6030' into regulator-next

2017-04-30T13:17:36+00:00

regulator: core: Allow dummy regulators for supplies

2017-04-14T17:08:01+00:00

Rather than just not resolving the supply when there is explicitly no
supply mapping fall through and allow a dummy supply to be substituted.
This fixes issues with constant retries reported by Dong Aisheng.

Signed-off-by: Mark Brown 
Tested-by: Dong Aisheng 
Reviewed-by: Dong Aisheng

regulator: core: Only propagate voltage changes to if it can change voltages

2017-04-14T17:07:51+00:00

When we are propagating voltage changes to parent regulators don't
bother if the parent does not have permission to change voltages.  This
simplifies error checking in the function for cases where the regulator
lacks some of the voltage operations.

Reported-by: Dong Aisheng 
Tested-by: Dong Aisheng 
Reviewed-by: Dong Aisheng 
Signed-off-by: Mark Brown

regulator: Add settling time for non-linear voltage transition

2017-04-05T17:25:10+00:00

Some regulators (some PWM regulators) have the voltage transition
non-linear i.e. exponentially. On such cases, the settling time
for voltage transition can not be presented in the voltage-ramp-delay.

Add new property for non-linear voltage transition and handle this
in getting the voltage settling time.

Signed-off-by: Laxman Dewangan 
Signed-off-by: Mark Brown