From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org, bob.feretich@domain.hid
Subject: Re: [Xenomai-help] Having trouble with a BeagleBoard GPIO interrupt pin
Date: Mon, 09 Aug 2010 15:37:05 +0200 [thread overview]
Message-ID: <1281361025.1706.143.camel@domain.hid> (raw)
In-Reply-To: <4C5FEB8C.200@domain.hid>
On Mon, 2010-08-09 at 13:50 +0200, Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > On Mon, 2010-08-09 at 02:54 -0700, Bob Feretich wrote:
> >> I am converting my second driver to RTDM. This one receives a
> >> negativing going edge triggered interrupt on GPIO133 of the OMAP3
> >> chip.
> >>
> >> I have...
> >> ret = rtdm_irq_request(&adis_data_rdy_irq_handle, irq,
> >> adis_data_rdy_irq_handler,
> >> RTDM_IRQTYPE_EDGE,
> >> "asuspidvr", ctx);
> >> then...
> >> ret = rtdm_irq_enable(&adis_data_rdy_irq_handle);
> >>
> >> but the interrupt handler is never invoked.
> >>
> >> cat /proc/xenomai/irq shows:
> >> IRQ CPU0
> >> 37: 15815 [timer]
> >> 39: 0 asuspidvr
> >> 48: 0 asuspidvr
> >> 91: 0 asuspidvr
> >> 293: 0 asuspidvr
> >> 418: 0 [virtual]
> >>
> >> IRQ 293 in the interrupt that should be happening.
> >>
> >> I can see the pulses on the input pin and the non-rt version of the
> >> driver sees the interrupts, so that excludes hardware issues and
> >> u-boot pin configuration issues.
> >>
> >> Any suggestions?
> >> Regards,
> >> Bob Feretich
> >>
> >>
> >> __
> >
> > For some reason, that IRQ line may not be properly enabled by the core
> > code. Could you introduce this patch? If a valid routine is reported in
> > the kernel log message, you could locate it by address, from a kernel
> > image objdump.
>
> There may also be more to do than enabling the irq line, such as
> programming the hardware to enable irq for this gpio, set the type
> (edge, level) and so on. You can try and call request_irq, then free_irq
> before calling rtdm_request_irq to see if request_irq would trigger some
> actions that rtdm_request_irq does not trigger.
>
If you mean that beagle_twl_gpio_setup() still has to be called at this
point, then we probably have something broken at ipipe level.
--
Philippe.
next prev parent reply other threads:[~2010-08-09 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 9:54 [Xenomai-help] Having trouble with a BeagleBoard GPIO interrupt pin Bob Feretich
2010-08-09 10:34 ` Philippe Gerum
2010-08-09 11:50 ` Gilles Chanteperdrix
2010-08-09 13:27 ` Philippe Gerum
2010-08-09 13:37 ` Philippe Gerum [this message]
2010-08-09 14:08 ` Gilles Chanteperdrix
2010-08-09 17:19 ` Gilles Chanteperdrix
2010-08-10 5:35 ` [Xenomai-core] " Philippe Gerum
2010-08-10 6:22 ` Bob Feretich
2010-08-10 6:43 ` [Xenomai-core] " Philippe Gerum
2010-08-10 7:18 ` Bob Feretich
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=1281361025.1706.143.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=bob.feretich@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--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.