iio: imu: inv_mpu6050: stabilized timestamping in interrupt
authorJean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Mon, 27 May 2024 15:01:17 +0000 (15:01 +0000)
committerJonathan Cameron <Jonathan.Cameron@huawei.com>
Mon, 3 Jun 2024 18:05:56 +0000 (19:05 +0100)
commit8844ed0a6e063acf7173b231021b2d301e31ded9
tree1ca4b8a8814fa379e52e230f868a1c96660a8344
parent182bc496dc63ca03986e3c393166477f4a4c2742
iio: imu: inv_mpu6050: stabilized timestamping in interrupt

Use IRQ ONESHOT flag to ensure the timestamp is not updated in the
hard handler during the thread handler. And use a fixed value of 1
sample that correspond to this first timestamp.

This way we can ensure the timestamp is always corresponding to the
value used by the timestamping mechanism. Otherwise, it is possible
that between FIFO count read and FIFO processing the timestamp is
overwritten in the hard handler.

Fixes: 111e1abd0045 ("iio: imu: inv_mpu6050: use the common inv_sensors timestamp module")
Cc: stable@vger.kernel.org
Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Link: https://lore.kernel.org/r/20240527150117.608792-1-inv.git-commit@tdk.com
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c
drivers/iio/imu/inv_mpu6050/inv_mpu_trigger.c