LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Bosko Radivojevic" <bosko.radivojevic@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: High resolution timers on AT91SAM926x
Date: Sat, 1 Mar 2008 18:59:48 +0100	[thread overview]
Message-ID: <d6c8ef150803010959t2f82e12q12c182e698d165fe@mail.gmail.com> (raw)
In-Reply-To: <d6c8ef150803010952g666118dfu7679593b3c92c8be@mail.gmail.com>

Hi!

 Is there a way to enable high resolution timers on AT91SAM926x? The
best resolution I can get (kernel 2.6.23.11-rt14 with at91 patch from
maxim.org.za) is around 1ms. Is there any other way to get timers with
better resolution?

When I enable CONFIG_GENERIC_TIME and CONFIG_GENERIC_CLOCKEVENTS (as
prerequisites for CONFIG_HIGH_RES) I'm unable to compile at91 part of
kernel.

Is there any "unofficial" patch? I saw that in 2.6.24 high res is
supported for ARM, but AT91 still lacks support.


$ cat /proc/timer_list
Timer List Version: v0.3
HRTIMER_MAX_CLOCK_BASES: 2
now at 11995813000 nsecs

cpu: 0
 clock 0:
  .index:      0
  .resolution: 999961 nsecs
  .get_time:   ktime_get_real
 active timers:
 clock 1:
  .index:      1
  .resolution: 999961 nsecs
  .get_time:   ktime_get
active timers:
 #0: <c388de9c>, it_real_fn, S:01
 # expires at 1207195374000 nsecs [in 1195199561000 nsecs]

Thanks!

       reply	other threads:[~2008-03-01 17:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d6c8ef150803010952g666118dfu7679593b3c92c8be@mail.gmail.com>
2008-03-01 17:59 ` Bosko Radivojevic [this message]
2008-03-01 22:57 David Brownell
2008-03-03 10:26 ` 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

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=d6c8ef150803010959t2f82e12q12c182e698d165fe@mail.gmail.com \
    --to=bosko.radivojevic@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: High resolution timers on AT91SAM926x' \
    /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

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).