From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] First set of IIO fixes for the 5.2 cycle.
Date: Sun, 19 May 2019 09:33:56 +0100 [thread overview]
Message-ID: <20190519093356.4703119a@archlinux> (raw)
The following changes since commit 131ac62253dba79daf4a6d83ab12293d2b9863d3:
staging: most: core: use device description as name (2019-04-02 20:23:07 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-5.2a
for you to fetch changes up to e6d12298310fa1dc11f1d747e05b168016057fdd:
iio: adc: ti-ads8688: fix timestamp is not updated in buffer (2019-05-11 12:50:18 +0100)
----------------------------------------------------------------
First set of IIO fixes for the 5.2 cycle.
* ads124
- Avoid a buffer overrun when setting an array to 0.
* ads8688
- Don't use the pollfunc timestamp as it isn't set and would be wrong
anyway for a device that does sampling on demand.
* ds4422
- Fix masking on register used for chip verification. Wrong address
was being read.
* mpu6050
- Fix the fifo layout for ICM20602 to avoid underreading and hence failure
to move on to the next record in the fifo.
* NPCM ADC
- Make sure there is actually a valid regulator before reading its voltage.
----------------------------------------------------------------
Ruslan Babayev (1):
iio: dac: ds4422/ds4424 fix chip verification
Sean Nyekjaer (1):
iio: adc: ti-ads8688: fix timestamp is not updated in buffer
Steve Moskovchenko (1):
iio: imu: mpu6050: Fix FIFO layout for ICM20602
Tomer Maimon (1):
iio: adc: modify NPCM ADC read reference voltage
Vincent Stehlé (1):
iio: adc: ads124: avoid buffer overflow
drivers/iio/adc/npcm_adc.c | 2 +-
drivers/iio/adc/ti-ads124s08.c | 2 +-
drivers/iio/adc/ti-ads8688.c | 2 +-
drivers/iio/dac/ds4424.c | 2 +-
drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 46 +++++++++++++++++++++++++++---
drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 20 ++++++++++++-
drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c | 3 ++
7 files changed, 68 insertions(+), 9 deletions(-)
next reply other threads:[~2019-05-19 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 8:33 Jonathan Cameron [this message]
2019-05-20 7:16 ` [PULL] First set of IIO fixes for the 5.2 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=20190519093356.4703119a@archlinux \
--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.