From: Jonathan Cameron <jic23@kernel.org>
To: Ramona Gradinariu <ramona.bolboaca13@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
nuno.sa@analog.com
Subject: Re: [PATCH v5 0/9] adis16501 and adis1657x support
Date: Sun, 2 Jun 2024 12:09:41 +0100 [thread overview]
Message-ID: <20240602120941.34bb294d@jic23-huawei> (raw)
In-Reply-To: <20240527142618.275897-1-ramona.bolboaca13@gmail.com>
On Mon, 27 May 2024 17:26:09 +0300
Ramona Gradinariu <ramona.bolboaca13@gmail.com> wrote:
> Add adis16501 and adis1657x support in adis16475.
>
> Ramona Gradinariu (9):
> dt-bindings: iio: imu: Add ADIS16501 compatibles
> drivers: iio: imu: Add support for ADIS16501
> iio: imu: adis_buffer: Add buffer setup API with buffer attributes
> iio: imu: adis16475: Create push single sample API
> drivers: iio: imu: adis16475: generic computation for sample rate
> iio: imu: adis_trigger: Allow level interrupts for FIFO readings
> iio: imu: adis16475: Re-define ADIS16475_DATA
> dt-bindings: iio: imu: Add ADIS1657X family devices compatibles
> drivers: iio: imu: Add support for adis1657x family
>
> .../bindings/iio/imu/adi,adis16475.yaml | 31 +
> drivers/iio/imu/Kconfig | 4 +-
> drivers/iio/imu/adis16475.c | 807 +++++++++++++++---
> drivers/iio/imu/adis_buffer.c | 32 +-
> drivers/iio/imu/adis_trigger.c | 37 +-
> include/linux/iio/imu/adis.h | 21 +-
> 6 files changed, 792 insertions(+), 140 deletions(-)
This seems to be based on a tree that is missing your sync mode fix from
last cycle. I've applied and fixed it up but please check the result.
I also fixed up Dan's report.
Applied to the togreg branch of iio.git and pushed out as testing for
0-day to take a look at it.
Thanks,
Jonathan
>
> --
> 2.34.1
>
prev parent reply other threads:[~2024-06-02 11:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 14:26 [PATCH v5 0/9] adis16501 and adis1657x support Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 1/9] dt-bindings: iio: imu: Add ADIS16501 compatibles Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 2/9] drivers: iio: imu: Add support for ADIS16501 Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 3/9] iio: imu: adis_buffer: Add buffer setup API with buffer attributes Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 4/9] iio: imu: adis16475: Create push single sample API Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 5/9] drivers: iio: imu: adis16475: generic computation for sample rate Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 6/9] iio: imu: adis_trigger: Allow level interrupts for FIFO readings Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 7/9] iio: imu: adis16475: Re-define ADIS16475_DATA Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 8/9] dt-bindings: iio: imu: Add ADIS1657X family devices compatibles Ramona Gradinariu
2024-05-27 14:26 ` [PATCH v5 9/9] drivers: iio: imu: Add support for adis1657x family Ramona Gradinariu
2024-05-29 14:32 ` Dan Carpenter
2024-06-02 11:10 ` Jonathan Cameron
2024-06-02 11:09 ` 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=20240602120941.34bb294d@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ramona.bolboaca13@gmail.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