RFC clk: dt: bindings for mux & divider clocks
Get series with b4
b4 am 20130607175254.10233.7661@quantumVersions newest first
- v1 RFC Latest0 of 3 patches 1 replyIn review
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 0/3] clk: dt: bindings for mux & divider clocks
Quoting Shawn Guo (2013-06-06 22:51:31)
Quoted 11 lines
Mike,
Quoted 1 line · Mike Turquette
I am using this code while converting the OMAP4 clock data over to DT
I see these basic clk bindings can be useful for platforms that have a relatively simple clock tree, but I'm a little surprised that you plan to move OMAP4 to it. I'm wondering how many nodes you will have to add to OMAP4 device tree. For imx6q example, it means ~200 nodes addition to device tree, which is obviously a bloating of device tree.
Yes, there was a time when I was firmly against doing such a thing. However I'm not sure it is so bad now. More and more SoCs are going to keep getting merged into the kernel and that just means more and more clock data. Perhaps DT is best suited to handle this bloat. I broke the clock data out into a separate file so that it didn't overwhelm the existing omap4.dtsi.
Either way I marked this series as RFC precisely due to your point. I want feedback on how the OMAP folks feel about this. So far no has has NACKed it ;-)
Regards,
Mike
Quoted 4 lines
Shawn
Quoted 2 lines
and some common boilerplate code can be factored out of several clock drivers if this is merged.