From: "Nuno Sá" <nuno.sa@analog.com>
To: "Sabau, Radu bogdan" <radu.sabau@analog.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux <linux@analog.com>
Subject: Re: [PATCH v4 6/8] iio: imu: adis16607: Add FIFO-based buffered/triggered capture
Date: Mon, 2 Nov 2026 10:59:02 +0000 [thread overview]
Message-ID: <auhszHAlMwT6WW2H@nsa> (raw)
In-Reply-To: <LV9PR03MB8414E62A0A91DEF6FA4C6D80F76A2@LV9PR03MB8414.namprd03.prod.outlook.com>
On Mon, Nov 02, 2026 at 08:08:50AM +0000, Sabau, Radu bogdan wrote:
> > -----Original Message-----
> > From: Sa, Nuno <nuno.sa@analog.com>
> > 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.
I see! Thanks to clear that out (too lazy to go look at the datashee :))!
- Nuno Sá
>
next prev parent reply other threads:[~2026-11-02 10:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 9:30 [PATCH v4 0/8] iio: imu: Add support for the ADI ADIS16607 Radu Sabau via B4 Relay
2026-10-23 9:30 ` [PATCH v4 1/8] iio: imu: adis: Add optional self_test callback Radu Sabau via B4 Relay
2026-10-30 14:06 ` Nuno Sá
2026-10-23 9:30 ` [PATCH v4 2/8] iio: imu: adis: Fix custom reset dispatch in adislib Radu Sabau via B4 Relay
2026-10-30 14:06 ` Nuno Sá
2026-10-23 9:30 ` [PATCH v4 3/8] iio: imu: adis: Add optional post_reset_setup callback Radu Sabau via B4 Relay
2026-10-25 23:52 ` Jonathan Cameron
2026-10-26 9:52 ` Sabau, Radu bogdan
2026-10-23 9:30 ` [PATCH v4 4/8] dt-bindings: iio: imu: Add bindings for ADI ADIS16607 Radu Sabau via B4 Relay
2026-10-25 23:54 ` Jonathan Cameron
2026-10-23 9:30 ` [PATCH v4 5/8] iio: imu: Add driver for the " Radu Sabau via B4 Relay
2026-10-23 10:26 ` Andy Shevchenko
2026-10-26 10:22 ` Sabau, Radu bogdan
2026-10-26 10:50 ` Andy Shevchenko
2026-10-30 14:06 ` Nuno Sá
2026-11-02 8:04 ` Sabau, Radu bogdan
2026-10-23 9:30 ` [PATCH v4 6/8] iio: imu: adis16607: Add FIFO-based buffered/triggered capture Radu Sabau via B4 Relay
2026-10-26 0:09 ` Jonathan Cameron
2026-10-27 9:36 ` Sabau, Radu bogdan
2026-11-01 23:50 ` Jonathan Cameron
2026-11-02 0:04 ` Jonathan Cameron
2026-10-30 14:06 ` Nuno Sá
2026-11-02 8:08 ` Sabau, Radu bogdan
2026-11-02 10:59 ` Nuno Sá [this message]
2026-10-23 9:30 ` [PATCH v4 7/8] iio: imu: adis16607: Add external clock sync support Radu Sabau via B4 Relay
2026-10-26 0:11 ` Jonathan Cameron
2026-10-26 10:54 ` Sabau, Radu bogdan
2026-10-30 14:06 ` Nuno Sá
2026-10-23 9:30 ` [PATCH v4 8/8] iio: imu: adis16607: Add calibration bias support for gyro/accel Radu Sabau via B4 Relay
2026-10-26 0:15 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=auhszHAlMwT6WW2H@nsa \
--to=nuno.sa@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=radu.sabau@analog.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®