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@xxxxxx> [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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
