On Tuesday 27 of August 2013 17:43:41 Mike Turquette wrote: > Quoting Padmavathi Venna (2013-08-16 00:49:36) > > > From: Andrew Bresticker <abrestic@xxxxxxxxxxxx> > > > > Different Exynos SoCs have different names for certain input clocks > > to the AudioSS block. Since the order in which clock providers are > > probed is not guaranteed, we can't use the device-tree to pass the > > correct input clocks. > > Why not? Could your audss binding include something like a "clocks" > property with phandles to the input clocks? Then your audss clock driver > could just use clk_get like a regular driver to get the parents. AFAIR, the driver is currently probed using of_clk_init(), so the reason was probably being unable to defer probing. However this is not the core system clock controller, so I believe there is no reason for it not to be a normal platform driver. Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
