From mboxrd@z Thu Jan 1 00:00:00 1970 From: santosh.shilimkar@ti.com (Santosh Shilimkar) Date: Mon, 21 Jan 2013 13:44:15 +0530 Subject: [PATCH 07/10] ARM: OMAP5: clock data: Add OMAP54XX full clock tree and headers In-Reply-To: <20130118171912.GD15361@atomide.com> References: <1358522856-12180-1-git-send-email-santosh.shilimkar@ti.com> <1358522856-12180-8-git-send-email-santosh.shilimkar@ti.com> <20130118171912.GD15361@atomide.com> Message-ID: <50FCF8D7.1010609@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Friday 18 January 2013 10:49 PM, Tony Lindgren wrote: > * Santosh Shilimkar [130118 07:30]: >> From: Rajendra Nayak >> >> Add the clock tree related data for OMAP54xx platforms. >> >> Cc: Paul Walmsley >> >> Signed-off-by: Rajendra Nayak >> Signed-off-by: Benoit Cousson >> [santosh.shilimkar at ti.com: Generated es2.0 data] >> Signed-off-by: Santosh Shilimkar >> --- >> 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. Regards, Santosh