From: Rajendra Nayak <rnayak@ti.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: Nishanth Menon <nm@ti.com>, Tony Lindgren <tony@atomide.com>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Kevin Hilman <khilman@deeprootsystems.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data
Date: Thu, 25 Apr 2013 12:31:22 +0530 [thread overview]
Message-ID: <5178D4C2.7080400@ti.com> (raw)
In-Reply-To: <20130424162847.8998.73264@quantum>
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 of_clk_add_provider
>> to the device node to be accessible by of_clk_get.
>>
>> Based on discussion contributions from Roger Quadros, Grygorii Strashko
>> and others.
>>
>> Cc: Kevin Hilman <khilman@deeprootsystems.com>
>> Cc: Mike Turquette <mturquette@linaro.org>
>> Cc: Paul Walmsley <paul@pwsan.com>
>> [tony@atomide.com: co-developed]
>> Signed-off-by: Tony Lindgren <tony@atomide.com>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>
> I can take this into clk-next after the merge window. Please refresh it
> for -rc1 as we discussed on irc.
>
> As an aside, will Tero's series for migrating to drivers/clk/omap[1] and
> Rajendra's patch for registering clocks late[2] be refreshed after the
[2] is already in mainline.
> merge window? It would be nice to combine these efforts.
>
> Thanks,
> Mike
>
> [1] http://article.gmane.org/gmane.linux.ports.arm.omap/95948
> [2] http://www.spinics.net/lists/arm-kernel/msg231288.html
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data
Date: Thu, 25 Apr 2013 12:31:22 +0530 [thread overview]
Message-ID: <5178D4C2.7080400@ti.com> (raw)
In-Reply-To: <20130424162847.8998.73264@quantum>
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 of_clk_add_provider
>> to the device node to be accessible by of_clk_get.
>>
>> Based on discussion contributions from Roger Quadros, Grygorii Strashko
>> and others.
>>
>> Cc: Kevin Hilman <khilman@deeprootsystems.com>
>> Cc: Mike Turquette <mturquette@linaro.org>
>> Cc: Paul Walmsley <paul@pwsan.com>
>> [tony at atomide.com: co-developed]
>> Signed-off-by: Tony Lindgren <tony@atomide.com>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>
> I can take this into clk-next after the merge window. Please refresh it
> for -rc1 as we discussed on irc.
>
> As an aside, will Tero's series for migrating to drivers/clk/omap[1] and
> Rajendra's patch for registering clocks late[2] be refreshed after the
[2] is already in mainline.
> merge window? It would be nice to combine these efforts.
>
> Thanks,
> Mike
>
> [1] http://article.gmane.org/gmane.linux.ports.arm.omap/95948
> [2] http://www.spinics.net/lists/arm-kernel/msg231288.html
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
WARNING: multiple messages have this Message-ID (diff)
From: Rajendra Nayak <rnayak@ti.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: Nishanth Menon <nm@ti.com>, Tony Lindgren <tony@atomide.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data
Date: Thu, 25 Apr 2013 12:31:22 +0530 [thread overview]
Message-ID: <5178D4C2.7080400@ti.com> (raw)
In-Reply-To: <20130424162847.8998.73264@quantum>
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 of_clk_add_provider
>> to the device node to be accessible by of_clk_get.
>>
>> Based on discussion contributions from Roger Quadros, Grygorii Strashko
>> and others.
>>
>> Cc: Kevin Hilman <khilman@deeprootsystems.com>
>> Cc: Mike Turquette <mturquette@linaro.org>
>> Cc: Paul Walmsley <paul@pwsan.com>
>> [tony@atomide.com: co-developed]
>> Signed-off-by: Tony Lindgren <tony@atomide.com>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>
> I can take this into clk-next after the merge window. Please refresh it
> for -rc1 as we discussed on irc.
>
> As an aside, will Tero's series for migrating to drivers/clk/omap[1] and
> Rajendra's patch for registering clocks late[2] be refreshed after the
[2] is already in mainline.
> merge window? It would be nice to combine these efforts.
>
> Thanks,
> Mike
>
> [1] http://article.gmane.org/gmane.linux.ports.arm.omap/95948
> [2] http://www.spinics.net/lists/arm-kernel/msg231288.html
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
next prev parent reply other threads:[~2013-04-25 7:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 22:54 [PATCH V4 0/6] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
[not found] ` <1365807278-554-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2013-04-12 22:54 ` [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 23:31 ` Tony Lindgren
2013-04-12 23:31 ` Tony Lindgren
[not found] ` <20130412233142.GE10155-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-04-12 23:39 ` Nishanth Menon
2013-04-12 23:39 ` Nishanth Menon
2013-04-12 23:39 ` Nishanth Menon
2013-04-13 17:22 ` Tony Lindgren
2013-04-13 17:22 ` Tony Lindgren
[not found] ` <20130413172210.GM10155-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-04-14 21:19 ` Nishanth Menon
2013-04-14 21:19 ` Nishanth Menon
2013-04-14 21:19 ` Nishanth Menon
2013-04-24 16:28 ` Mike Turquette
2013-04-24 16:28 ` Mike Turquette
2013-04-25 7:01 ` Rajendra Nayak [this message]
2013-04-25 7:01 ` Rajendra Nayak
2013-04-25 7:01 ` Rajendra Nayak
2013-04-15 16:22 ` Stephen Warren
2013-04-15 16:22 ` Stephen Warren
2013-04-15 18:43 ` Nishanth Menon
2013-04-15 18:43 ` Nishanth Menon
2013-04-12 22:54 ` [PATCH V4 3/6] ARM: dts: OMAP4: add clock nodes for CPU Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` [PATCH V4 2/6] ARM: dts: OMAP3: " Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` [PATCH V4 4/6] ARM: dts: AM33XX: " Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` [PATCH V4 5/6] ARM: OMAP2+: AM33XX: add lateinit hook for calling pm late init Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` [PATCH V4 6/6] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5178D4C2.7080400@ti.com \
--to=rnayak@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.