From: Matt Ranostay <mranostay@gmail.com>
To: jic23@kernel.org, lars@metafoo.de, pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, Matt Ranostay <mranostay@gmail.com>
Subject: [RFC v4 0/4] iio: new chemical sensor framework and channel types
Date: Wed, 9 Sep 2015 23:30:50 -0700 [thread overview]
Message-ID: <1441866654-10381-1-git-send-email-mranostay@gmail.com> (raw)
Changes from RFC v3:
* Add missing Kconfig
Matt Ranostay (4):
iio: chemical: Add IIO_CONCENTRATION channel type
iio: resistance: add IIO_RESISTANCE channel type
devicetree: add SGX Sensortech vendor id
iio: chemical: add SGX VZ89x VOC sensor support
Documentation/ABI/testing/sysfs-bus-iio | 14 ++
.../ABI/testing/sysfs-bus-iio-chemical-vz89x | 30 +++
.../devicetree/bindings/i2c/trivial-devices.txt | 1 +
.../devicetree/bindings/vendor-prefixes.txt | 1 +
drivers/iio/Kconfig | 1 +
drivers/iio/Makefile | 1 +
drivers/iio/chemical/Kconfig | 15 ++
drivers/iio/chemical/Makefile | 6 +
drivers/iio/chemical/vz89x.c | 245 +++++++++++++++++++++
drivers/iio/industrialio-core.c | 2 +
include/uapi/linux/iio/types.h | 2 +
11 files changed, 318 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-chemical-vz89x
create mode 100644 drivers/iio/chemical/Kconfig
create mode 100644 drivers/iio/chemical/Makefile
create mode 100644 drivers/iio/chemical/vz89x.c
--
1.9.1
next reply other threads:[~2015-09-10 6:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 6:30 Matt Ranostay [this message]
2015-09-10 6:30 ` [RFC v4 1/4] iio: chemical: Add IIO_CONCENTRATION channel type Matt Ranostay
2015-09-12 9:16 ` Jonathan Cameron
2015-09-10 6:30 ` [RFC v4 2/4] iio: resistance: add IIO_RESISTANCE " Matt Ranostay
2015-09-12 9:19 ` Jonathan Cameron
2015-09-10 6:30 ` [RFC v4 3/4] devicetree: add SGX Sensortech vendor id Matt Ranostay
2015-09-10 6:30 ` [RFC v4 4/4] iio: chemical: add SGX VZ89x VOC sensor support Matt Ranostay
2015-09-10 9:08 ` Peter Meerwald
2015-09-10 16:16 ` Matt Ranostay
2015-09-11 2:13 ` Matt Ranostay
2015-09-12 9:34 ` Jonathan Cameron
2015-09-12 23:11 ` Matt Ranostay
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=1441866654-10381-1-git-send-email-mranostay@gmail.com \
--to=mranostay@gmail.com \
--cc=jic23@kernel.org \
--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 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).