New Kconfig option added, OMAP_HWMOD_DATA_MODULES, which builds hwmod data as modules if enabled. By default, the data is built-in to kernel image for ease of use. Makefile is also changed to support building of the new hwmod data modules. Signed-off-by: Tero Kristo <t-kristo@xxxxxx> --- arch/arm/mach-omap2/Kconfig | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig index 2b8e477..a543dfe 100644 --- a/arch/arm/mach-omap2/Kconfig +++ b/arch/arm/mach-omap2/Kconfig @@ -299,6 +299,15 @@ config OMAP4_ERRATA_I688 In MPU case, L3 T2ASYNC FIFO and DDR T2ASYNC FIFO needs to be drained. IO barrier ensure that there is no synchronisation loss on initiators operating on both interconnect port simultaneously. + +config OMAP_HWMOD_DATA_MODULES + bool "OMAP hardware module data built to modules" + default n + help + Select whether hwmod data shall be built as modules, or built + in to kernel. By default, this option is n, which means all the + hwmod data will be built-in to kernel image. + endmenu endif -- 1.7.9.5 -- 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
