From: "S. Fricke" <silvio.fricke@googlemail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: [NEWBIE] Interrupt-problem mpc5200
Date: Tue, 11 Sep 2007 20:28:11 +0200 [thread overview]
Message-ID: <20070911182811.GA3582@sfrouter> (raw)
In-Reply-To: <fa686aa40709110719j26a5bf30uc075253c6d1a6d97@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
Hello,
> >[...]
> > intr = mpc52xx_find_and_map("mpc52xx-pic");
> > if(!intr) {
> > panic(__FILE__ ": mpc52xx-pic - MAP failed");
> > }
> >
> > set_irq_chip(MPC52xx_IRQ2, &my_irq_chip);
>
> You probably don't want to do this (unless you are cascading IRQs to
> custom external hardware). All you should need is the call to
> request_irq() to register your irq handler, and code in your ISR
> handler to clear the interrupt condition.
>
> You do *NOT* want to program the interrupt controller directly. The
> mpc5200 interrupt controller already has a driver. Don't go twiddling
> the registers manually.
OK!
I have tried it before and i get a "-ENOSYS" returned.
My code was/is now:
--==>
request_irq(MPC52xx_IRQ2, intmod_isr, IRQF_DISABLED , "intmod",
INTMOD_IRQ_BOARD);
<==--
I have looked up "kernel/irq/manage.c". "-ENOSYS" is returned on function
"setup_irq" because the used irq(MPC52xx_IRQ2) is the same as no_irq_chip.
THE MPC52xx_IRQ2 is a excerpt from "include/ppc/mpc52xx.h" (per copy
paste), but mpc52xx is (now) a powerpc-arch. What is the desired value for
IRQ-2 on a mpc5200b?
best regards,
Silvio Fricke
--
-- S. Fricke ----------------------------- MAILTO:silvio.fricke@gmail.com --
Diplom-Informatiker (FH)
Linux-Entwicklung JABBER: fricke@jabber.org
----------------------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-09-11 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 13:30 [NEWBIE] Interrupt-problem mpc5200 S. Fricke
2007-09-11 12:41 ` S. Fricke
2007-09-11 14:19 ` Grant Likely
2007-09-11 18:28 ` S. Fricke [this message]
2007-09-11 19:05 ` Grant Likely
2007-09-12 18:30 ` S. Fricke
2007-09-12 19:29 ` Grant Likely
2007-09-19 7:16 ` S. Fricke
2007-09-19 14:31 ` Grant Likely
2007-09-14 13:29 ` Matt Sealey
2007-09-14 14:53 ` Grant Likely
2007-09-14 15:18 ` Matt Sealey
2007-09-14 15:49 ` Grant Likely
2007-09-14 16:04 ` Matt Sealey
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=20070911182811.GA3582@sfrouter \
--to=silvio.fricke@googlemail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=silvio.fricke@gmail.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).