From: Jonathan Cameron <jic23@cam.ac.uk>
To: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Possible to software trigger an interrupt?
Date: Sun, 03 Apr 2011 17:04:26 +0100 [thread overview]
Message-ID: <4D989A8A.3050700@cam.ac.uk> (raw)
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.
Thanks,
Jonathan
next reply other threads:[~2011-04-03 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 16:04 Jonathan Cameron [this message]
2011-04-03 16:34 ` Possible to software trigger an interrupt? Jonathan Cameron
2011-04-07 13:20 ` Steven Rostedt
2011-04-07 13:30 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D989A8A.3050700@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox