From: Michael Ellerman <michael@ellerman.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC5200b external interrupt registration problem
Date: Sat, 10 May 2008 17:30:51 +1000 [thread overview]
Message-ID: <1210404651.22483.2.camel@localhost> (raw)
In-Reply-To: <20080509190218.GA32008@ld0162-tx32.am.freescale.net>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Fri, 2008-05-09 at 14:02 -0500, Scott Wood wrote:
> On Fri, May 09, 2008 at 02:49:04PM -0400, Nick wrote:
> > I am writing a driver to service an interrupt from our fpga. I am calling request_irq in the open
> > function of my driver. The fpga is connected to external interrupt 1. I am using interrupt
> > number 65 in the request_irq but the function is failing.
>
> request_irq takes a virtual IRQ number, not a hardware IRQ number. You
> need to get the virtual IRQ number from irq_of_parse_and_map(), or from
> irq_create_mapping().
>
> This would probably confuse far fewer people if we used pointers in the
> API rather than virtual IRQ numbers...
I'll do the core changes if you fix all the drivers .. ;)
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-10 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 18:49 MPC5200b external interrupt registration problem Nick
2008-05-09 19:02 ` Scott Wood
2008-05-10 7:30 ` Michael Ellerman [this message]
2008-05-12 14:03 ` Grant Likely
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=1210404651.22483.2.camel@localhost \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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.