From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: [PULL] First set of IIO fixes for the 4.6 cycle.
Date: Sun, 3 Apr 2016 21:23:34 +0100 [thread overview]
Message-ID: <57017BC6.3040107@kernel.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-4.6a
for you to fetch changes up to 655048a0b98bc6288ce87cb95a18bf4cada6c1a9:
iio: light: apds9960: correct FIFO check condition (2016-03-20 10:33:33 +0000)
----------------------------------------------------------------
First round of IIO fixes for the 4.6 cycle.
Again I've ended up with two early fix sets, depending on whether they are
dependent on elements of the merge window or simply came in after I had
patches with that dependency already, vs older fixes that were just too
late for the last cycle. This first set is for the older ones.
- max1353
* Add a missing adc to max1363_id - the driver has supported the
max11644-11647 for a while, but as they weren't in the id table there
was no way of actually initializing it.
* Fix a wrong reference voltage for the above models. Given you couldn't
initialize the driver for these parts without patching, no one noticed
that the reference voltage used in computing the scaling was wrong.
- apds9960
* The fifo last enelement was read twice (and hence pushed out twice) due
to a small logic bug.
----------------------------------------------------------------
Matt Ranostay (1):
iio: light: apds9960: correct FIFO check condition
Stefan Eichenberger (2):
iio: adc: max1363: add missing adc to max1363_id
iio: adc: max1363: correct reference voltage
drivers/iio/adc/max1363.c | 12 ++++++++----
drivers/iio/light/apds9960.c | 3 ++-
2 files changed, 10 insertions(+), 5 deletions(-)
next reply other threads:[~2016-04-03 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 20:23 Jonathan Cameron [this message]
2016-04-04 20:00 ` [PULL] First set of IIO fixes for the 4.6 cycle Greg KH
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=57017BC6.3040107@kernel.org \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.