On 04/16/2013 10:45 AM, Peter Ujfalusi wrote:
On 04/15/2013 06:25 PM, Tony Lindgren wrote:
This fix should not be needed. It just means the real
problem is somewhere else. Pinctrl is already before the i2c
in drivers/Makefile. Maybe one of the MFD drivers has
a wrong initcall level?
FYI; I just sent a patch which I believe is the correct way to fix this issue.
Hi Tony, Peter
OMAP i2c/pin-control initialization isn't controlled by Makefiles now (:
- i2c initialized at subsys_initcall(omap_i2c_init_driver);
- pinctrl-single at module_platform_driver(pcs_driver) => module_init =>
device_initcall (if built-in)
And pls, pay attention on overall BUG description - twl-regulators
initialization has been delayed as result all Regulators consumers
(drivers which use regulators) will need to defer it's probe correctly too.
For now it isn't true for many drivers and, for example,
omap_hsmmc driver's probe will just fail if it can't get regulator.
(+ problems with DSS - most probably Panel/DSI driver probe can't handle
pin configuration)
Before, on early kernel versions, the OMAP pinmux was ready to work at
arch_initcall time
and most of the code has been created with this assumption.
Unfortunately, RTC is just a small part of problem.
-grygorii
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
