Re: [RFC] API for system clocks (oscillators)

[Jonas Bonn]

>
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/