From: Matt Ranostay <mranostay@gmail.com>
To: linux-iio@vger.kernel.org, jic23@kernel.org
Cc: Matt Ranostay <mranostay@gmail.com>
Subject: [RFC v2 0/3] iio: chemical: add Atlas pH-SM sensor support
Date: Tue, 15 Dec 2015 01:26:11 -0800 [thread overview]
Message-ID: <1450171574-3283-1-git-send-email-mranostay@gmail.com> (raw)
Changes from v1:
* Add triggered buffer support
* Rework runtime PM functionality
* Add more verbosity to the sysfs-bus-iio documentation
* Correct buffer size with padding bytes
IMPORTANT NOTE: Hasn't been tested on actual hardware yet
Matt Ranostay (3):
devicetree: add Atlas Scientific LLC vendor prefix
iio: ph: add IIO_PH channel type
iio: chemical: add Atlas pH-SM sensor support
Documentation/ABI/testing/sysfs-bus-iio | 7 +
.../bindings/iio/chemical/atlas,ph-sm.txt | 22 ++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
drivers/iio/chemical/Kconfig | 13 +
drivers/iio/chemical/Makefile | 1 +
drivers/iio/chemical/atlas-ph-sensor.c | 431 +++++++++++++++++++++
drivers/iio/industrialio-core.c | 1 +
include/uapi/linux/iio/types.h | 1 +
8 files changed, 477 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,ph-sm.txt
create mode 100644 drivers/iio/chemical/atlas-ph-sensor.c
--
1.9.1
next reply other threads:[~2015-12-15 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 9:26 Matt Ranostay [this message]
2015-12-15 9:26 ` [RFC v2 1/3] devicetree: add Atlas Scientific LLC vendor prefix Matt Ranostay
2015-12-15 9:26 ` [RFC v2 2/3] iio: ph: add IIO_PH channel type Matt Ranostay
2015-12-15 9:26 ` [RFC v2 3/3] iio: chemical: add Atlas pH-SM sensor support Matt Ranostay
2015-12-15 11:03 ` Adriana Reus
2015-12-15 15:06 ` Matt Ranostay
2015-12-15 15:19 ` Matt Ranostay
2015-12-16 9:25 ` Adriana Reus
2015-12-19 16:37 ` Jonathan Cameron
2015-12-20 0:40 ` 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=1450171574-3283-1-git-send-email-mranostay@gmail.com \
--to=mranostay@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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