RE: [PATCH v4 6/8] iio: imu: adis16607: Add FIFO-based buffered/triggered capture

[Sabau, Radu bogdan]

> -----Original Message-----
> From: Sa, Nuno <nuno.sa@xxxxxxxxxx>
> Sent: Friday, October 30, 2026 4:07 PM

...

> > +
> > +/*
> > + * 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?
> 

Burst Read Function can be used on two registers, DIAG_STAT and FIFO_DATA.
On DIAG_STAT it returns a single set of the most recent samples directly
from the sensor, bypassing the FIFO. 
On FIFO_DATA each burst read pops one set of samples from the FIFO.
Either way the whole set comes out in a single SPI transfer with CS held
low. I used half-duplex because that is what gives access to the burst
read: in full duplex, register reads are separate transfers with CS toggling
between them, so a set can't be popped in one transfer.