From: Jonathan Cameron <jic23@kernel.org>
To: Radu Sabau via B4 Relay <devnull+radu.sabau.analog.com@kernel.org>
Cc: radu.sabau@analog.com, "Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Robert Budai" <robert.budai@analog.com>,
"Ramona Gradinariu" <ramona.gradinariu@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@analog.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Conor Dooley" <conor.dooley@microchip.com>
Subject: Re: [PATCH v7 0/7] iio: imu: Add support for the ADI ADIS16607
Date: Thu, 19 Nov 2026 03:26:38 +0000 [thread overview]
Message-ID: <20261119032638.4ba84193@jic23-hlaptop> (raw)
In-Reply-To: <20261118-adis16607-v7-0-707609737691@analog.com>
On Wed, 18 Nov 2026 15:17:42 +0200
Radu Sabau via B4 Relay <devnull+radu.sabau.analog.com@kernel.org> wrote:
> This series adds support for the Analog Devices ADIS16607, a precision
> MEMS IMU with triaxial gyroscope, triaxial accelerometer, and
> temperature sensor, communicating over a non-standard SPI Half-Duplex
> protocol.
>
> This version no longer carries the buffered capture. Following the v6
> review, the FIFO support is split out into a follow-up series, which
> will first update adislib's has_fifo handling (keeping the existing
> trigger/current_trigger interface in place) and the adis16475 FIFO
> variants that use it, and then add the adis16607 FIFO on top. The
> devicetree binding still describes the interrupt pin, as it is part of
> the hardware and is what the follow-up uses.
Given changes from the bits I tried to pick up in v6 are minor
and I only had that one really trivial comment, looks like it
is ready to go to me.
Applied to the testing branch of iio.git.
Thanks
Jonathan
prev parent reply other threads:[~2026-11-19 3:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 13:17 Radu Sabau via B4 Relay
2026-11-18 13:17 ` [PATCH v7 1/7] iio: imu: adis: Fix custom reset dispatch in adislib Radu Sabau via B4 Relay
2026-11-18 13:17 ` [PATCH v7 2/7] iio: imu: adis: Add optional self_test callback Radu Sabau via B4 Relay
2026-11-18 13:17 ` [PATCH v7 3/7] iio: imu: adis: Add optional init callback Radu Sabau via B4 Relay
2026-11-18 13:17 ` [PATCH v7 4/7] dt-bindings: iio: imu: Add bindings for ADI ADIS16607 Radu Sabau via B4 Relay
2026-11-18 13:17 ` [PATCH v7 5/7] iio: imu: Add driver for the " Radu Sabau via B4 Relay
2026-11-19 3:24 ` Jonathan Cameron
2026-11-18 13:17 ` [PATCH v7 6/7] iio: imu: adis16607: Add external clock sync support Radu Sabau via B4 Relay
2026-11-18 13:17 ` [PATCH v7 7/7] iio: imu: adis16607: Add calibration bias support for gyro/accel Radu Sabau via B4 Relay
2026-11-19 3:26 ` Jonathan Cameron [this message]
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=20261119032638.4ba84193@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=devnull+radu.sabau.analog.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=nuno.sa@analog.com \
--cc=radu.sabau@analog.com \
--cc=ramona.gradinariu@analog.com \
--cc=robert.budai@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®