better leve triggered IRQ management needed

I am seeing repeated problems with misconfigured systems that have shared IRQ
devices configured for edge-triggered. Also, network devices using NAPI won't
work reliably on edge-triggered IRQ's.  The kernel IRQ architecture doesn't
have sufficient information to detect this at boot time.  
We should fail request_irq() if the SA_SHIRQ but the irq is edge-triggered.

Right now the concept of level vs edge triggered is buried in things like ELCR for old
PIC, and other stuff for IO-APIC.  There is a IRQ_LEVEL flag in the descriptor field
but nothing sets it or uses it.

Haven't even looked at non i386 arch's but probably even more confusion there.

-
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: better leve triggered IRQ management needed
    • From: Alan Cox <[email protected]>
  • Re: better leve triggered IRQ management needed
    • From: Linus Torvalds <[email protected]>
  • Re: better leve triggered IRQ management needed
    • From: "linux-os \(Dick Johnson\)" <[email protected]>

• Prev by Date: Re: [kernel 2.6] Patch for mxser.c driver
• Next by Date: Re: [Alsa-devel] Re: ALSA regression: oops on shutdown
• Previous by thread: [PATCH] change gen_pool allocator to not touch managed memory
• Next by thread: Re: better leve triggered IRQ management needed
• 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]