RE: Shared Interrupt handling.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for the code snippet Rajat,
so this confirms that at design time one should be careful not to share interrupt between a high int generating device and a one that does it less frequently.

Also is it always that the hardware have a register which tell if there is a pending interrupt, which the int handler checks to make sure if need to service an int.

thanks
Bisla


> Date: Thu, 3 May 2007 01:32:10 -0400
> From: vapier.adi@xxxxxxxxx
> To: rajat.noida.india@xxxxxxxxx
> Subject: Re: Shared Interrupt handling.
> CC: kernelnewbies@xxxxxxxxxxxx; k_bisla@xxxxxxxxxxx
>
> On 5/3/07, Rajat Jain <rajat.noida.india@xxxxxxxxx> wrote:
> > Doesn't the following code in handle_IRQ_event() suggest that ALL the
> > interrupt handlers are called, IRRESPECTIVE of the return value?
> >
> > do {
> > ret = action->handler(irq, action->dev_id);
> > if (ret == IRQ_HANDLED)
> > status |= action->flags;
> > retval |= ret;
> > action = "">> > } while (action);
>
> it certainly seems that way huh ;)
>
> makes sense too for the reasons "k b" highlighted
> -mike
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
> Please read the FAQ at http://kernelnewbies.org/FAQ
>


Explore the seven wonders of the world Learn more!

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux