Re: [PATCHv4 02/33] clk: omap: introduce clock driver

2013-08-01 Thread Nishanth Menon
On 07/31/2013 03:59 AM, Tero Kristo wrote: On 07/30/2013 06:21 PM, Nishanth Menon wrote: On 07/23/2013 02:19 AM, Tero Kristo wrote: Parses OMAP clock data from DT and registers those clocks with the clock framework. dt_omap_clk_init must be called early during boot for timer initialization so

Re: [PATCHv4 02/33] clk: omap: introduce clock driver

2013-08-01 Thread Tero Kristo
On 08/01/2013 04:44 PM, Nishanth Menon wrote: On 07/31/2013 03:59 AM, Tero Kristo wrote: On 07/30/2013 06:21 PM, Nishanth Menon wrote: On 07/23/2013 02:19 AM, Tero Kristo wrote: Parses OMAP clock data from DT and registers those clocks with the clock framework. dt_omap_clk_init must be

Re: [PATCHv4 02/33] clk: omap: introduce clock driver

2013-07-31 Thread Tero Kristo
On 07/30/2013 06:21 PM, Nishanth Menon wrote: On 07/23/2013 02:19 AM, Tero Kristo wrote: Parses OMAP clock data from DT and registers those clocks with the clock framework. dt_omap_clk_init must be called early during boot for timer initialization so it is exported and called from the existing

Re: [PATCHv4 02/33] clk: omap: introduce clock driver

2013-07-30 Thread Nishanth Menon
On 07/23/2013 02:19 AM, Tero Kristo wrote: Parses OMAP clock data from DT and registers those clocks with the clock framework. dt_omap_clk_init must be called early during boot for timer initialization so it is exported and called from the existing clock code instead of probing like a real

[PATCHv4 02/33] clk: omap: introduce clock driver

2013-07-23 Thread Tero Kristo
Parses OMAP clock data from DT and registers those clocks with the clock framework. dt_omap_clk_init must be called early during boot for timer initialization so it is exported and called from the existing clock code instead of probing like a real driver. Based on initial work done by Mike