[patch 00/16] arm: Replace arm sched_clock by clocksource based sched_clock

Tony Lindgren tony at atomide.com
Tue Apr 26 04:50:54 EDT 2011

* Linus Walleij <linus.walleij at linaro.org> [110426 10:41]:
> 2011/4/25 john stultz <johnstul at us.ibm.com>:
> > On Sun, 2011-04-24 at 09:27 +0200, Linus Walleij wrote:
> >> Any reason why we can't simply move *all* of these to
> >> drivers/clocksource/* and proceed with consolidation there?
> >
> > This gives me some pause, as having the clocksources in the platform
> > code makes it easier to know what platform needs to be tested when a
> > change is made. The rule so far has been if more then one arch can make
> > use of it, it should be moved to the drivers/clocksource dir. Otherwise,
> > leave it close to any arch specific code that manages the hardware.
> That means that by definition anything in a plat-* directory, say e.g.
> plat-nomadik/timer.c and plat-omap/dmtimer.c should go into
> drivers/clocksource I believe?

Or drivers/timers as they may be generic hardware timers? They are
not necessarily used for clocksource.



More information about the linux-arm-kernel mailing list