Hi Thomas,
On 11/27/2012 01:34 AM, Thomas Petazzoni wrote:
On Fri, 16 Nov 2012 14:47:24 +1000, gerg@xxxxxxxxxxxx wrote:
The current Coldfire clock code only really supports those ColdFire
CPU types that have the more advanced enable/disable clock hardware
support. If we generalize our clock code we can support all types,
even those with simpler fixed clock trees.
This results in much cleaner and consistent clock support. And it
means that we can in the future use the clock API in our timers and
throughout the other ColdFire p[eripheraps, instead of hard coded
clock definitions.
Have you considered instead using the generic clock framework that is
now in drivers/clk/ ?
I have, and that is what I plan to do next. This set of patches
was intended to clean up (and generalize) what we currently have.
It doesn't really change the current ColdFire clocking code in
any way, just makes it work consistently across all CPU types.
Regards
Greg
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@xxxxxxxxxxxx
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
