[Solved] Interrupt handler not executed

[R.Patil at mei-india.com]

Hello Scott,

Thanks for your immediate response. The problem has been resolved. Actually, I was wrong in pointing out the problem. 

The problem was lying in interrupt handler. The first statement in interrupt handler was disable_irq() which was leading into a deadlock. I replaced 'disable_irq' with 'disable_irq_nosync()' and it worked.  

Thanks and Regards,
Rahul Patil

-----Scott Wood <scottwood at freescale.com> wrote: -----

To: <R.Patil at mei-india.com>
From: Scott Wood <scottwood at freescale.com>
Date: 01/11/2013 11:46PM
Cc: <linuxppc-dev at lists.ozlabs.org>
Subject: Re: Interrupt handler not executed

On 01/11/2013 01:36:29 AM, R.Patil at mei-india.com wrote:
> Hello,
> 
> We are working on board based on Freescale MPC8313ERDB. We have  
> ported linux 3.0.46 kernel on it. In one of device driver written by  
> us, we need to take some action upon asserting IRQ0 interrupt. For  
> this we have written interrupt handler which takes care of this. We  
> are able register interrupt handler successfully with the help of  
> 'request_irq'. We confirmed this by checking respective entry in  
> '/proc/interrupts'. We have also confirmed assertion of interrupt  
> line (IRQ0) on oscilloscope. The problem is, interrupt handler does  
> not execute upon asserting the interrupt line.

What IRQ number did you pass to request_irq()?  request_irq() takes  
virtual interrupt numbers, not anything out of the chip manual.

If that's not the issue, is the interrupt configured properly for level  
and sense?

-Scott

Email Disclaimer:
  ---------------------------

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and  privileged information. Computer viruses can be transmitted via email.The recipient should check this email and any  attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.