From: Philippe Gerum <rpm@xenomai.org>
To: Mike McTernan <mmcternan@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] IRQ reservation and config
Date: Thu, 05 Feb 2009 17:25:08 +0100 [thread overview]
Message-ID: <498B12E4.6010001@domain.hid> (raw)
In-Reply-To: <4B3F8896E1733D4787DDB0EA1C7FF91F704346@domain.hid>
Mike McTernan wrote:
>> Mike McTernan wrote:
>>> Hi,
>>>
>>> Right - I want the interrupt to be handled in realtime.
>>>
>>> Is there a way to configure the interrupt as level sensitive under
>>> Xenomai? I can't see how to do it, hence the thought of using
>>> request_irq(), which can do that.
>>>
>> rtdm_irq_request() assumes that the platform-dependent code did set
> the
>> correct IRQ type/sense already.
>
> Cool. So I think you are saying it is valid to first request_irq() to
> setup and config the interrupt, then hook it with rtdm_irq_request() for
> the realtime handler afterwards.
>
Yes; the IRQ could even be freed right away, since you only want request_irq()
to set the IRQ sense, and free_irq() won't undo anything.
> I was unsure about mixing calls to the rtdm with the normal APIs, but it
> sounds like in this case it is not a problem and the recommended method.
>
I would say that the recommended method is rather to have the BSP code do
whatever is needed to set the damn thing properly, but if it does not, plan B
may be to count on request_irq() to call the set_type() callback of the related
interrupt chip for the IRQ in question. That should work (Famous Last Words).
> Many Thanks,
>
> Mike
>
>
--
Philippe.
prev parent reply other threads:[~2009-02-05 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 17:40 [Xenomai-help] IRQ reservation and config Mike McTernan
2009-02-03 17:46 ` Philippe Gerum
2009-02-03 17:49 ` Mike McTernan
2009-02-05 15:54 ` Philippe Gerum
2009-02-05 16:10 ` Mike McTernan
2009-02-05 16:25 ` Philippe Gerum [this message]
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=498B12E4.6010001@domain.hid \
--to=rpm@xenomai.org \
--cc=mmcternan@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.