[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190926111812.15957-1-alexandru.ardelean@analog.com>
Date: Thu, 26 Sep 2019 14:18:02 +0300
From: Alexandru Ardelean <alexandru.ardelean@...log.com>
To: <linux-iio@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC: <jic23@...nel.org>,
Alexandru Ardelean <alexandru.ardelean@...log.com>
Subject: [PATCH 00/10] iio: imu: adis: cleanup lock usage
There is a general effort for cleaning up `indio_dev->mlock` usage in IIO
drivers. As part of that some ADIS drivers also need to do that.
This changeset does a little more, by reworking the `txrx_lock` from the
ADIS library to be used as a general `state_lock` to protect state between
consecutive read/write ops.
As such, all users of the ADIS lib have been verified to have their usage
of mlock checked. Some just needed the mlock usage removed (as done in
other patches).
Alexandru Ardelean (10):
iio: imu: adis: rename txrx_lock -> state_lock
iio: imu: adis: add unlocked read/write function versions
iio: imu: adis[16480]: group RW into a single lock in
adis_enable_irq()
iio: imu: adis: create an unlocked version of adis_check_status()
iio: imu: adis: create an unlocked version of adis_reset()
iio: imu: adis: protect initial startup routine with state lock
iio: imu: adis: group single conversion under a single state lock
iio: imu: adis16400: rework locks using ADIS library's state lock
iio: gyro: adis16136: rework locks using ADIS library's state lock
iio: imu: adis16480: use state lock for filter freq set
drivers/iio/gyro/adis16136.c | 31 ++++---
drivers/iio/imu/adis.c | 95 ++++++++++++----------
drivers/iio/imu/adis16400.c | 51 ++++++------
drivers/iio/imu/adis16480.c | 17 ++--
drivers/iio/imu/adis_buffer.c | 4 +-
include/linux/iio/imu/adis.h | 148 ++++++++++++++++++++++++++++++++--
6 files changed, 254 insertions(+), 92 deletions(-)
--
2.20.1
Powered by blists - more mailing lists