On Thu, Oct 29, 2015 at 12:49:28AM +0200, Ioana Ciornei wrote:
> On Thu, Oct 29, 2015 at 12:47 AM, Greg KH <greg@xxxxxxxxx> wrote:
> > On Tue, Oct 27, 2015 at 08:40:56PM +0200, Ioana Ciornei wrote:
> >> 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@xxxxxxxxx>
> >> Fixes: fd2bb310ca ("Staging: iio: Move evgen interrupt generation to irq_work")
> >> Acked-by: Daniel Baluta <daniel.baluta@xxxxxxxxx>
> >> ---
> >> rebased on linux-iio tree
> >
> > Daniel, can you forward this to the iio developers, I can't take this as
> > it doesn't apply to my tree :(
> >
>
> I already sent it to the linux-iio list as Daniel suggested in a
> previous message.
> I hope it's ok.
Fine with me, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
