linux-toradex.git/drivers/regulator/mc13892-regulator.c, branch v3.2.29

regulator: Add module.h to drivers/regulator users as required

2011-10-31T23:32:15+00:00

Another group of drivers that are taking advantage of the implicit
presence of module.h -- and will break when we pull the carpet out
from under them during a cleanup.  Fix 'em now.

Signed-off-by: Paul Gortmaker

regulator: mc13892: Fix voltage unit in test case.

2011-05-27T09:49:10+00:00

Voltage values should be expressed in microvolts, not in milivolts.

Signed-off-by: Fabio Estevam 
Signed-off-by: Ranjani Vaidyanathan 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

Revert "regulator: Move VCOINCELL to be the last element of mc13892_regulators array"

2011-05-27T09:49:09+00:00

I check this patch again and found this actually is not a bug
because MC13xxx_DEFINE explictly defines the order of each entry in the array.

Thus revert the patch.

Signed-off-by: Axel Lin 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Use mc13xxx_reg_write instead of mc13xxx_reg_rmw in mc13892_sw_regulator_set_voltage

2011-05-27T09:34:37+00:00

Currently, we call mc13xxx_reg_read and mc13xxx_reg_rmw for the same register.
This can be converted to simply a mc13xxx_reg_read and a mc13xxx_reg_write,
thus save a redundant register read.

Signed-off-by: Axel Lin 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Move VCOINCELL to be the last element of mc13892_regulators array

2011-05-27T09:34:37+00:00

In include/linux/mfd/mc13892.h, we define MC13892_VCOINCELL as 23.
Thus VCOINCELL should be defined as 23th element in mc13892_regulators array, not the first one.
This actually fixes an off-by-one bug while accessing mc13892_regulators array.

For example,
In mc13892_regulator_probe, we use MC13892_VCAM as array index of mc13892_regulators array.
        mc13892_regulators[MC13892_VCAM].desc.ops->set_mode
                = mc13892_vcam_set_mode;
Currently, it access mc13892_regulators[12] ,which is VAUDIO not VCAM.

Signed-off-by: Axel Lin 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

mfd: Use mfd cell platform_data for mc13xxx cells platform bits

2011-05-26T17:45:07+00:00

With the addition of a platform device mfd_cell pointer, MFD drivers
can go back to passing platform data back to their sub drivers.
This allows for an mfd_cell->mfd_data removal and thus keep the
sub drivers MFD agnostic. This is mostly needed for non MFD aware
sub drivers.

Cc: Mark Brown 
Cc: Liam Girdwood 
Acked-by: Uwe Kleine-König 
Signed-off-by: Samuel Ortiz

mfd: mfd_cell is now implicitly available to mc13xxx drivers

2011-03-23T09:41:54+00:00

The cell's platform_data is now accessed with a helper function;
change clients to use that, and remove the now-unused data_size.

Note that mfd-core no longer makes a copy of platform_data, but the
mc13xxx-core driver creates the pdata structures on the stack.  In
order to get around that, the various ARM mach types that set the
pdata have been changed to hold the variable in static (global) memory.
Also note that __initdata references in aforementioned pdata structs
have been dropped.

Signed-off-by: Andres Salomon 
Signed-off-by: Samuel Ortiz

regulator: Assign return value of mc13xxx_reg_rmw to ret

2011-01-12T14:33:05+00:00

Otherwise, we will not return error if write to MC13892_SWITCHERS5 failed.

Signed-off-by: Axel Lin 
Acked-by: Yong Shen 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Staticise non-exported functions in mc13892

2011-01-12T14:33:05+00:00

No point exposing functions that aren't used elsewhere to the global
namespace and sparse warns about doing so.

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

regulator: support PMIC mc13892

2011-01-12T14:33:03+00:00

add support for mc13892, tested on mx51 babbage board

Signed-off-by: Arnaud Patard 
Signed-off-by: Yong Shen 
Acked-by: Sascha Hauer 
Acked-by: Samuel Ortiz 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood