All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Terry Fryar <terry.fryar@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Interrupt numbers
Date: Fri, 23 Dec 2011 10:45:29 +0100	[thread overview]
Message-ID: <4EF44DB9.9000609@domain.hid> (raw)
In-Reply-To: <56F449AE83D74177BAC5887692E0EF55@domain.hid>

On 12/23/2011 01:38 AM, Terry Fryar wrote:
> Using Xenomai 2.60 with 2.6.38 omap kernel on beagleboard xm.  
>  
> Trying to use a GPIO pin as an interrupt and catch this in a xenomai
> userspace program.  Got the GPIO132 pin set as an input and is working fine.
> I guess I'll need to set the irq enable register on the omap cpu to enable
> it to generate irqs.  Now...what irq number do I use in the xenomai
> rt_intr_create() function call??  I'm not sure how the omap gpio interrupts
> are mapped to the linux kernel/xenomai stuff??  Can I use what's in the
> arch/arm/plat-omap/include/plat/irqs.h header file?  It appears that each
> bank of GPIO pins has it's own interrupt number??

Xenomai uses the same interrupt numbers as linux. But rt_intr_create is
deprecated in user-space, you should instead write a driver using the
rtdm skin. The enable bit is handled by xenomai when you request the irq
at xenomai level.

-- 
					    Gilles.


  reply	other threads:[~2011-12-23  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23  0:38 [Xenomai-help] Interrupt numbers Terry Fryar
2011-12-23  9:45 ` Gilles Chanteperdrix [this message]
2011-12-23 14:04   ` Terry Fryar
2011-12-23 15:26   ` Makarand Pradhan
2011-12-23 15:53     ` Gilles Chanteperdrix
2011-12-23 16:16       ` Terry Fryar
2011-12-23 18:13         ` Philippe Gerum
2011-12-23 23:06           ` Terry Fryar
2012-01-19 19:41           ` Michael Pustylnik
2012-01-19 22:59             ` Philippe Gerum
2011-12-23 16:17       ` Makarand Pradhan

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=4EF44DB9.9000609@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=terry.fryar@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.