From: Scott Wood <scottwood@freescale•com>
To: Rognlien Dag Kristian <Dag.K.Rognlien@sintef•no>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: request_irq() for external interrupt pin on MPC875 (A&M adder MPC 875)
Date: Mon, 28 Jan 2008 11:20:04 -0600 [thread overview]
Message-ID: <479E0EC4.5070707@freescale.com> (raw)
In-Reply-To: <39417DF3286A66428FA558987839F44F03FC914F@SINTEFXCH01.sintef.no>
Rognlien Dag Kristian wrote:
> With kernel 2.6.13 we used
>
> request_irq (use_irq, irq_handler, SA_INTERRUPT|SA_SHIRQ, DEVICE_NAME, dev)
>
> where use_irq is 12 to use the external IRQ6 pin.
>
> We are now trying to get this driver to work with the 2.6.25 pull from
> powerpc.git.
>
> request_irq (use_irq, irq_handler, IRQF_SHARED, DEVICE_NAME, dev);
>
> returns -ENOSYS on the newer kernel.
>
> Have the IRQ mappings for the external IRQX pins been moved in the later
> kernels?
Yes, you need to use the result of irq_create_mapping() or
irq_of_parse_and_map().
-Scott
prev parent reply other threads:[~2008-01-28 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 13:28 request_irq() for external interrupt pin on MPC875 (A&M adder MPC 875) Rognlien Dag Kristian
2008-01-28 17:20 ` Scott Wood [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=479E0EC4.5070707@freescale.com \
--to=scottwood@freescale$(echo .)com \
--cc=Dag.K.Rognlien@sintef$(echo .)no \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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