From: Jan Kiszka <jan.kiszka@domain.hid>
To: Tomas Kalibera <kalibera@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Loosing serial interrupt
Date: Tue, 06 May 2008 08:52:56 +0200 [thread overview]
Message-ID: <48200048.7010604@domain.hid> (raw)
In-Reply-To: <481F9B32.9060003@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Tomas Kalibera wrote:
> Hi Jan,
>> Try to pass I_EDGE to rt_intr_create. The UART IRQs are edge-triggered,
>> so you have to enable the appropriate handling at kernel IRQ handler
>> level.
>>
>> Jan
>>
>
> I'm calling rt_intr_create from user space, so I cannot specify I_EDGE.
> But even if I could, looking at the code I assumed that I_EDGE was only
> applicable together with I_SHARED, and should be only used when I need
> to share and edge IRQ among multiple rt_intr objects/interrupt
> handlers. Is that correct ?
Yeah, that was nonsense. It's a shared-IRQ thing, and those won't work
via the native API anyway.
If you can identify a point when something interesting just happened
(which means much less than 10 seconds ago), try placing a
xntrace_user_freeze() at that location and use the I-pipe tracer to
analyse the history of the system (of the last few milliseconds). That
can help to understand what does or does not go on at lower levels. Find
more infos on the tracer in the wiki.
BTW, there is also a test case available for IRQ delivery via
null-modem, check irqbench. It doesn't use the rt_intr API, but the same
hardware.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]
next prev parent reply other threads:[~2008-05-06 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 20:22 [Xenomai-help] Loosing serial interrupt Tomas Kalibera
2008-05-05 22:21 ` Jan Kiszka
2008-05-05 22:46 ` Karch, Joshua
2008-05-05 23:22 ` Tomas Kalibera
2008-05-05 23:41 ` Tomas Kalibera
2008-05-06 6:52 ` Jan Kiszka [this message]
2008-05-06 16:29 ` Tomas Kalibera
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=48200048.7010604@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=kalibera@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.