From: WITTROCK <jwittrock@maginst.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Interrupt-problem mpc5200
Date: Tue, 11 Sep 2007 17:47:58 -0700 (PDT) [thread overview]
Message-ID: <12626802.post@talk.nabble.com> (raw)
In-Reply-To: <20070911124348.GJ11807@sfrouter>
Is it possible the interrupt is going off as soon as you unmask it? Can you
show your "intmod_isr".
I had a similar problem when I pulled a "wittrock" and forgot to make the
interrupt edge sensitive, but from what I can see you have made yours edge
sensitive.
-WITTROCK
S. Fricke wrote:
>
>
> Dear Linux-enthusiasts,
>
> I'm still at the same problem.
>
> I have now implemented a irq_chip for the hardwired IRQ2. Now I have
>
>
> --==>
> volatile static struct mpc52xx_intr __iomem *intr;
> unsigned long flags;
> static DEFINE_SPINLOCK(my_irq_controller_lock);
>
> /*
> * HELPER-Function
> */
> static inline void io_be_setbit(u32 __iomem *addr, int bitno)
> {
> out_be32(addr, in_be32(addr) | (1 << bitno));
> }
>
> static inline void io_be_clrbit(u32 __iomem *addr, int bitno)
> {
> out_be32(addr, in_be32(addr) & ~(1 << bitno));
> }
>
> /*
> * IRQ-Zeugs
> */
> static void my_irq_ack(unsigned int irq)
> {
> printk("%s(%s/%d):\n", __FILE__, __FUNCTION__, __LINE__);
> spin_lock_irqsave(&my_irq_controller_lock, flags);
> if(intr)
> io_be_setbit(&intr->ctrl, 25);
> spin_unlock_irqrestore(&my_irq_controller_lock, flags);
> printk("%s(%s/%d):\n", __FILE__, __FUNCTION__, __LINE__);
> }
>
> /* irq - disabled */
> static void my_irq_mask(unsigned int irq)
> {
> printk("%s(%s/%d):\n", __FILE__, __FUNCTION__, __LINE__);
> spin_lock_irqsave(&my_irq_controller_lock, flags);
> if(intr)
> io_be_clrbit(&intr->ctrl, 9);
> spin_unlock_irqrestore(&my_irq_controller_lock, flags);
> printk("%s(%s/%d):\n", __FILE__, __FUNCTION__, __LINE__);
> }
>
> /* irq - enable */
> static void my_irq_unmask(unsigned int irq)
> {
> printk("%s(%s/%d):\n", __FILE__, __FUNCTION__, __LINE__);
> spin_lock_irqsave(&my_irq_controller_lock, flags);
> if(intr)
> io_be_setbit(&intr->ctrl, 9);
> spin_unlock_irqrestore(&my_irq_controller_lock, flags);
> printk("%s(%s/%d):\n", __FILE__, __FUNCTION__, __LINE__);
> }
>
> static struct irq_chip my_irq_chip = {
> .typename = "MY_IRQ_TEST",
> .ack = my_irq_ack,
> .mask = my_irq_mask,
> .unmask = my_irq_unmask,
> };
>
> static int __init mod_init( void )
> {
> // ...
>
> intr = mpc52xx_find_and_map("mpc52xx-pic");
> if(!intr) {
> panic(__FILE__ ": mpc52xx-pic - MAP failed");
> }
>
> set_irq_chip(MPC52xx_IRQ2, &my_irq_chip);
> a = request_irq(2, intmod_isr, IRQF_DISABLED , "intmod",
> INTMOD_IRQ_BOARD);
> printk("a: 0x%08x\n", a);
>
> // ...
> }
>
> <==--
>
> Now my code hangs on the my_irq_unmask(...)-function on "io_be_setbit".
> Why?
> Can anyone help me, or point me to the right newsgroup/forum?
>
> So long!
>
> Silvio
>
>
> --
> -- S. Fricke ----------------------------- MAILTO:silvio.fricke@gmail.com
> --
> Diplom-Informatiker (FH)
> Linux-Entwicklung JABBER: fricke@jabber.org
> ----------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
View this message in context: http://www.nabble.com/Interrupt-problem-mpc5200-tf4413834.html#a12626802
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-09-12 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 9:03 Interrupt-problem mpc5200 S. Fricke
2007-09-11 12:43 ` S. Fricke
2007-09-12 0:47 ` WITTROCK [this message]
2007-09-11 12:49 ` WITTROCK
2007-09-11 13:48 ` S. Fricke
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=12626802.post@talk.nabble.com \
--to=jwittrock@maginst.com \
--cc=linuxppc-embedded@ozlabs.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 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).