Hi while testing an omap3 board with device tree support I stumbled upon a bug which is due to wrong initialization order of twl-core and twl-regulator (I suppose): In the boot process they get loaded way too late so that a lot of drivers before where configured wrong or just refuse to load.
For example the real time clock driver: The RTC kicks in way before twl_probe() and due to that it configures its register map wrong (at this time twl_priv->twl_id isn't configured yet). Another example is the omap display subsystem. It (DSS) fails loading while trying to register some not yet existent regulators and because it lacks EPROBE_DEFER. USB and MMC is also not working and I'm suspicious of the same cause. Any ideas? Thanks -- Christoph -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
