From: Matt Ranostay <matt.ranostay@konsulko.com>
To: linux-iio@vger.kernel.org
Cc: jic23@kernel.org, Matt Ranostay <matt.ranostay@konsulko.com>
Subject: [PATCH v5 0/3] iio: chemical: atlas-sensor: add DO support
Date: Thu, 6 Feb 2020 21:18:10 -0800 [thread overview]
Message-ID: <20200207051813.9708-1-matt.ranostay@konsulko.com> (raw)
Changes from v1:
* combined dt binding docs
* added making interrupt line is optional patchset
* broke out dt changes from DO-SM module patchset
Change from v2:
* switch docs to YAML format
Change from v3:
* fix up issues reported with dt-schema
Change from v4:
* fix logic issue in optional interrupt patchset
Matt Ranostay (3):
iio: chemical: atlas-sensor: allow probe without interrupt line
iio: chemical: atlas-sensor: add DO-SM module support
dt-bindings: iio: chemical: consolidate atlas-sensor docs
.../bindings/iio/chemical/atlas,ec-sm.txt | 21 -----
.../bindings/iio/chemical/atlas,orp-sm.txt | 21 -----
.../bindings/iio/chemical/atlas,ph-sm.txt | 21 -----
.../bindings/iio/chemical/atlas,sensor.yaml | 53 +++++++++++
drivers/iio/chemical/atlas-sensor.c | 91 +++++++++++++++----
5 files changed, 125 insertions(+), 82 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,ec-sm.txt
delete mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,orp-sm.txt
delete mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,ph-sm.txt
create mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,sensor.yaml
--
2.20.1
next reply other threads:[~2020-02-07 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 5:18 Matt Ranostay [this message]
2020-02-07 5:18 ` [PATCH v5 1/3] iio: chemical: atlas-sensor: allow probe without interrupt line Matt Ranostay
2020-02-07 5:18 ` [PATCH v5 2/3] iio: chemical: atlas-sensor: add DO-SM module support Matt Ranostay
2020-02-07 5:18 ` [PATCH v5 3/3] dt-bindings: iio: chemical: consolidate atlas-sensor docs 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=20200207051813.9708-1-matt.ranostay@konsulko.com \
--to=matt.ranostay@konsulko.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;
as well as URLs for NNTP newsgroup(s).