Hi, This RFC provides support for moving hwmod data into separate modules which can be registered later during boot. Only system critical parts of the hwmod data remain in omap_hwmod_*_early_data.c file, rest are moved into omap_hwmod_*_late_data.c. The late data can alternatively be built into a module, or built-in to kernel image, in which case the system behaves pretty much the same way as it does currently. Use kconfig option OMAP_HWMOD_DATA_MODULES to control the behavior. If this approach is something that is seen feasible to follow, rest of the SoCs can be converted in similar manner, and eventually all the hwmod code should be moved under some driver (drivers/bus/ maybe?) This RFC set only provides support for omap3 hwmod data split. Please note that you probably must use ramdisk rootfs to load the hwmod data module itself from, as most of the system devices are not initialized in the early boot. Testing done on omap3-beagle: - boot, insmod, suspend-resume (ret/off), cpuidle (ret/off) Boot log for omap3 here: http://pastebin.ubuntu.com/10826443/ - some spam generated by USB here, it seems to defer probe until i2c/twl is ready - some additional debug prints enabled for testing purposes Trial branch pushed here: - tree: https://github.com/t-kristo/linux-pm.git - branch: 4.0-hwmod-split-rfc -Tero -- 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
