From: "Schlägl Manfred jun." <manfred.schlaegl@domain.hid>
To: adeos-main@gna.org
Subject: [Adeos-main] Re: Porting to Intel IXP425
Date: Fri, 30 Mar 2007 23:29:23 +0200 [thread overview]
Message-ID: <1175290163.5363.16.camel@domain.hid> (raw)
In-Reply-To: <460D219D.5070302@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
Am Freitag, den 30.03.2007, 16:41 +0200 schrieb Gilles Chanteperdrix:
> Richard Cochran wrote:
> >>The timer is aperiodic (most of the time) when running Xenomai, so
> >>__ipipe_mach_set_dec is called for each timer tick and programs the
> >>timer hardware for the next tick.
> >
> >
> > Okay, so does that mean that I should implement a "one-shot" timer, or
> > are we talking about resetting the periodic timer once in a while?
> >
> > (BTW, in one-shot mode, the IXP425 timer does not do what the Developers
> > Manual, part 252480-006, says that it does!)
>
> Yes, the one shot mode is Xenomai default mode. The implementation of a
> periodic timer over the one-shot timer is already done by the generic
> ARM part of the Adeos patch.
It's better to use a periodic implementation in background, because then
you are able to messure the lost ticks between a timer-interrupt and
programming next timer-event.
Example with 16bit timer:
* Periode: 27000 Ticks
* Timer counts down to zero (Interrupt) & wrap around to 2^16-1
* Reprogramm Timer with new Periode (lost-ticks = 2^16 - timerval)
These lost-ticks should be added to the global time-stamp (returned by
get_tsc) and should mentioned at the linux-gettimeoffset-function also.
Lost-ticks could sum up to a bothering time-error.
- Manfred Schlaegl
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-30 21:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 10:20 [Adeos-main] Porting to Intel IXP425 Richard Cochran
2007-03-30 11:35 ` Sebastian Smolorz
2007-03-30 12:16 ` Gilles Chanteperdrix
2007-03-30 13:51 ` Richard Cochran
2007-03-30 14:05 ` Gilles Chanteperdrix
2007-03-30 14:33 ` Richard Cochran
2007-03-30 14:41 ` Gilles Chanteperdrix
2007-03-30 21:29 ` Schlägl Manfred jun. [this message]
2007-03-31 10:33 ` [Adeos-main] " Gilles Chanteperdrix
2007-03-30 14:55 ` [Adeos-main] " Philippe Gerum
2007-03-30 16:07 ` Richard Cochran
2007-03-30 17:16 ` 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=1175290163.5363.16.camel@domain.hid \
--to=manfred.schlaegl@domain.hid \
--cc=adeos-main@gna.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.