diff options
author | Jean-Baptiste Maneyrol <[email protected]> | 2024-05-29 15:47:17 +0000 |
---|---|---|
committer | Jonathan Cameron <[email protected]> | 2024-06-02 11:56:40 +0100 |
commit | d7bd473632d07f8a54655c270c0940cc3671c548 (patch) | |
tree | 9286b850a08110db7ecdea1fa2b36fc743d37186 /scripts/generate_rust_analyzer.py | |
parent | 95444b9eeb8c5c0330563931d70c61ca3b101548 (diff) |
iio: imu: inv_icm42600: stabilized timestamp in interrupt
Use IRQF_ONESHOT flag to ensure the timestamp is not updated in the
hard handler during the thread handler. And compute and use the
effective watermark value 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: ec74ae9fd37c ("iio: imu: inv_icm42600: add accurate timestamping")
Cc: [email protected]
Signed-off-by: Jean-Baptiste Maneyrol <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jonathan Cameron <[email protected]>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions