On 10/20/2010 12:53 PM, Kevin Hilman wrote: > Ohad Ben-Cohen <ohad@xxxxxxxxxx> writes: > >> On Tue, Oct 19, 2010 at 7:03 PM, Kevin Hilman >> <khilman@xxxxxxxxxxxxxxxxxxx> wrote: >>>> +postcore_initcall(hwspinlocks_init); >>> >>> Any reason this needs to be a postcore_initcall? Are there users of >>> hwspinlocks this early in boot? >> >> i2c-omap, which is subsys_initcall (the I2C bus is shared between the >> A9 and the M3 on some OMAP4 boards). > > Rather than moving towards having more drivers have to be built in (and > depend on their probe order) we need to be moving towards building all > these drivers as modules, including omap-i2c. The issue of probe order still needs to be resolved for those of us who do want all the drivers built into the kernel. Everything comes out in the wash already if everything is built as modules by installing the modules in the correct order right? ~Ryan -- Bluewater Systems Ltd - ARM Technology Solution Centre Ryan Mallon 5 Amuri Park, 404 Barbadoes St ryan@xxxxxxxxxxxxxxxx PO Box 13 889, Christchurch 8013 http://www.bluewatersys.com New Zealand Phone: +64 3 3779127 Freecall: Australia 1800 148 751 Fax: +64 3 3779135 USA 1800 261 2934 -- 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
