summaryrefslogtreecommitdiff
path: root/include/linux/iio/imu
diff options
context:
space:
mode:
authorNuno Sa <nuno.sa@analog.com>2021-04-27 11:54:52 +0300
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2021-05-17 15:49:09 +0300
commitdbf20809d6e0072ad189c937761d58bf98a47b43 (patch)
tree77cdd9cb412f0e087398c5fe247d5559d7ea52ff /include/linux/iio/imu
parent669da56a7eafb9b4025261a07f1d27364159cac9 (diff)
downloadlinux-dbf20809d6e0072ad189c937761d58bf98a47b43.tar.xz
iio: adis: add burst_max_speed_hz variable
Typically, in burst mode, the device cannot operate at it's full spi speed. Hence, the spi transfers for burst mode have to take this into account. With this change we avoid a potential race with the spi core as drivers were 'hacking' the device 'max_speed_hz' directly in the trigger handler. Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com> Signed-off-by: Nuno Sa <nuno.sa@analog.com> Link: https://lore.kernel.org/r/20210427085454.30616-5-nuno.sa@analog.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'include/linux/iio/imu')
-rw-r--r--include/linux/iio/imu/adis.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/linux/iio/imu/adis.h b/include/linux/iio/imu/adis.h
index f9b728d490b1..cf49997d5903 100644
--- a/include/linux/iio/imu/adis.h
+++ b/include/linux/iio/imu/adis.h
@@ -55,6 +55,7 @@ struct adis_timeout {
* this should be the minimum size supported by the device.
* @burst_max_len: Holds the maximum burst size when the device supports
* more than one burst mode with different sizes
+ * @burst_max_speed_hz: Maximum spi speed that can be used in burst mode
*/
struct adis_data {
unsigned int read_delay;
@@ -83,6 +84,7 @@ struct adis_data {
unsigned int burst_reg_cmd;
unsigned int burst_len;
unsigned int burst_max_len;
+ unsigned int burst_max_speed_hz;
};
/**