linux/drivers/regulator, branch v3.3

regulator: da9052: Ensure the selected voltage falls within the specified range

2012-03-11T20:39:10Z

Integer division may truncate the result, use DIV_ROUND_UP to ensure the selected voltage falls within the specified range. Signed-off-by: Axel Lin Signed-off-by: Mark Brown

regulator: Set n_voltages for da9052 regulators

2012-03-11T20:39:04Z

The n_voltages setting for all LDOs and DCDCs are missing in current code. Signed-off-by: Axel Lin Signed-off-by: Mark Brown

regulator: Fix setting selector in tps6524x set_voltage function

2012-03-11T20:38:10Z

Don't assign the voltage to selector. Signed-off-by: Axel Lin Signed-off-by: Mark Brown Cc: stable@vger.kernel.org

regulator: tps65910: Configure correct value for VDDCTRL vout reg

2012-03-07T19:28:37Z

As per datasheet, the voltage output is defined as from SEL[6:0] = 3 to 64 (dec) Vout= (SEL[6:0] × 12.5 mV + 562.5 mV) The list_voltage returns the vout as 600mV + selector * 12.5mV and so equivalent VSEL is selector + 3. Adding 3 on selector when configuring VSEL register for VDDCTRL output. Signed-off-by: Laxman Dewangan Signed-off-by: Mark Brown

regulator: Fix mask parameter in da9052_reg_update calls

2012-03-05T12:28:58Z

If the mask parameter is 0, info->activate_bit bit won't be set by calling da9052_reg_update. Signed-off-by: Axel Lin Signed-off-by: Mark Brown

regulator: fix the ldo configure according to 88pm860x spec

2012-02-24T14:56:32Z

Signed-off-by: Jett.Zhou Signed-off-by: Mark Brown Cc: stable@vger.kernel.org

regulator: Fix getting voltage in max8649_enable_time()

2012-02-10T11:20:55Z

Current code takes wrong parameter while calling max8649_list_voltage. Signed-off-by: Axel Lin Signed-off-by: Mark Brown

regulator: Fix mc13xxx regulator modular build (again)

2012-02-09T22:57:46Z

Since mc13xxx-regulator-core.c and the actual drivers can get built into seperate modules, you have to export the DT support symbols "mc13xxx_get_num_regulators_dt" and "mc13xxx_parse_regulators_dt" otherwise the allmodconfig build fails on sparc64. [Updated the subject; the same thing was previously reported and fixed in -next but for some reason nobody noticed for some considerable time after the issue was introduced -- broonie] Signed-off-by: David S. Miller Signed-off-by: Mark Brown

Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator

2012-01-30T18:16:25Z

This fixes an integration issue with the regulator device tree bindings which shook out in -rc. The bindings were overly enthusiatic when deciding to set a voltage on a regulator and would try to set zero volts on an unconfigured regulator which isn't supported. * tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator: regulator: Set apply_uV only when min and max voltages are defined

regulator: Set apply_uV only when min and max voltages are defined

2012-01-26T11:01:21Z

apply_uV is errornously set when regulator is instantiated from device tree, even when it doesn't contain any voltage constraints. This commit fixes error: machine_constraints_voltage: CHARGER: failed to apply 0uV constraint for following regulator description in DTS: CHARGER { regulator-min-microamp = <100000>; regulator-max-microamp = <200000>; } Signed-off-by: Karol Lewandowski Signed-off-by: Kyungmin Park Signed-off-by: Mark Brown