From: Detlef Vollmann <dv@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai@xenomai.org
Subject: Re: [Xenomai-core] Some questions about the ARM port (Integrator vs. PXA)
Date: Tue, 04 Jul 2006 08:43:45 +0200 [thread overview]
Message-ID: <44AA0E21.3F17401F@vollmann.ch> (raw)
In-Reply-To: 17577.5372.702355.432641@domain.hid
Gilles Chanteperdrix wrote:
> You can even do this in __ipipe_mach_set_dec, this avoid the need to
> modify I-ipipe non-machine specific code. Something like:
>
> void __ipipe_mach_set_dec(unsigned long delay)
> {
> if (delay < 8)
> ipipe_trigger_irq(__ipipe_mach_timerint);
> else
> OSMR0 = OSCR + delay;
> }
Thanks, ipipe_trigger_irq() is exactly what I was looking for.
I'll just add another test after the update of OSMR0 for the
case that we got interrupted between the comparison and the
assignment. And in that (probably very rare) case I accept that
I loose a timer tick :-(
Also, this way the timer comes a bit early, so any handler that
checks the TSC might think that this is the wrong interrupt --
and wait forever for the correct one.
But the only other option would be the busy wait...
The question about recursion remains:
If a domain decides in its timer interrupt handler to reprogram
the timer by calling __ipipe_mach_set_dec() (indirectly), and
we already are too close to the next match, then that interrupt
handler is called recursively.
Is every ipipe domain expected to cope with this?
Detlef Vollmann
--
Detlef Vollmann vollmann engineering gmbh
Linux and C++ for Embedded Systems http://www.vollmann.ch/
Linux for PXA270 Colibri module: http://www.vollmann.ch/en/colibri/
next prev parent reply other threads:[~2006-07-04 6:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 8:38 [Xenomai-core] Some questions about the ARM port (Integrator vs. PXA) Detlef Vollmann
2006-06-29 14:46 ` Stelian Pop
2006-06-30 6:31 ` Detlef Vollmann
[not found] ` <44A4C4CB.5F24DA68@domain.hid>
2006-06-30 8:53 ` Stelian Pop
2006-07-03 5:56 ` Detlef Vollmann
2006-07-03 6:33 ` Jan Kiszka
2006-07-03 8:38 ` Detlef Vollmann
2006-07-03 9:37 ` Jan Kiszka
2006-07-03 12:39 ` Gilles Chanteperdrix
2006-07-03 13:00 ` Gilles Chanteperdrix
2006-07-04 6:43 ` Detlef Vollmann [this message]
2006-07-04 14:09 ` Jan Kiszka
2006-07-05 22:32 ` Detlef Vollmann
2006-07-05 22:42 ` Detlef Vollmann
2006-07-05 13:03 ` Gilles Chanteperdrix
2006-07-05 23:44 ` Detlef Vollmann
2006-07-06 7:15 ` Jan Kiszka
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=44AA0E21.3F17401F@vollmann.ch \
--to=dv@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@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.