Re: [PATCH 14/23] clocksource: increase initcall priority
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Date: Wed, 31 Jan 2007 14:47:09 -0800
On Wed, 2007-01-31 at 11:43 -0800, David Brownell wrote:
As a note, arm and mips both register their clocksources during
time_init() instead of using initcalls.
That's actually platform-specific. If there's only one possible
clocksource, that'd be the normal answer.
Otherwise, there can be multiple clocksources just like any other
architecture. Maybe there's an always-present 32 KHz counter, and
a bank of timers that can run at higher frequences ... but those
may not be available for timekeeping on all boards, maybe because
they're used for something else (motor control, etc) or because the
system has prioritized battery life over timestamp precision.
So don't assume any platform doesn't use clocksource initcalls.
What does your OMAP clocksource do now ? I thought one of the changes
that you made was to have both 32k and mpu both registered ..
Daniel
-
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/
- References:
- Re: [PATCH 14/23] clocksource: increase initcall priority
- From: David Brownell
- Re: [PATCH 14/23] clocksource: increase initcall priority
- Prev by Date: [PATCH] rapidio: fix multi-switch enumeration
- Previous by thread: Re: [PATCH 14/23] clocksource: increase initcall priority
- Next by thread: 2.6.20-rc7 mtrr handling
- Index(es):
Relevant Pages
|