__omap2_common_pm_late_init too early
Hi,
I analyzed boot issues a bit:
On the bt200 (OMAP4460) I see:
[ 1.647430] twl: not initialized [ 1.650817] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for
1375000 Vs max 1316660
All that is called from __omap2_common_pm_late_init
Well, the second line is the consequence of the first line. TWL is not initialized yet, nor i2c nor ti-sysc.
So that cannot work. Probably it did only work in days when async probe was not that widespread.
It is declared asomap_late_initcall(omap2_common_pm_late_init);
In the past there were some stories where omap3 offmode could only be enabled from userspace... So maybe more trouble here because we are doing things sometimes too early.
I am a bit unsure when it should be started.
For comparison, other places where things should be done when the system should be basically known:
clk uses late_initcall_sync() instead of late_initcall() for disabling unused clocks.
regualtor uses late_initcall_sync() +30s delayed_work for disabling unused regulators.
Opinions?
Regards,
Andreas