summaryrefslogtreecommitdiff
path: root/drivers/iio/imu
diff options
context:
space:
mode:
authorNuno Sa <nuno.sa@analog.com>2021-04-27 10:54:50 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2021-05-17 13:49:09 +0100
commit0ae157081ca33d4ec5a997b67b8942bd149305b6 (patch)
tree4c95b2e02087034138caf56aecf1acdfe8edf4b6 /drivers/iio/imu
parent00a72db718fa198da3946286dcad222399ccd4fb (diff)
iio: adis_buffer: update device page after changing it
It makes more sense to update the device page as soon as we we successfully changed it. Moreover, a follow up patch will handle 'spi_sync' error path which would leave 'current_page' in a inconsistent state. Signed-off-by: Nuno Sa <nuno.sa@analog.com> Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com> Link: https://lore.kernel.org/r/20210427085454.30616-3-nuno.sa@analog.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/imu')
-rw-r--r--drivers/iio/imu/adis_buffer.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/drivers/iio/imu/adis_buffer.c b/drivers/iio/imu/adis_buffer.c
index 0ae551a748eb..4fc0e0ca7561 100644
--- a/drivers/iio/imu/adis_buffer.c
+++ b/drivers/iio/imu/adis_buffer.c
@@ -140,6 +140,8 @@ static irqreturn_t adis_trigger_handler(int irq, void *p)
mutex_unlock(&adis->state_lock);
goto irq_done;
}
+
+ adis->current_page = 0;
}
}
@@ -148,10 +150,8 @@ static irqreturn_t adis_trigger_handler(int irq, void *p)
dev_err(&adis->spi->dev, "Failed to read data: %d", ret);
- if (adis->data->has_paging) {
- adis->current_page = 0;
+ if (adis->data->has_paging)
mutex_unlock(&adis->state_lock);
- }
iio_push_to_buffers_with_timestamp(indio_dev, adis->buffer,
pf->timestamp);