From: Gary Thomas <gary@mlbassoc.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Hooking an IRQ on a modified mpc8349emitx board
Date: Thu, 04 Sep 2008 09:21:33 -0600 [thread overview]
Message-ID: <48BFFCFD.8010608@mlbassoc.com> (raw)
In-Reply-To: <20080904144457.GA2522@ld0162-tx32.am.freescale.net>
Scott Wood wrote:
> On Wed, Sep 03, 2008 at 03:55:41PM -0700, Oscar Takeshita wrote:
>> I've been trying to hook an IRQ on a modified mpc8349emitx board without
>> success.
>>
>> The IRQ is hooked physically to IRQ1/GPIO2[13] on the mpc8349e. No other
>> devices are
>> tied to this pin.
>>
>> I'm using uboot 1.2.0 and kernel 2.6.22.19.
>>
>> Do I need to have a dts entry for this interrupt in order to make
>> request_irq() succeed?
>>
>> How can I find the IRQ number? I tried probe_irq_on/off unfortunately it
>> did not work.
>> Would it be MPC83xx_IRQ_EXT1 in arch/powerpc/include/asm/mpc83xx.h ?
>>
>> I'm new doing kernel work. Any hints appreciated.
>
> You need to describe the IRQ in a device tree node and use
> irq_of_parse_and_map(). request_irq() takes virtual IRQ numbers.
>
> Maybe we should put together an arch/powerpc FAQ...
That would be wonderful :-) This could help many [of us] over these
initial speed-bumps.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2008-09-04 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 22:55 Hooking an IRQ on a modified mpc8349emitx board Oscar Takeshita
2008-09-04 14:44 ` Scott Wood
2008-09-04 15:21 ` Gary Thomas [this message]
2008-09-04 18:44 ` Oscar Takeshita
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=48BFFCFD.8010608@mlbassoc.com \
--to=gary@mlbassoc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).