From: Andreas Klinger <ak@it-klinger.de>
To: robh+dt@kernel.org, jic23@kernel.org, mark.rutland@arm.com
Cc: mripard@kernel.org, shawnguo@kernel.org, heiko@sntech.de,
icenowy@aosc.io, laurent.pinchart@ideasonboard.com,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
gregkh@linuxfoundation.org, christophe.jaillet@wanadoo.fr,
tglx@linutronix.de, mchehab+samsung@kernel.org,
davem@davemloft.net, paulmck@linux.ibm.com,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] iio: add driver for ping))) and laserping sensors
Date: Fri, 15 Nov 2019 08:43:35 +0100 [thread overview]
Message-ID: <20191115074333.ria34nl64ehglalm@arbad> (raw)
This patchset adds support for parallax PING))) and LaserPING sensors as
iio driver. The driver is derived from srf04 but the device is using only
one GPIO for both triggering and the echo.
Changes in v2:
Thanks to the reviews of Jonathan, Rob and Michel there are some
improvements:
- optimize use of macros with to_platform_device() and
of_device_get_match_data()
- change spacing and typos
- simplify ascii art timing diagram
- merge patch for driver and corresponding Kconfig and Makefile
Andreas Klinger (4):
dt-bindings: add vendor prefix parallax
dt-bindings: add parallax ping sensors
iio: ping: add parallax ping sensors
MAINTAINERS: add maintainer for ping iio sensors
.../bindings/iio/proximity/parallax-ping.yaml | 51 ++++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
MAINTAINERS | 7 +
drivers/iio/proximity/Kconfig | 15 +
drivers/iio/proximity/Makefile | 1 +
drivers/iio/proximity/ping.c | 333 +++++++++++++++++++++
6 files changed, 409 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/proximity/parallax-ping.yaml
create mode 100644 drivers/iio/proximity/ping.c
--
2.11.0
reply other threads:[~2019-11-15 7:44 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=20191115074333.ria34nl64ehglalm@arbad \
--to=ak@it-klinger.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=icenowy@aosc.io \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mripard@kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/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