From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <greg@kroah.com>, Ioana Ciornei <ciorneiioana@gmail.com>
Cc: linux-iio@vger.kernel.org,
outreachy-kernel <outreachy-kernel@googlegroups.com>,
Cristina Georgiana Opriceana <cristina.opriceana@gmail.com>
Subject: Re: [Outreachy kernel] [PATCH] staging: iio: dummy: complete IIO events delivery to userspace
Date: Sat, 31 Oct 2015 10:39:56 +0000 [thread overview]
Message-ID: <56349A7C.7070907@kernel.org> (raw)
In-Reply-To: <20151028230709.GA28617@kroah.com>
On 28/10/15 23:07, Greg KH wrote:
> 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@kroah.com> 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@gmail.com>
>>>> Fixes: fd2bb310ca ("Staging: iio: Move evgen interrupt generation to irq_work")
>>>> Acked-by: Daniel Baluta <daniel.baluta@intel.com>
>>>> ---
>>>> 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.
Hmm. This one got complex. The fix needs to go prior to the driver move
but after the patch that broken. I've bodged it together and pushed out
a temporary branch fixes-togreg-post-rc1
I'll push that one on to Greg as the name suggests after rc1 is out and hence
the broken patch has gone into Linus' tree. Then I'll deal with any fallout
in the togreg branch before sending that on to Greg.
At the end of the day, we have a broken fake driver - as long as we fix it reasonably
quickly no one other than Ioana will probably ever notice ;)
Jonathan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-10-31 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 18:40 [PATCH] staging: iio: dummy: complete IIO events delivery to userspace Ioana Ciornei
2015-10-28 8:26 ` [Outreachy kernel] " Daniel Baluta
2015-10-28 22:47 ` Greg KH
2015-10-28 22:49 ` Ioana Ciornei
2015-10-28 23:07 ` Greg KH
2015-10-31 10:39 ` Jonathan Cameron [this message]
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=56349A7C.7070907@kernel.org \
--to=jic23@kernel.org \
--cc=ciorneiioana@gmail.com \
--cc=cristina.opriceana@gmail.com \
--cc=greg@kroah.com \
--cc=linux-iio@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.