On Thu, Jan 19, 2012 at 18:39:26, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [120118 06:18]:
> > On Wed, Jan 18, 2012 at 02:45:36PM +0000, Marc Zyngier wrote:
> > > Can't you instead use the ARM sched_clock framework?
> >
> > OMAP does, and has done for quite some time. The problem is these
> > patches are against an old kernel.
>
> Additionally we're already handling the 32k timer or not case already
> on omap1 as it does not exist on 1510, so there should only minimal
> patching needed AFAIK.
>
Tony,
All this is handled using cpu_is_omapxxxx() checks, something like,
int __init omap_init_clocksource_32k(void) {
...
if (cpu_is_omap16xx() || cpu_class_is_omap2()) {
...
...
...
}
}
This will not help for omap2/3+ devices.
I have cleaned up the code and about to submit it, please review
it and provide the comments.
Submitting shortly...
Thanks,
Vaibhav
> Tony
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
