* Santosh Shilimkar <santosh.shilimkar@xxxxxx> [130121 00:16]: > On Friday 18 January 2013 10:49 PM, Tony Lindgren wrote: > >* Santosh Shilimkar <santosh.shilimkar@xxxxxx> [130118 07:30]: > >>From: Rajendra Nayak <rnayak@xxxxxx> > >> > >>Add the clock tree related data for OMAP54xx platforms. > >> > >>Cc: Paul Walmsley <paul@xxxxxxxxx> > >> > >>Signed-off-by: Rajendra Nayak <rnayak@xxxxxx> > >>Signed-off-by: Benoit Cousson <b-cousson@xxxxxx> > >>[santosh.shilimkar@xxxxxx: Generated es2.0 data] > >>Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > >>--- > >>As mentioned in the summary, this patch will be updated once the > >>movement of clock data to drivers/clock is clear. > > > >Yes let's first fix up the issues prevent us from moving all the > >cclock*_data.c files to live under drivers/clock/omap. > > > >It seems that fixing this issue boils down to rearranging some > >clock related headers in arch/arm/mach-omap2, and then populating > >some of the clock data dynamically. Or am I missing something? > > > Am not sure of all the dependencies. Since clock data is using the low > level prm/cm APIs, all those needs to be exported some how to move > the data. Paul can comment better on it. It seems that we should be able to export some omap specific functions from drivers/clk/omap for that. Regards, Tony -- 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
