From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, gregkh@linuxfoundation.org
Subject: [PULL] 2nd set of IIO fixes for the 5.4 cycle.
Date: Wed, 30 Oct 2019 20:16:51 +0000 [thread overview]
Message-ID: <20191030201651.0f9b5237@archlinux> (raw)
The following changes since commit 3f3d31622a2c18b644328965925110dd7638b376:
Merge tag 'iio-fixes-for-5.4a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus (2019-10-10 11:18:37 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-5.4b
for you to fetch changes up to e6afcf6c598d6f3a0c9c408bfeddb3f5730608b0:
iio: adc: stm32-adc: fix stopping dma (2019-10-27 15:57:19 +0000)
----------------------------------------------------------------
Second set of IIO fixes for the 5.4 cycle.
* adis16480
- Prevent negative numbers being accepted for sampling frequency.
* inv_mpu6050
- Fix an issue where fifo overflow bits don't actually work as expected,
by checking the fifo count instead.
* srf04
- Allow more time for echo to signal as some sensors supported have
a higher range.
* stm32-adc
- Fix a potential race in dma disable by ensuring all transfers are done.
----------------------------------------------------------------
Alexandru Ardelean (1):
iio: imu: adis16480: make sure provided frequency is positive
Andreas Klinger (1):
iio: srf04: fix wrong limitation in distance measuring
Fabrice Gasnier (1):
iio: adc: stm32-adc: fix stopping dma
Jean-Baptiste Maneyrol (1):
iio: imu: inv_mpu6050: fix no data on MPU6050
drivers/iio/adc/stm32-adc.c | 4 ++--
drivers/iio/imu/adis16480.c | 5 ++++-
drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 9 +++++++++
drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 2 ++
drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c | 15 ++++++++++++---
drivers/iio/proximity/srf04.c | 29 +++++++++++++++--------------
6 files changed, 44 insertions(+), 20 deletions(-)
next reply other threads:[~2019-10-30 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 20:16 Jonathan Cameron [this message]
2019-10-31 17:55 ` [PULL] 2nd set of IIO fixes for the 5.4 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=20191030201651.0f9b5237@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.