From: Matt Ranostay <mranostay@gmail.com>
To: linux-iio@vger.kernel.org
Cc: jic23@kernel.org, Matt Ranostay <mranostay@gmail.com>
Subject: [PATCH v2 0/4] iio: chemical: vz89x: add multiple chip functionality
Date: Wed, 24 Aug 2016 23:44:46 -0700 [thread overview]
Message-ID: <1472107490-11924-1-git-send-email-mranostay@gmail.com> (raw)
Add support for multiple chip configuration, support for the vz89te part,
CRC check functionality, and buffer corruption check.
Changes from v1:
* Move chip configuration to vz89_chip_data struct
* Removed redundant mutex and use indio_dev->mlock instead
Matt Ranostay (4):
iio: chemical: vz89x: abstract chip configuration
iio: chemical: vz89x: add support for VZ89TE part
iio: chemical: vz89x: prevent corrupted buffer from being read
iio: chemical: vz89x: remove mutex and replace with
iio_device_*_direct_mode
drivers/iio/chemical/vz89x.c | 222 ++++++++++++++++++++++++++++++++++---------
1 file changed, 178 insertions(+), 44 deletions(-)
--
2.7.4
next reply other threads:[~2016-08-25 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 6:44 Matt Ranostay [this message]
2016-08-25 6:44 ` [PATCH v2 1/4] iio: chemical: vz89x: abstract chip configuration Matt Ranostay
2016-08-29 16:48 ` Jonathan Cameron
2016-08-25 6:44 ` [PATCH v2 2/4] iio: chemical: vz89x: add support for VZ89TE part Matt Ranostay
2016-08-29 16:49 ` Jonathan Cameron
2016-08-25 6:44 ` [PATCH v2 3/4] iio: chemical: vz89x: prevent corrupted buffer from being read Matt Ranostay
2016-08-29 17:01 ` Jonathan Cameron
2016-08-25 6:44 ` [PATCH v2 4/4] iio: chemical: vz89x: remove mutex and replace with iio_device_*_direct_mode Matt Ranostay
2016-08-29 16:56 ` 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=1472107490-11924-1-git-send-email-mranostay@gmail.com \
--to=mranostay@gmail.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).