From: Andreas Klinger <ak@it-klinger.de>
To: afaerber@suse.de, arnd@arndb.de, davem@davemloft.net,
devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
jic23@kernel.org, johan@kernel.org, khilman@baylibre.com,
knaack.h@gmx.de, lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
martin.blumenstingl@googlemail.com, mchehab+samsung@kernel.org,
m.othacehe@gmail.com, nicolas.ferre@microchip.com,
pmeerw@pmeerw.net, robh+dt@kernel.org, robh@kernel.org,
songqiang1304521@gmail.com, treding@nvidia.com
Subject: [PATCH 0/4] add maxbotix ultrasonic iio driver
Date: Sun, 24 Feb 2019 17:21:28 +0100 [thread overview]
Message-ID: <20190224162126.vzzstmm7rcv6mnh7@arbad> (raw)
This patch series adds support for MaxSonar-I2CXL ultrasonic distance
sensors of family mb12x2 using the i2c interface of vendor maxbotix
Implemented and tested functionality:
- reading the distance via in_distance_raw
- buffered mode with trigger
- make use of status gpio to announce completion of ranging
Andreas Klinger (4):
maxbotix,mb12x2.txt: add dt doc for maxbotix,mb12x2
iio/proximity: add mb12x2 driver to Kconfig and Makefile
mb12x2.c: add mb12x2 ultrasonic distance iio sensor
MAINTAINERS: add maintainer for maxbotix ultrasonic driver
.../bindings/iio/proximity/maxbotix,mb12x2.txt | 22 ++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
MAINTAINERS | 7 +
drivers/iio/proximity/Kconfig | 11 +
drivers/iio/proximity/Makefile | 1 +
drivers/iio/proximity/mb12x2.c | 283 +++++++++++++++++++++
6 files changed, 325 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/proximity/maxbotix,mb12x2.txt
create mode 100644 drivers/iio/proximity/mb12x2.c
--
2.11.0
reply other threads:[~2019-02-24 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190224162126.vzzstmm7rcv6mnh7@arbad \
--to=ak@it-klinger.de \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=johan@kernel.org \
--cc=khilman@baylibre.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=songqiang1304521@gmail.com \
--cc=treding@nvidia.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