diff options
author | Ioana Ciornei <ciorneiioana@gmail.com> | 2015-10-27 21:40:56 +0300 |
---|---|---|
committer | Jonathan Cameron <jic23@kernel.org> | 2015-11-21 18:56:44 +0300 |
commit | 2e9fed42209b17116c6221e136ccbd3f252f5f86 (patch) | |
tree | 1eeeb8259272706e243aec8d1df95225c4628223 /drivers/iio/proximity | |
parent | b57f9f34e27bf81c97b10d6725d71824e448c37e (diff) | |
download | linux-2e9fed42209b17116c6221e136ccbd3f252f5f86.tar.xz |
staging: iio: dummy: complete IIO events delivery to userspace
Starting with commit fd2bb310ca (Staging: iio: Move evgen interrupt
generation to irq_work) event processing is handled by calling
both the top half and the threaded part properly simulating real
hardware interrupts making use of threaded interrupts.
This way the processing is split in 2 parts:
* the IRQ handler that runs in IRQ context and only saves the event
timestamp
* the threaded handler that runs in process context, reads the events
and pushes the in the userspace.
If the IRQ handler returns IRQ_HANDLED the threaded handler is not
even being called since the interrupt is considered to be processed.
Because the iio dummy driver processes the events in the threaded
handler the IRQ handler must return IRQ_WAKE_THREAD so that the
threaded part would be awakened and called.
Signed-off-by: Ioana Ciornei <ciorneiioana@gmail.com>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Diffstat (limited to 'drivers/iio/proximity')
0 files changed, 0 insertions, 0 deletions