Commit 735eb93ae267f0b5638045b86dbc1e0b7019e3e8

Authored by Alberto Panizzo
Committed by Liam Girdwood
1 parent eb143ac1b9

regulator: mc13783-regulator: correct the probing time.

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 <maramaopercheseimorto@gmail.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>

Showing 1 changed file with 2 additions and 2 deletions Side-by-side Diff

drivers/regulator/mc13783-regulator.c
... ... @@ -224,12 +224,12 @@
224 224 .owner = THIS_MODULE,
225 225 },
226 226 .remove = __devexit_p(mc13783_regulator_remove),
  227 + .probe = mc13783_regulator_probe,
227 228 };
228 229  
229 230 static int __init mc13783_regulator_init(void)
230 231 {
231   - return platform_driver_probe(&mc13783_regulator_driver,
232   - mc13783_regulator_probe);
  232 + return platform_driver_register(&mc13783_regulator_driver);
233 233 }
234 234 subsys_initcall(mc13783_regulator_init);
235 235