Hello, On Thu, 14 Apr 2016 21:19:54 +0200, Geert Uytterhoeven wrote: > From my experience with clock drivers for Renesas SoCs, life is much easier > when handling all of this (clock names, parents, ...) in C. The same is true > BTW for PM Domains. > > The clock controllers of r8a7791 and r8a7795 are very similar, and could > be handled similarly. > Compare the DT hierarchy for CPG and MSTP/MSSR in > arch/arm/boot/dts/r8a7791.dtsi and arch/arm64/boot/dts/renesas/r8a7795.dtsi. Thanks for your feedback. However in practice, there will ultimately be two instances of this clock controller, as some variants of the SoC will contain two CP parts. Due to this, it is going to be quite convenient to have the clock names configurable from the DT, as I will be able to give the same clock on the master CP and the slave CP a different name. That's actually why my binding documentation uses names like "cpm-<foo>" for all the clocks, where "cpm" stands for "CP Master". In the future, another instance will have clocks named "cps-<foo>" for "CP Slave". Best regards, 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 devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
