17 Dec, 2009
3 commits
-
When the mc13783-regulator driver is built in kernel, probing it during
the regulator subsystem initialisation result in a fault.That is because regulator subsystem is planned to be initialised very early
in the boot process, before the mfd subsystem initialisation.The mc12783-regulator probing process need to access to the mc13783-core
functionality to read/write mc13783 registers and so must be called after
the mc13783-core driver initialisation.The way to do this is to let the kernel probe the mc13783-regulator driver when
mc13783-core register his regulator subdevice.Signed-off-by: Alberto Panizzo
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
- define needed registers and bits in the driver
- properly namespace functions and structs
- fix locking as required by patch
"mfd/mc13783: near complete rewrite"
- use platform_data as provided by "mfd/mc13783: near complete rewrite"
instead of accessing struct mc13783
- struct mc13783_regulator_priv.desc is (and was) unused and so can go
away
- use cpp magic to initialize mc13783_regulators
- bring MODULE_LICENSE in sync with actual copyright
- minor style fixesThis allows not including mc13783-private.h which I intend to remove
soon.Signed-off-by: Uwe Kleine-König
Cc: Sascha Hauer
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Samuel Ortiz
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
One annoying thing about the old name was that the module was just
called mc13783 which caused wrong expectations (at least for me).Signed-off-by: Uwe Kleine-König
Cc: Sascha Hauer
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Samuel Ortiz
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood
