Hello, On Mon, 10 Feb 2014 18:42:59 +0100, Gregory CLEMENT wrote: > Until now the clock providers were initialized in the order found in > the device tree. This led to have the dependencies between the clocks > not respected: children clocks could be initialized before their > parent clocks. > > Instead of forcing each platform to manage its own initialization order, > this patch adds this work inside the framework itself. > > Using the data of the device tree the of_clk_init function now delayed > the initialization of a clock provider if its parent provider was not > ready yet. > > The strict dependency check (all parents of a given clk must be > initialized) was added by Boris BREZILLON > > Signed-off-by: Gregory CLEMENT <gregory.clem...@free-electrons.com> > --- > > Since the v1, I have merged the strict dependency check from Boris. > And of course tested on my Armada 370 and Armada XP based board > > drivers/clk/clk.c | 109 > ++++++++++++++++++++++++++++++++++++++++++++++++++++-- > 1 file changed, 106 insertions(+), 3 deletions(-)
Tested-by: Thomas Petazzoni <thomas.petazz...@free-electrons.com> On the newly proposed Armada 375 platform. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
