From: David Brownell <david-b@pacbell.net>
To: Bosko Radivojevic <bosko.radivojevic@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: High resolution timers on AT91SAM926x
Date: Sat, 1 Mar 2008 14:57:40 -0800 [thread overview]
Message-ID: <200803011457.40857.david-b@pacbell.net> (raw)
> Is there a way to enable high resolution timers on AT91SAM926x?
Update PIT to support the clocksource/clockevent framework:
http://marc.info/?l=linux-arm-kernel&m=119940724711435&w=2
Declare timer/counter block platform devices:
http://marc.info/?l=linux-arm-kernel&m=120302318811110&w=2
Use timer/counter blocks for better clocksource and clockevents:
http://marc.info/?l=linux-kernel&m=120373043520279&w=2
http://marc.info/?l=linux-kernel&m=120373063320487&w=2
The focus in that last patch is on NO_HZ support -- so the
clockevents run at 32 KiHz (about 31 usec precision for HRT)
to allow overall HZ to run below 1 where practical. If you
need even higher precision, you could update that clockevent
code to use a different base clock.
Those last two patches are in some MM tree, and Haavard has
some updates to then (which don't much affect functionality).
I understand the upcoming 2.6.24-at91 patch will include the
first two patches.
- Dave
next reply other threads:[~2008-03-01 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 22:57 David Brownell [this message]
2008-03-03 10:26 ` High resolution timers on AT91SAM926x Bosko Radivojevic
2008-03-03 18:39 ` David Brownell
2008-03-03 21:42 ` Bosko Radivojevic
2008-03-04 1:29 ` David Brownell
2008-03-04 20:22 ` Remy Bohmer
2008-03-04 20:55 ` Wolfgang Grandegger
[not found] <d6c8ef150803010952g666118dfu7679593b3c92c8be@mail.gmail.com>
2008-03-01 17:59 ` Bosko Radivojevic
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=200803011457.40857.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=bosko.radivojevic@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).