[PATCH 1/3] Add a common struct clk
jeremy.kerr at canonical.com
Thu Sep 16 20:24:34 EDT 2010
> I am not sure about the scope of your assumed task, but I would still
> like to bring
> to your notice some points.
> IMHO any clock api that aims to be used by multiple platforms should be generic
> more than this one. Let me explain.
None of my patches change the clock API itself. The clock API is already
in use on ARM (ie, multiple platforms) and seems to work for most cases.
> Clocks that are simply output of MUX'es inherit the rate of the parent
> clock - they do have
> rate yet this API would return 0 (IIRUIC).
The proposed clock infrastructure does not provide implementations for
the clock operation functions (like get_rate, which you're referring to
here). The behaviour of the clocks is dictated by each implementation of
struct clk. For MUXes, the callback for clk->ops.get_rate would be
unsigned long clk_mux_get_rate(struct clk *clk)
- so it just returns the rate of the parent (not 0). However, if the
clock implementation has a reason to return 0, it is free to do so.
> Another scenario could have a source clock parenting more than one
> child clock via
> different MUX'es. It would be nice to be able to set rate of that
> parent clock (after ensuring
> other siblings won't complain) and have some mechanism to notify other
> siblings of the change.
> Or some better solution.
Again, these patches don't change the API itself; if we want to
implement clock-change notifications, that would best be done in a
More information about the linux-arm-kernel