linux-kernel - Re: Possible to software trigger an interrupt?

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 for Android: free password hash cracker in your pocket

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

Date:	Sun, 03 Apr 2011 17:34:13 +0100
From:	Jonathan Cameron <jic23@....ac.uk>
To:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Possible to software trigger an interrupt?

On 04/03/11 17:04, Jonathan Cameron wrote:
> Hi,
> 
> Having produced a proof of concept for using gpio chips
> to handle the triggers in IIO I am looking at converting
> over our sysfs trigger.  This trigger is used to initialize
> capture on devices in a similar way to dataready interrupts.
> The key point is we want to handle this in the same way within
> drivers as the hardware event triggers. 
> 
> It is a very useful tool.  So the upshot is, what is the best
> way to handle causing an interrupt to occur from userspace?
> 
> Any pointers on how to do this would be most welcome.

For what it is worth, the incredibly dumb approach of just
calling handle_nested_irq seems to 'work'.   I dread to think
what that might be quietly breaking though...

My understanding of some of this code is still rather limited
I'm afraid!

Jonathan
--
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/