Re: Where is the interrupt going?

On Friday 23 November 2007, Alan Cox wrote:
> On Thu, 22 Nov 2007 16:48:53 -0800
> [email protected] wrote:
> 
> > 
> > I tried the hammer and the problem persists.
> 
> See my earlier email - your driver registers the irq with IRQF_DISABLED
> then never enables it.

As already explained by Kyle IRQF_DISABLED shouldn't matter here.

[ Nowadays IRQF_DISABLED only tells kernel/irq/handle.c::handle_IRQ_event()
  to not enable local interrupts before calling your IRQ handler.

  I've recently removed IRQF_DISABLED from IDE after noticing this. ]

Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Where is the interrupt going?
    • From: Alan Cox <[email protected]>

• References:
  • Where is the interrupt going?
    • From: Al Niessner <[email protected]>
  • Re: Where is the interrupt going?
    • From: [email protected]
  • Re: Where is the interrupt going?
    • From: Alan Cox <[email protected]>

• Prev by Date: Re: Inotify fails to send IN_ATTRIB events
• Next by Date: [PATCH] sata_nv: don't use legacy DMA in ADMA mode (v2)
• Previous by thread: Re: Where is the interrupt going?
• Next by thread: Re: Where is the interrupt going?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]