Jan Kiszka wrote:
> It's this piece of code always running under IRQ-lock?
No. ipipe_tune_timer() is a public ipipe interface and can
be called from everywhere.
> The IRQ is marked pending for the receiving domain if
> ipipe_trigger_irq() is called when that domain is stalled - and that
> should always be the case for ipipe_mach_set_dec(), at least when called
> from the timer handler. The timer IRQ will then be handled once the
> stall is removed again (on handler return e.g.).
Thanks for the explanation.
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/
Xenomai-core mailing list