devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Klinger <ak@it-klinger.de>
To: devicetree@vger.kernel.org, linux-iio@vger.kernel.org
Cc: jic23@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
	afaerber@suse.de, arnd@arndb.de, davem@davemloft.net,
	gregkh@linuxfoundation.org, johan@kernel.org,
	khilman@baylibre.com, knaack.h@gmx.de, lars@metafoo.de,
	linux-kernel@vger.kernel.org, martin.blumenstingl@googlemail.com,
	mchehab+samsung@kernel.org, m.othacehe@gmail.com,
	nicolas.ferre@microchip.com, pmeerw@pmeerw.net, robh@kernel.org,
	songqiang1304521@gmail.com, treding@nvidia.com,
	techsupport@maxbotix.com
Subject: [PATCH v2 0/4] add MaxBotix I2CXL ultrasonic iio driver
Date: Fri, 1 Mar 2019 14:41:27 +0100	[thread overview]
Message-ID: <20190301134125.4zqbyzoc2exxigae@arbad> (raw)

This patch series adds support for I2CXL-MaxSonar 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


Changes in v2:
Thanks to the review of Andreas and Peter there are a couple of changes:
- rename type wildcard mb12x2 to i2cxl in dt binding
- split changes in vendor list and dt doc into two patches
- merge driver source and Kconfig/Makefile change into one patch
- reword dt documentation
- use directly __be16 datatype to read directly from i2c
- use s16 as return value from mb12x2_read_distance()

Andreas Klinger (4):
  dt-bindings: Add vendor prefix for MaxBotix
  dt-bindings: maxbotix,i2cxl: Add MaxBotix i2c ultrasonic rangers
  mb12x2.c: add distance iio sensor with i2c
  MAINTAINERS: add maintainer for maxbotix ultrasonic driver

 .../bindings/iio/proximity/maxbotix,i2cxl.txt      |  21 ++
 .../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, 324 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/iio/proximity/maxbotix,i2cxl.txt
 create mode 100644 drivers/iio/proximity/mb12x2.c

-- 
2.11.0

                 reply	other threads:[~2019-03-01 13:41 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=20190301134125.4zqbyzoc2exxigae@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=techsupport@maxbotix.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;
as well as URLs for NNTP newsgroup(s).