From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Terje Frøysa" <Terje.Froysa@sintef.no>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] IRQ155 not handled. Disabling IRQ line
Date: Tue, 2 Dec 2014 11:53:44 +0100 [thread overview]
Message-ID: <20141202105344.GH2076@hermes> (raw)
In-Reply-To: <314E5ECDAA86314791309FA670550F89C9C51AB4@SINTEFEXMBX05.sintef.no>
On Tue, Dec 02, 2014 at 10:20:59AM +0000, Terje Frøysa wrote:
> Thanks Gilles,
>
> The flags are zero (from example code).... should I have used RTDM_IRQTYPE_EDGE ?
>
> err = rtdm_irq_request(&info->gpio_irq, gpio_irq_n, imu_irq_handler, 0, THIS_MODULE->name, NULL);
If the IRQ is of a certain type, you certainly want to pass the
right irq type.
Looking at the code:
- you only get the message after not returning RTDM_IRQ_HANDLED 1000
times, so, if you see the message, it is sure that some code is not
returning RTDM_IRQ_HANDLED, I suggest you check if the interrupt is
shared, and if another handler is not called
- the xenomai core skips reenabling the interrupts in that case, so,
if it gets reenabled, something re-enables it.
Are you sure that you do not register the handler to early, that it
fires because the hardware is not initialized, then gets disabled by
Xenomai core. Then later, your driver performs the hardware
initializations, and re-enables irqs ?
--
Gilles.
next prev parent reply other threads:[~2014-12-02 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 9:28 [Xenomai] IRQ155 not handled. Disabling IRQ line Terje Frøysa
2014-12-02 9:33 ` Gilles Chanteperdrix
2014-12-02 9:51 ` Terje Frøysa
2014-12-02 9:57 ` Gilles Chanteperdrix
2014-12-02 10:20 ` Terje Frøysa
2014-12-02 10:53 ` Gilles Chanteperdrix [this message]
2014-12-02 12:07 ` Terje Frøysa
2014-12-02 12:13 ` Gilles Chanteperdrix
2014-12-02 12:16 ` Terje Frøysa
2014-12-02 12:17 ` 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=20141202105344.GH2076@hermes \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Terje.Froysa@sintef.no \
--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.