Currently we use CK_446X etc to differentiate which clk needs to be registered on which SoC. The following patch series removes that requirement, instead SoC and SoC variants are detected on the fly and only the required clocks are registered in the system. This will help to remove the CK_XYZ macros from the system. Please comment if this is an acceptable approach - at a first glance, it seems to pave way to be capable of being replaced potentially by DT data as well. Grygorii Strashko (2): ARM: OMAP2+: clock: Add omap2_clks_register API ARM: OMAP4: clock: use omap4_clks_register API arch/arm/mach-omap2/clock.c | 36 ++++++++++++++++++++++++++++++ arch/arm/mach-omap2/clock.h | 3 +++ arch/arm/mach-omap2/clock44xx_data.c | 40 ++++++++++++++++++---------------- 3 files changed, 60 insertions(+), 19 deletions(-) -- 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
