From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: at91_enthus <nwromania@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] I-pipe clock source change and MMC issues (AT91)
Date: Wed, 02 Feb 2011 23:09:12 +0100 [thread overview]
Message-ID: <4D49D608.5020006@domain.hid> (raw)
In-Reply-To: <AANLkTinaTVSJW1jQzn7+jbsQgNE+HAEOXLEK3LC0MoWR@mail.gmail.com>
at91_enthus wrote:
>
>
> On Wed, Feb 2, 2011 at 3:39 PM, Gilles Chanteperdrix
> <gilles.chanteperdrix@xenomai.org
> <mailto:gilles.chanteperdrix@xenomai.org>> wrote:
>
> at91_enthus wrote:
> > Hi.
> >
> > In order to get better accuracy with Xenomai, I modified the I-pipe
> > timebase (MCK divider) in arch/arm.mach-at91/at91_ipipe_time.c.
> > Unfortunately, I cannot mount the rootfs on the MMC, since the MMC
> > controller is no longer functioning. I tried to change TCx in kernel
> > configuration to no avail.
> > When I switch back to a timebase of 1 MHz, the MMC works fine.
>
> The thing is that we are a bit tight on AT91. A 16 bits counter is used
> for both the timer and the tsc emulation, and this tsc must be refreshed
> at least once before it wraps. The problem is that since it is a 16 bits
> counter, it wraps really fast, on my AT91SAM9263 it wraps in 20 ms, and
> since the Linux default period is 10ms we are actually quite close to
> the limit.
>
> Anyway, trying to get a better accuracy than 1us is kind of useless on
> AT91, since even reading this counter takes more than 1us. So, you are
> not in fact improving anything. The 1MHz is even a bit overkill.
On the other hand, the AT91SAM9G20 may be running at a better frequency.
But with latencies in the order of tens of microseconds, having a better
accuracy than 1us still does not make really much sense. Why do you need
this accuracy?
--
Gilles.
next prev parent reply other threads:[~2011-02-02 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 20:51 [Xenomai-help] I-pipe clock source change and MMC issues (AT91) at91_enthus
2011-02-02 21:39 ` Gilles Chanteperdrix
2011-02-02 22:00 ` at91_enthus
2011-02-02 22:09 ` Gilles Chanteperdrix [this message]
2011-02-02 22:22 ` at91_enthus
2011-02-03 10:18 ` Gilles Chanteperdrix
2011-02-03 10:28 ` Gilles Chanteperdrix
2011-02-04 4:24 ` at91_enthus
2011-02-04 22:34 ` Gilles Chanteperdrix
2011-02-05 0:23 ` at91_enthus
2011-02-05 15:39 ` Gilles Chanteperdrix
2011-02-05 17:26 ` at91_enthus
2011-02-05 17:40 ` Gilles Chanteperdrix
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=4D49D608.5020006@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=nwromania@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.