From: Andreas Klinger <ak@it-klinger.de>
To: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, linux-iio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, hdegoede@redhat.com, wsa@the-dreams.de,
chris.packham@alliedtelesis.co.nz, jelle@vdwaa.nl,
devicetree@vger.kernel.org
Subject: [PATCH v4 0/5] iio: srf08: add support for similar devices and triggered buffers
Date: Fri, 18 Aug 2017 00:08:29 +0200 [thread overview]
Message-ID: <20170817220829.GA4687@arbeit> (raw)
This patch series adds support for:
- triggered buffer
- ultrasonic devices srf02 and srf10
Changes in v4:
- rebase to recent git repository with trivial-devices.txt now under
devicetree/bindings
Changes in v3:
- introduce struct chip_info for device specific features
- remove locking error in srf08_trigger_handler()
Changes in v2:
- removed unnecessary patch "[PATCH 6/7] iio: srf08: add buffered to device mode"
- incorporated patch "[PATCH 7/7] iio: srf08: change text in Kconfig" where suitable
- changed order of patches to improve logical flow of changes
- improved distinction of sensor types
Andreas Klinger (5):
iio: srf08: add device tree binding for srf02 and srf10
iio: srf08: add device tree table
iio: srf08: add triggered buffer support
iio: srf08: add sensor type srf10
iio: srf08: add support for srf02 in i2c mode
.../devicetree/bindings/trivial-devices.txt | 2 +
drivers/iio/proximity/Kconfig | 8 +-
drivers/iio/proximity/srf08.c | 227 ++++++++++++++++++---
3 files changed, 203 insertions(+), 34 deletions(-)
--
2.1.4
--
Andreas Klinger
Grabenreith 27
84508 Burgkirchen
+49 8623 919966
ak@it-klinger.de
www.it-klinger.de
www.grabenreith.de
next reply other threads:[~2017-08-17 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 22:08 Andreas Klinger [this message]
2017-08-18 7:19 ` [PATCH v4 0/5] iio: srf08: add support for similar devices and triggered buffers Jonathan Cameron
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=20170817220829.GA4687@arbeit \
--to=ak@it-klinger.de \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=jelle@vdwaa.nl \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).