Hi Tomasz, > Well, this is basically how it should be done, but in current state of > clock core I can see a problem: can we really rely on the order of clock > initialization? I mean, we can't defer initialization of particular clock > controller until all external clocks it needs are available, because there > is no probing involved here. Right, we can't. The reason I added the device-tree lookup of input clocks was because Exynos5420 has different names for several of the input clocks to the audio block. We already need a separate compatibility string because of the ADMA clock, so we could just use that to determine the parent clock names. It's not ideal, but it's a workaround for the initialization order issue. Thoughts? Thanks, Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |