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 <[email protected]> > Cc: Mike Turquette <[email protected]> > Cc: Paul Walmsley <[email protected]> > [[email protected]: co-developed] > Signed-off-by: Tony Lindgren <[email protected]> > Signed-off-by: Nishanth Menon <[email protected]>
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 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
