Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-25 Thread Rajendra Nayak
On Wednesday 24 April 2013 09:58 PM, Mike Turquette wrote: Quoting Nishanth Menon (2013-04-14 14:19:17) Overall strategy introduced here is simple: a clock node described in device tree blob is used to identify the exact clock provided in the SoC specific data. This is then linked back using

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-24 Thread Mike Turquette
Quoting Nishanth Menon (2013-04-14 14:19:17) Overall strategy introduced here is simple: a clock node described in device tree blob is used to identify the exact clock provided in the SoC specific data. This is then linked back using of_clk_add_provider to the device node to be accessible by

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-15 Thread Stephen Warren
On 04/12/2013 04:54 PM, Nishanth Menon wrote: OMAP clock data is located in arch/arm/mach-omap2/cclockXYZ_data.c. However, this presents an obstacle for using these clock nodes in Device Tree definitions. This is especially true for board specific clocks initially. The fixed clocks are

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-15 Thread Nishanth Menon
On Mon, Apr 15, 2013 at 11:22 AM, Stephen Warren swar...@wwwdotorg.org wrote: On 04/12/2013 04:54 PM, Nishanth Menon wrote: OMAP clock data is located in arch/arm/mach-omap2/cclockXYZ_data.c. However, this presents an obstacle for using these clock nodes in Device Tree definitions. This is

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-14 Thread Nishanth Menon
On 10:22-20130413, Tony Lindgren wrote: * Nishanth Menon n...@ti.com [130412 16:43]: Thanks for checking up. Fixed all of them below, will post part of series again, only if I need to address further comments in other patches.. Thanks it seems that the other ones are ready to go, just

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-13 Thread Tony Lindgren
* Nishanth Menon n...@ti.com [130412 16:43]: Thanks for checking up. Fixed all of them below, will post part of series again, only if I need to address further comments in other patches.. Thanks it seems that the other ones are ready to go, just one more comment below. --- /dev/null +++

[PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-12 Thread Nishanth Menon
OMAP clock data is located in arch/arm/mach-omap2/cclockXYZ_data.c. However, this presents an obstacle for using these clock nodes in Device Tree definitions. This is especially true for board specific clocks initially. The fixed clocks are currently found via clock aliases table. There are many

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-12 Thread Tony Lindgren
* Nishanth Menon n...@ti.com [130412 15:59]: --- /dev/null +++ b/drivers/clk/omap/clk.c +/** + * omap_clk_src_get() - Get OMAP clock from node name when needed + * @clkspec: clkspec argument + * @data:unused + * + * REVISIT: We assume the following: + * 1. omap clock names end with

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-12 Thread Nishanth Menon
On 16:31-20130412, Tony Lindgren wrote: * Nishanth Menon n...@ti.com [130412 15:59]: --- /dev/null +++ b/drivers/clk/omap/clk.c +/** + * omap_clk_src_get() - Get OMAP clock from node name when needed + * @clkspec: clkspec argument + * @data: unused + * + * REVISIT: We