linux.git/drivers/regulator, branch v3.5-rc4

regulator: Change db8500-prcmu match names to reflect Device Tree

2012-06-17T17:27:49+00:00

The 'name' field in 'struct of_regulator_match' expects to match with
its corresponding regulator device node in the Device Tree. This patch
renames each of the regulators in the db8500-prcum regulator driver so
this is true.

Signed-off-by: Lee Jones 
Acked-by: Linus Walleij 
Signed-off-by: Mark Brown

regulator: Change ab8500 match names to reflect Device Tree

2012-06-17T17:27:47+00:00

The 'name' field in 'struct of_regulator_match' expects to match with
its corresponding regulator device node in the Device Tree. This patch
renames each of the regulators in the ab8500 regulator driver so this
is true.

Signed-off-by: Lee Jones 
Acked-by: Linus Walleij 
Signed-off-by: Mark Brown

regulator: Fix the s5m8767a problem of the division by null

2012-06-17T17:27:20+00:00

If ramp_delay is 0, delay value can be divided by zero.
This patch can fix the problem.

Signed-off-by: Sangbeom Kim 
Signed-off-by: Mark Brown

regulator: core: Properly handle the case min_uV < rdev->desc->min_uV in map_voltage_linear

2012-06-07T23:15:55+00:00

Properly handle the case if the specified min_uV is less than the voltage given
by the lowest selector.

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown

regulator: max8649: fix missing regmap in rdev

2012-06-05T10:15:22+00:00

In probe(), rdev->regmap must be assigned.

Signed-off-by: Haojian Zhuang 
Signed-off-by: Mark Brown

regulator: gpio-regulator: populate selector from set_voltage

2012-06-04T09:44:30+00:00

This was missing until now and the underlying
_regulator_do_set_voltage is using this value when calling list_voltage.

Signed-off-by: Heiko Stuebner 
Acked-by: Axel Lin 
Signed-off-by: Mark Brown

regulator: gpio-regulator: Fix finding of smallest value

2012-06-04T09:44:24+00:00

Commit 4dbd8f63f07a (regulator: gpio-regulator: Set the smallest
voltage/current in the specified range) forgot to set the newly
introduced best_val.

Therefore it stayed always at INT_MAX thus breaking the setting
of the voltage.

Included is also an init value for target, as warnings about
a possibly uninitialised target started appearing with this fix.

Signed-off-by: Heiko Stuebner 
Acked-by: Axel Lin 
Signed-off-by: Mark Brown

regulator: gpio-regulator: do not pass drvdata pointer as reference

2012-06-04T09:44:18+00:00

Commit c172708d38a4 (regulator: core: Use a struct to pass in
regulator runtime configuration) added the drvdata pointer
only per reference to the new config array in the gpio-regulator.

Signed-off-by: Heiko Stuebner 
Acked-by: Axel Lin 
Signed-off-by: Mark Brown

regulator: anatop: Use correct __devexit_p annotation

2012-06-04T09:42:49+00:00

__devexit functions are discarded when CONFIG_HOTPLUG
is not set, so the symbol needs to be referenced carefully.

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown

regulator: palmas: Fix wrong kfree calls

2012-06-04T09:42:49+00:00

The devm_kzalloc function eliminates the need for manual resource releasing
and simplify error handling. Resources allocated by devm_* are freed
automatically on driver detach.

Thus adding kfree calls here will introduce double free bug.

The memory of desc array and the pointers to the rdev[] are allocated by
devm_kzalloc call for struct palmas_pmic.

struct palmas_pmic {
        struct palmas *palmas;
        struct device *dev;
        struct regulator_desc desc[PALMAS_NUM_REGS];
        struct regulator_dev *rdev[PALMAS_NUM_REGS];
        struct mutex mutex;

        int smps123;
        int smps457;

        int range[PALMAS_REG_SMPS10];
};

Which means we should not call kfree for pmic->rdev and pmic->desc.

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown