[PATCH] iio: health: max30100: remove mlock usage

From: Rohit Sarkar
Date: Mon Mar 09 2020 - 14:31:42 EST


Use local lock instead of indio_dev's mlock.
The mlock was being used to protect local driver state thus using the
local lock is a better option here.

Signed-off-by: Rohit Sarkar <rohitsarkar5398@xxxxxxxxx>
---
drivers/iio/health/max30100.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/iio/health/max30100.c b/drivers/iio/health/max30100.c
index 84010501762d..8ddc4649547d 100644
--- a/drivers/iio/health/max30100.c
+++ b/drivers/iio/health/max30100.c
@@ -388,7 +388,7 @@ static int max30100_read_raw(struct iio_dev *indio_dev,
* Temperature reading can only be acquired while engine
* is running
*/
- mutex_lock(&indio_dev->mlock);
+ mutex_lock(&data->lock);

if (!iio_buffer_enabled(indio_dev))
ret = -EAGAIN;
@@ -399,7 +399,7 @@ static int max30100_read_raw(struct iio_dev *indio_dev,

}

- mutex_unlock(&indio_dev->mlock);
+ mutex_unlock(&data->lock);
break;
case IIO_CHAN_INFO_SCALE:
*val = 1; /* 0.0625 */
--
2.23.0.385.gbc12974a89