From: Daniel Walker <dwalker@mvista.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 14/23] clocksource: increase initcall priority
Date: Wed, 31 Jan 2007 14:47:09 -0800 [thread overview]
Message-ID: <1170283629.9781.163.camel@imap.mvista.com> (raw)
In-Reply-To: <20070131194311.4B8381FD833@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
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
next prev parent reply other threads:[~2007-01-31 22:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 19:43 David Brownell
2007-01-31 22:47 ` Daniel Walker [this message]
2007-01-31 23:23 ` Thomas Gleixner
2007-02-01 0:15 ` Daniel Walker
2007-02-01 0:34 ` Thomas Gleixner
2007-02-01 0:24 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2007-01-31 3:37 [PATCH 00/23] clocksource update v12 Daniel Walker
2007-01-31 3:37 ` [PATCH 14/23] clocksource: increase initcall priority Daniel Walker
2007-01-31 11:50 ` Ingo Molnar
2007-01-31 16:42 ` Daniel Walker
2007-01-31 17:10 ` Ingo Molnar
2007-01-31 17:20 ` Daniel Walker
2007-01-31 17:29 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1170283629.9781.163.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®