[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240602120941.34bb294d@jic23-huawei>
Date: Sun, 2 Jun 2024 12:09:41 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Ramona Gradinariu <ramona.bolboaca13@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
devicetree@...r.kernel.org, conor+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, robh@...nel.org, nuno.sa@...log.com
Subject: Re: [PATCH v5 0/9] adis16501 and adis1657x support
On Mon, 27 May 2024 17:26:09 +0300
Ramona Gradinariu <ramona.bolboaca13@...il.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
>
Powered by blists - more mailing lists