On Monday 04 June 2012 07:21 PM, Jon Hunter wrote:
I was infact thinking of moving these files into mach-omap1/ since they
> are now OMAP1 specific. Is your concern coming mainly from the clksel
> structs that you will need to be shared across OMAP1 and OMAP2+?
Yes, especially if we plan to move omap1 to the common clock framework.
> The right thing to do seems like is to move OMAP1 across to COMMON clk
> also and keep the plat clock.h and get rid of plat clock.c completely.
> But for now, I really haven;t looked at OMAP1 migration as all.
Yes that would make sense. Do you have plans to do this or not yet?
At-least my plan for this series was to address only OMAP2+.
--
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
