linux-toradex.git/drivers/regulator/da903x.c, branch v2.6.38.8

regulator: Report actual configured voltage to set_voltage()

2011-01-12T14:32:59+00:00

Change the interface used by set_voltage() to report the selected value
to the regulator core in terms of a selector used by list_voltage().
This allows the regulator core to know the voltage that was chosen
without having to do an explict get_voltage(), which would be much more
expensive as it will generally access hardware.

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: keep index within bounds in da9034_get_ldo12_voltage()

2009-12-17T10:27:25+00:00

If selector equals ARRAY_SIZE(da9034_ldo12_data), that is one too
large already.

Signed-off-by: Roel Kluin 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: fix voltage range in da9034 ldo12

2009-09-22T12:58:23+00:00

Signed-off-by: Roel Kluin 
Signed-off-by: Haojian Zhuang 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: fix calculation of voltage range in da9034_set_ldo12_voltage()

2009-09-22T12:32:44+00:00

For val to be greater than 7 or less than 20 is logically always true.

Signed-off-by: Roel Kluin 
Cc: Liam Girdwood 
Cc: Mark Brown 
Signed-off-by: Andrew Morton 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: da903x: consolidate DA903[045]_DVC macros

2009-09-22T12:32:39+00:00

Signed-off-by: Mike Rapoport 
Signed-off-by: Liam Girdwood

regulator: support list voltage in da903x

2009-09-22T12:32:38+00:00

Make da903x driver to list voltage and count voltage.

Signed-off-by: Haojian Zhuang 
Acked-by: Mark Brown 
Acked-by: Eric Miao 
Signed-off-by: Liam Girdwood

regulator: replace ADTV1 register by ADTV2 in da903x

2009-09-22T12:32:37+00:00

In PXA3xx SoC family, V_CORE power doamin is supplied by BUCK1 that is
controller by ADTV1 or ADTV2 register.

By default, v1 and v2 has the same copy. If v1 or v2 is updated, the last
value that is written to either register takes effect. It means that v1
and v2 has different copy. And the actual voltage output is determinated
by last update on either register.

DA9034/35 is binded with PXA3xx SoC family. While SoC is scaling OP or
entering/exiting lower power mode, SoC needs to change voltage of V_CORE
power doamin. In order to be efficient, POWER I2C (hardcode) mode could
be enabled in SoC. In this mode, SoC will control v2 register directly.

In original DA903x driver, software will only read regulator data from v1
register. But SoC controls v2 register directly. It results that v1 and v2
isn't synchronized. Wrong data will be read from v1 register. So access v2
register in da903x driver instead.

Signed-off-by: Haojian Zhuang 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: support da9030 BUCK in da903x driver

2009-09-22T12:32:37+00:00

Support the operation of DA9030 BUCK2 in da903x driver.

Signed-off-by: Haojian Zhuang 
Acked-by: Mark Brown 
Acked-by: Eric Miao 
Acked-by: Mike Rapoport 
Signed-off-by: Liam Girdwood

regulator: add buck3 in da903x driver

2009-09-22T12:32:37+00:00

BUCK3 is the new component in DA9035. So there're three BUCKs in DA9035.
And there're two BUCKs in DA9034.

Signed-off-by: Haojian Zhuang 
Acked-by: Mark Brown 
Acked-by: Eric Miao 
Signed-off-by: Liam Girdwood

regulator: Move regulator drivers to subsys_initcall()

2009-06-15T10:18:23+00:00

Regulators need to be available early in init in order to allow them
to be available for consumers when requested. This is generally done
by registering them at subsys_initcall() time but not all regulator
drivers have done that. Convert these drivers to do so in order to
mimimise future support.

Signed-off-by: Mark Brown 
Acked-by: Mike Rapoport 
Signed-off-by: Liam Girdwood