linux-toradex.git/drivers/regulator/of_regulator.c, branch v4.10 Linux kernel for Apalis and Colibri modules regulator: of: setup initial suspend state 2016-06-22T15:15:34+00:00 Keerthy j-keerthy@ti.com 2016-06-20T08:43:31+00:00 a0f78bc89c0396d14b6102c6f72485e14c8821f3 Setup initial suspend state to mem, if suspend state is defined for mem state. This makes sure that the regulators are in proper mode already from boot. Signed-off-by: Tero Kristo <t-kristo@ti.com> Signed-off-by: Dave Gerlach <d-gerlach@ti.com> Signed-off-by: Keerthy <j-keerthy@ti.com> Signed-off-by: Mark Brown <broonie@kernel.org> 
Setup initial suspend state to mem, if suspend state is defined for
mem state. This makes sure that the regulators are in proper mode
already from boot.

Signed-off-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
Signed-off-by: Keerthy <j-keerthy@ti.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
regulator: of: Don't flag voltage change as possible for exact voltages 2016-03-30T15:26:09+00:00 Mark Brown broonie@kernel.org 2016-03-30T15:26:09+00:00 45fa2038cf7820ecfcca8793b81e656ca3caaf0f Flagging voltage changes as possible for exactly specified voltages appears to be triggering bugs in the SDHCI code (it should be able to handle the case where only one voltage it wants is in the range it is allowed to set) so make sure we only set the flag in cases where there's genuine variability. Signed-off-by: Mark Brown <broonie@kernel.org> 
Flagging voltage changes as possible for exactly specified voltages
appears to be triggering bugs in the SDHCI code (it should be able to
handle the case where only one voltage it wants is in the range it is
allowed to set) so make sure we only set the flag in cases where there's
genuine variability.

Signed-off-by: Mark Brown <broonie@kernel.org>
regulator: core: Ensure we are at least in bounds for our constraints 2016-03-27T09:02:43+00:00 Mark Brown broonie@kernel.org 2016-03-21T18:12:52+00:00 fa93fd4ecc9c58475abac6db93a797bff893bc16 Currently we only attempt to set the voltage during constraints application if an exact voltage is specified. Extend this so that if the currently set voltage for the regulator is outside the bounds set in constraints we will move the voltage to the nearest constraint, raising to the minimum or lowering to the maximum as needed. This ensures that drivers can probe without the hardware being driven out of spec. Reported-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com> Tested-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com> Signed-off-by: Mark Brown <broonie@kernel.org> 
Currently we only attempt to set the voltage during constraints
application if an exact voltage is specified.  Extend this so that if
the currently set voltage for the regulator is outside the bounds set in
constraints we will move the voltage to the nearest constraint, raising
to the minimum or lowering to the maximum as needed.  This ensures that
drivers can probe without the hardware being driven out of spec.

Reported-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
Tested-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
regulator: core: Always flag voltage constraints as appliable 2016-03-22T10:30:12+00:00 Mark Brown broonie@kernel.org 2016-03-21T18:17:43+00:00 895fe2321efaf62023fdd8239d1846394df68570 Allow the core to always use the voltage constraints to set the voltage on startup. A forthcoming change in that code will ensure that we bring out of constraints voltages into spec with this setting. Signed-off-by: Mark Brown <broonie@kernel.org> 
Allow the core to always use the voltage constraints to set the voltage
on startup.  A forthcoming change in that code will ensure that we bring
out of constraints voltages into spec with this setting.

Signed-off-by: Mark Brown <broonie@kernel.org>
Merge remote-tracking branches 'regulator/topic/mt6397', 'regulator/topic/of', 'regulator/topic/pv88060', 'regulator/topic/pwm' and 'regulator/topic/s2mps11' into regulator-next 2016-03-13T08:20:00+00:00 Mark Brown broonie@kernel.org 2016-03-13T08:20:00+00:00 41eeb34acd3def009b1dd827364c9ed6d70ca4ea 






regulator: of: Use of_property_read_u32() for reading min/max
2016-03-12T05:59:33+00:00

Laxman Dewangan
ldewangan@nvidia.com

2016-03-10T12:12:47+00:00

a34785f10d33f70680941da284d7ec3a612aad1a

OF interface provides to read the u32 value via standard interface
of_property_read_u32(). Use this API to read "regulator-min-microvolts"
and "regulator-max-microvolt".

This will make consistent with other property value reads.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: Mark Brown <broonie@kernel.org>





OF interface provides to read the u32 value via standard interface
of_property_read_u32(). Use this API to read "regulator-min-microvolts"
and "regulator-max-microvolt".

This will make consistent with other property value reads.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: Mark Brown <broonie@kernel.org>







regulator: core: Add support for active-discharge configuration
2016-03-02T14:13:05+00:00

Laxman Dewangan
ldewangan@nvidia.com

2016-03-02T10:54:46+00:00

670666b9e0aff40c65d8061a2f53e79eee238685

Add support to enable/disable active discharge of regulator via
machine constraints. This configuration is done when setting
machine constraint during regulator register and if regulator
driver implemented the callback ops.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: Mark Brown <broonie@kernel.org>





Add support to enable/disable active discharge of regulator via
machine constraints. This configuration is done when setting
machine constraint during regulator register and if regulator
driver implemented the callback ops.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: Mark Brown <broonie@kernel.org>







regulator: Introduce property to flag set-load support
2015-09-17T11:14:12+00:00

Bjorn Andersson
bjorn.andersson@sonymobile.com

2015-08-18T22:14:06+00:00

b263d20373d7726dd3ac0cd5e32f123e69a02847

Introduce "regulator-allow-set-load" property to make it possible to
flag in the board configuration that a regulator is allowed to have the
load requirements changed.

Signed-off-by: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Signed-off-by: Mark Brown <broonie@kernel.org>





Introduce "regulator-allow-set-load" property to make it possible to
flag in the board configuration that a regulator is allowed to have the
load requirements changed.

Signed-off-by: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Signed-off-by: Mark Brown <broonie@kernel.org>







regulator: Add over current protection (OCP) support
2015-07-24T17:28:46+00:00

Stephen Boyd
sboyd@codeaurora.org

2015-07-17T21:41:54+00:00

3a003baeec246f604ed1d2e0087560d7f15edcc6

Some regulators can automatically shut down when they detect an
over current event. Add an op (set_over_current_protection) and a
DT property + constraint to support this capability.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Mark Brown <broonie@kernel.org>





Some regulators can automatically shut down when they detect an
over current event. Add an op (set_over_current_protection) and a
DT property + constraint to support this capability.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Mark Brown <broonie@kernel.org>







Merge remote-tracking branches 'regulator/topic/of', 'regulator/topic/pwm', 'regulator/topic/qcom' and 'regulator/topic/soft-start' into regulator-next
2015-06-22T10:19:56+00:00

Mark Brown
broonie@kernel.org

2015-06-22T10:19:56+00:00

733ada000f2c9618ccbac7b9ba146113f0a6675b