From: Gregor Boirie <gregor.boirie@parrot.com>
To: <linux-iio@vger.kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Gregor Boirie <gregor.boirie@parrot.com>
Subject: [PATCH v1 0/2] iio-interrupt-trigger enhancements
Date: Fri, 19 Feb 2016 20:18:42 +0100 [thread overview]
Message-ID: <cover.1455908065.git.gregor.boirie@parrot.com> (raw)
First patch enable device-tree support.
Second one adds poll(2) support through a new sysfs attribute file "count"
showing how many times the attached interrupt occurred since trigger
initialization. This allows a userspace process :
* to explicitly wait for the interrupt to happen ;
* and to know wether or not it missed interrupt events since last count
retrieval.
Regards.
Grégor
Grégor Boirie (2):
iio:iio-interrupt-trigger: device-tree support
iio:iio-interrupt-trigger: sysfs poll support
.../ABI/testing/sysfs-bus-iio-trig-interrupt | 22 +++++
drivers/iio/trigger/iio-trig-interrupt.c | 99 +++++++++++++++++-----
2 files changed, 98 insertions(+), 23 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-trig-interrupt
--
2.1.4
next reply other threads:[~2016-02-19 19:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 19:18 Gregor Boirie [this message]
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
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=cover.1455908065.git.gregor.boirie@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.