On 02 Oct 2009, at 9:30 AM, Harinderjit Singh Sandhu wrote: i want to know which statement is turning it off.....
On Thu, Oct 1, 2009 at 9:03 PM, Greg KH <greg@xxxxxxxxx> wrote: On Thu, Oct 01, 2009 at 08:55:27PM +0530, Harinderjit Singh Sandhu wrote:
> this is the code for the small module that i wrote
The problem is in your interrupt handler:
> // interrupt handler
> irqreturn_t interrupt_handler (int irqn, void *dev)
> {
>
> printk("Press a key ");
>
>
> return IRQ_HANDLED;
>
>
> }
You aren't really handling the interrupt by turning it off in the
hardware. So the kernel sees an interrupt storm for your device and
shuts it off to save the system from going crazy.
What are you trying to do with this sample module?
greg k-h
You need to clear the hardware interrupt in some way (to acknowledge to the hardware that you've seen it essentially). Often this means reading a register value. It depends on your hardware... |
