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@xxxxxxxxxxxxxxxxxxx> >> Cc: Mike Turquette <mturquette@xxxxxxxxxx> >> Cc: Paul Walmsley <paul@xxxxxxxxx> >> [tony@xxxxxxxxxxx: co-developed] >> Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx> >> Signed-off-by: Nishanth Menon <nm@xxxxxx> > > 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@xxxxxxxxxxxxxxxx > https://lists.ozlabs.org/listinfo/devicetree-discuss > -- 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
