linux-kernel - Re: Simulating level triggered interrupts with edges

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] [day] [month] [year] [list]

Message-ID: <20110623012352.GD20949@opensource.wolfsonmicro.com>
Date:	Thu, 23 Jun 2011 02:23:53 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Russell King <linux@....linux.org.uk>
Subject: Re: Simulating level triggered interrupts with edges

On Wed, Jun 22, 2011 at 11:32:03PM +0200, Thomas Gleixner wrote:

> Though it's non-trivial. Think threaded interrupts, where we cannot
> deal with that in handle_irq_edge(). I have no immediate idea how to
> solve that at the core code, but feel free to have a stab.

Yes, that's why I asked - all the devices I care about have threaded
handlers and I care about a system where the interrupt controller is
threaded too.  I was thinking error handling on set_type() and flags
but thought I must be missing something.  I'll probably have a poke
sometime anyway.
--
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/