Messages in this thread | | | Date | Thu, 30 Oct 2008 17:27:30 +0100 | From | "Jonas Bonn" <> | Subject | Re: [RFC] API for system clocks (oscillators) |
| |
> > How does this compare to the framework in linux/include/linux/clk.h? >
clk.h is pretty much just an infrastructure for "storing" clock data and accessors... it does not provide:
i) Constraints on selectable frequencies of active devices ii) Notifiers on frequency change, including changes due to events such as reparenting
These are the big ones that cause headaches. When I want to switch frequency, I have to check elsewhere which devices are active and which frequencies they allow. When a frequency changes, I have to manually make sure that the active devices are notified properly of the change. These are the main things that my document tries to consolidate into one framework. Like I said, I'm not sure it's the right approach, that's why I requested feedback...
/Jonas
| |