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-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Laxman Dewangan <ldewangan@nvidia.com>,
Alexander Kurz <akurz@blala.de>, Tejun Heo <tj@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
Daniel Baluta <daniel.baluta@intel.com>,
"Ludovic Tancerel" <ludovic.tancerel@maplehightech.com>,
Vlad Dogaru <vlad.dogaru@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
"Marek Vasut" <marex@denx.de>,
Crestez Dan Leonard <leonard.crestez@intel.com>,
Gregor Boirie <gregor.boirie@parrot.com>
Subject: [PATCH v1 0/3] iio: devm helpers and Murata zpa2326 barometer support
Date: Wed, 24 Aug 2016 16:58:45 +0200 [thread overview]
Message-ID: <cover.1472050374.git.gregor.boirie@parrot.com> (raw)
Introduce support for the Murata ZPA2326 pressure and temperature sensor.
Also bring in resource managed versions for triggered buffer setup helpers and
trigger registration which the above mentioned driver depends on.
Driver features:
* I2C and SPI buses
* interrupt and polling based operations
* direct, triggered and software buffered IIO sampling modes
* hardware sampling frequency handling
* trigger consumers notification (plugged on interrupt)
* runtime and system power states
2 questions with respect to current driver implementation for which I'd
like to hear your suggestions...
Hardware frequency handling is using the (legacy ?) IIO_DEV_ATTR_SAMP_FREQ and
IIO_CONST_ATTR_SAMP_FREQ_AVAIL macros. As I remember Jonathan telling he was
trying to get rid of these, I wonder whether I should move to
iio_chan_spec_ext_info based code or not.
Sensor is able to sample in a continuous manner, triggering an interrupt each
time a new sample is ready to be fetched by CPU. This mode is implemented using
INDIO_BUFFER_SOFTWARE mode instead of INDIO_BUFFER_TRIGGERED (as can be seen in
the vast majority of IIO drivers). Can somebody confirm there is no misuse
here ?
Regards,
gregor.
Gregor Boirie (3):
iio:trigger: add resource managed (un)register
iio: add resource managed triggered buffer init helpers
iio:pressure: initial zpa2326 barometer support
.../devicetree/bindings/iio/pressure/zpa2326.txt | 23 +
Documentation/driver-model/devres.txt | 4 +
drivers/iio/buffer/industrialio-triggered-buffer.c | 42 +
drivers/iio/industrialio-core.c | 3 +-
drivers/iio/industrialio-trigger.c | 59 +
drivers/iio/pressure/Kconfig | 33 +
drivers/iio/pressure/Makefile | 3 +
drivers/iio/pressure/zpa2326.c | 1766 ++++++++++++++++++++
drivers/iio/pressure/zpa2326.h | 76 +
drivers/iio/pressure/zpa2326_i2c.c | 188 +++
drivers/iio/pressure/zpa2326_spi.c | 184 ++
include/linux/iio/iio.h | 1 +
include/linux/iio/trigger.h | 6 +
include/linux/iio/triggered_buffer.h | 8 +
14 files changed, 2395 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/iio/pressure/zpa2326.txt
create mode 100644 drivers/iio/pressure/zpa2326.c
create mode 100644 drivers/iio/pressure/zpa2326.h
create mode 100644 drivers/iio/pressure/zpa2326_i2c.c
create mode 100644 drivers/iio/pressure/zpa2326_spi.c
--
2.1.4
next reply other threads:[~2016-08-24 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 14:58 Gregor Boirie [this message]
2016-08-24 14:58 ` [PATCH v1 1/3] iio:trigger: add resource managed (un)register Gregor Boirie
2016-08-24 14:58 ` [PATCH v1 2/3] iio: add resource managed triggered buffer init helpers Gregor Boirie
2016-08-24 14:58 ` [PATCH v1 3/3] iio:pressure: initial zpa2326 barometer support Gregor Boirie
2016-08-25 6:34 ` Peter Meerwald-Stadler
2016-08-25 14:45 ` Gregor Boirie
2016-08-29 19:01 ` Jonathan Cameron
2016-08-30 16:18 ` Gregor Boirie
2016-09-03 16:46 ` Jonathan Cameron
2016-08-25 8:38 ` Linus Walleij
2016-08-26 16:27 ` 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.1472050374.git.gregor.boirie@parrot.com \
--to=gregor.boirie@parrot.com \
--cc=akinobu.mita@gmail.com \
--cc=akurz@blala.de \
--cc=corbet@lwn.net \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=ldewangan@nvidia.com \
--cc=leonard.crestez@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=ludovic.tancerel@maplehightech.com \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tj@kernel.org \
--cc=vlad.dogaru@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).