This is a note to let you know that I've just added the patch titled
iio: gyro: bmg160: fix buffer read values
to the 4.5-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
iio-gyro-bmg160-fix-buffer-read-values.patch
and it can be found in the queue-4.5 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From b475c59b113db1e66eb9527ffdec3c5241c847e5 Mon Sep 17 00:00:00 2001
From: Irina Tirdea <irina.tirdea@xxxxxxxxx>
Date: Mon, 28 Mar 2016 20:15:46 +0300
Subject: iio: gyro: bmg160: fix buffer read values
From: Irina Tirdea <irina.tirdea@xxxxxxxxx>
commit b475c59b113db1e66eb9527ffdec3c5241c847e5 upstream.
When reading gyroscope axes using iio buffers, the values
returned are always 0. In the interrupt handler, the return
value of the read operation is returned to the user instead
of the value read. Return the value read to the user.
This is also fixed in commit 82d8e5da1a33 ("iio:
accel: bmg160: optimize transfers in trigger handler").
Signed-off-by: Irina Tirdea <irina.tirdea@xxxxxxxxx>
Signed-off-by: Jonathan Cameron <jic23@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/iio/gyro/bmg160_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/iio/gyro/bmg160_core.c
+++ b/drivers/iio/gyro/bmg160_core.c
@@ -780,7 +780,7 @@ static irqreturn_t bmg160_trigger_handle
mutex_unlock(&data->mutex);
goto err;
}
- data->buffer[i++] = ret;
+ data->buffer[i++] = val;
}
mutex_unlock(&data->mutex);
Patches currently in stable-queue which might be from irina.tirdea@xxxxxxxxx are
queue-4.5/iio-gyro-bmg160-fix-buffer-read-values.patch
queue-4.5/iio-gyro-bmg160-fix-endianness-when-reading-axes.patch
queue-4.5/iio-fix-config-watermark-initial-value.patch
queue-4.5/iio-accel-bmc150-fix-endianness-when-reading-axes.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html