From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: ti: change clock init to use generic of_clk_init
Date: Mon, 22 Sep 2014 10:55:32 +0300 [thread overview]
Message-ID: <541FD5F4.6020909@ti.com> (raw)
In-Reply-To: <541FC714.9050203@ti.com>
On 09/22/2014 09:52 AM, Tero Kristo wrote:
> On 09/19/2014 07:33 PM, Paul Walmsley wrote:
>> On Thu, 18 Sep 2014, Tony Lindgren wrote:
>>
>>> * Tero Kristo <t-kristo@ti.com> [140821 06:52]:
>>>> Previously, the TI clock driver initialized all the clocks
>>>> hierarchically
>>>> under each separate clock provider node. Now, each clock that requires
>>>> IO access will instead check their parent node to find out which IO
>>>> range
>>>> to use.
>>>>
>>>> This patch allows the TI clock driver to use a few new features
>>>> provided
>>>> by the generic of_clk_init, and also allows registration of clock nodes
>>>> outside the clock hierarchy (for example, any external clocks.)
>>>
>>> Paul, any comments on this one?
>>
>> Not at this point.
>
> Tony, ok to merge this through clock tree?
Oh btw, this is v1, I posted v2 a week back here:
http://article.gmane.org/gmane.linux.ports.arm.omap/118551
v2 has the retry init logic fixed in it (mainly for DPLLs which can have
two separate parents which of both must be available during init.)
-Tero
next prev parent reply other threads:[~2014-09-22 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 13:49 [PATCH] clk: ti: change clock init to use generic of_clk_init Tero Kristo
2014-08-27 15:15 ` Jyri Sarha
2014-09-18 17:17 ` Tony Lindgren
2014-09-19 16:33 ` Paul Walmsley
2014-09-22 6:52 ` Tero Kristo
2014-09-22 7:55 ` Tero Kristo [this message]
2014-09-23 15:49 ` Tony Lindgren
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=541FD5F4.6020909@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).