linux-kernel - Re: [PATCH] genirq: handle shared irqs in handle_nested

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinaTTqv3r0tWDOeZR5n=nHj5LybxAPf5uvUxpRh@mail.gmail.com>
Date:	Fri, 29 Oct 2010 20:51:38 +0530
From:	Rabin Vincent <rabin@....in>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] genirq: handle shared irqs in handle_nested_irq()

On Fri, Oct 29, 2010 at 12:24 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
> On Thu, 28 Oct 2010, Rabin Vincent wrote:
>> Allow shared irqs to work when nested threads are used for handling
>> threaded interrupts.
>
> Why do we want this ? handle_nested_irq() is called from a interrupt
> demultiplexer, so why would we need shared interrupts for this ?

Threaded IRQ + handle_nested_irq() is used by I2C GPIO expander drivers
like chained hander + generic_handle_irq() is used by on-chip GPIO
drivers.  If two irq handlers are registered on an on-chip GPIO
interrupt (because two devices are externally connected), it works.  If
the handlers are instead registered on one of the expander's pins'
interrupt, without this patch, only the handler registered first is
called.

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