On Wednesday 31 January 2007 2:47 pm, Daniel Walker wrote: > 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. ... > > > > So don't assume any platform doesn't use clocksource initcalls. > > What does your OMAP clocksource do now ?
OMAP being one family of ARMs ... well, maybe a few families under the same branding umbrella. > I thought one of the changes > that you made was to have both 32k and mpu both registered .. Some OMAP1 chips will do that, if the MPU timer is configured *AND* they have that 32K counter register. Not OMAP2 (which doesn't have MPU timers), and not the older OMAP1 chips (no 32K counter). It turned out to be simpler to do it that way. Otherwise the configuration options get too confusing. There are three types of timer (MPU timers on most OMAP1 systems, 32K timer on some, dual mode timers on newer chips including OMAP2) that can generate ticks. In some cases, another of those timers wil also be used in free run mode as a clocksource. That 32K counter isn't a timer, but it's a fine clocksource (if present). But until clockevents go upstream, it's kind of pointless to factor it all differently. - Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
