[PATCH RFC] clk: add support for automatic parent handling
benh at kernel.crashing.org
Sat Apr 23 19:34:20 EDT 2011
On Fri, 2011-04-22 at 17:48 -0700, Saravana Kannan wrote:
> They are completely independent. No synchronization is needed between
> these clock trees. It's basically a bunch of clocks controlled by
> another processor that has it's own set of PLLs, etc.
In fact the common struct clk work that Jeremy picked up from initial
patches I did for powerpc was intended for just that ... ie by moving
the implementation out to have the clock "provider" being the one
creating the clock objects.
There's many other similar cases, ie, you can have a multifunction
device (wifi + bt + mmc reader for example) which has its own internal
clock network and might want to use struct clk to handle clocks between
None of that should sit in the arch or platform code.
In fact, with the device-tree, you could completely represent the
binding between those objects without involving any platform code, that
was the original intend and I hope that ARM eventually gets there.
More information about the linux-arm-kernel