All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: aking_jin <jinxin16897123@163.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] request_irq with xenomai
Date: Fri, 21 Jun 2013 19:02:53 +0200	[thread overview]
Message-ID: <51C4873D.9030000@xenomai.org> (raw)
In-Reply-To: <51C41FD4.9070608@163.com>

On 06/21/2013 11:41 AM, aking_jin wrote:

> Hi,all
>      I've patched the kernel 3.5.7 with xenomai,and xenomai have been 
> enabled. After that, I want to have a  normal gpio interrupt test with 
> normal way using request_irq, found its return value is -/EINVAL,
> Finally found that IRQ_NOREQUEST was set in the irq_desc[irq_number] 
> through debug. could you give me some advice? thanks.
>          the following was the irq_desc of irq_gpio:
> 
>          [   66.087719] irq 10, desc: c1805600, depth: 0, count: 0, 
> unhandled: 0
>          [   66.097903] ->handle_irq():  c0065678, 
> __ipipe_chained_irq+0x0/0x4
>          [   66.104157] ->irq_data.chip(): c052de50, 
> pxa_internal_irq_chip+0x0/0x70
>          [   66.110751] ->action():   (null)
>          [   66.114010]    IRQ_NOPROBE set
>          [   66.117039]  IRQ_NOREQUEST set
>          [   66.120063]   IRQ_NOTHREAD set
> 
> Thank you very much~
> /
> 


I would say you are using the wrong irq number, you are using the irq
number of the parent, multiplexed interrupt, instead of using the
per-gpio irq number (which you should obtain with gpio_to_irq), but this
question is off-topic on this list, since it has nothing to do with xenomai.


-- 
                                                                Gilles.


      reply	other threads:[~2013-06-21 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21  9:41 [Xenomai] request_irq with xenomai aking_jin
2013-06-21 17:02 ` Gilles Chanteperdrix [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=51C4873D.9030000@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jinxin16897123@163.com \
    --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.