Re: [PATCH v4 6/8] iio: imu: adis16607: Add FIFO-based buffered/triggered capture
From: Nuno Sá
Date: Fri Oct 30 2026 - 10:06:32 EST
On Fri, 23 Oct 2026 12:30:23 +0300, Radu Sabau <radu.sabau@xxxxxxxxxx> wrote:
> diff --git a/drivers/iio/imu/adis16607.c b/drivers/iio/imu/adis16607.c
> index 2dda306d7b54..b1f3667d8ce3 100644
> --- a/drivers/iio/imu/adis16607.c
> +++ b/drivers/iio/imu/adis16607.c
> @@ -215,6 +244,286 @@ static const struct adis_ops adis16607_ops = {
> [ ... skip 73 lines ... ]
> + return 0;
> +}
> +
> +/*
> + * Process a single FIFO sample and push to IIO buffer.
> + * FIFO data format differs from regular burst - no DIAG_STAT, data starts immediately.
So FIFO is another command different from burst_mode? If so, is there
any constrain with using SPI full duplex and FIFO?
> [ ... skip 66 lines ... ]
> + u8 fifo_sample[ADIS16607_FIFO_DATA_LEN];
> + u16 diag_stat, word_cnt, sample_cnt;
> + s64 timestamp;
> + int ret, i;
> +
> + mutex_lock(&st->adis.state_lock);
Use the helper.
--
Nuno Sá <nuno.sa@xxxxxxxxxx>