All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregor Boirie <gregor.boirie@parrot.com>
To: Lars-Peter Clausen <lars@metafoo.de>,
	Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>, Peter Meerwald <pmeerw@pmeerw.net>
Subject: Re: [PATCH v1 2/2] iio:iio-interrupt-trigger: sysfs poll support
Date: Mon, 22 Feb 2016 14:07:32 +0100	[thread overview]
Message-ID: <56CB0814.9040604@parrot.com> (raw)
In-Reply-To: <56CAF312.1040200@metafoo.de>

On 02/22/2016 12:37 PM, Lars-Peter Clausen wrote:
> Add a sysfs file entry for each interrupt trigger instance allowing
> userspace to :
> * poll for interrupt events ;
>>> Why?
>> On our platform, several sensors are driven by a dedicated "real-time"
>> CPU (bare-metal context). This CPU interrupts Linux in a periodic manner
>> which in turn wakes a user process up to perform sensor fusion.
>> This sysfs poll support allows the user process to explictly wait for
>> this dedicated CPU interrupt to fetch data located in RAM then process
>> them.
> So you are only using the IIO trigger in this setup, but no buffers or
> devices? If you just want to forward the interrupt to userspace UIO might be
> the better solution in this case:
> https://www.kernel.org/doc/htmldocs/uio-howto/about.html
>
> - Lars
I forgot to mention I also need the trigger to initiate in-kernel sampling
for other IIO devices. These samples are also retrieved by the process 
performing
fusion.
>
> --
> 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


  reply	other threads:[~2016-02-22 13:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 19:18 [PATCH v1 0/2] iio-interrupt-trigger enhancements Gregor Boirie
2016-02-19 19:18 ` [PATCH v1 1/2] iio:iio-interrupt-trigger: device-tree support Gregor Boirie
2016-02-21 19:55   ` Jonathan Cameron
2016-02-21 19:55     ` Jonathan Cameron
2016-02-22 19:05     ` Rob Herring
2016-02-22 19:05       ` Rob Herring
2016-02-23  8:24       ` Gregor Boirie
2016-02-23  8:24         ` Gregor Boirie
2016-03-12 12:08       ` Jonathan Cameron
2016-03-12 12:08         ` Jonathan Cameron
2016-02-19 19:18 ` [PATCH v1 2/2] iio:iio-interrupt-trigger: sysfs poll support Gregor Boirie
2016-02-21 20:08   ` Jonathan Cameron
2016-02-22 11:32     ` Gregor Boirie
2016-02-22 11:37       ` Lars-Peter Clausen
2016-02-22 13:07         ` Gregor Boirie [this message]
2016-02-22 13:57           ` Lars-Peter Clausen
2016-02-22 16:07             ` Gregor Boirie

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=56CB0814.9040604@parrot.com \
    --to=gregor.boirie@parrot.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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.