public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Ramona Gradinariu <ramona.bolboaca13@gmail.com>
To: linux-kernel@vger.kernel.org, jic23@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
Cc: Ramona Gradinariu <ramona.bolboaca13@gmail.com>
Subject: [PATCH v4 00/10] adis16501 and adis1657x support
Date: Fri, 24 May 2024 12:00:21 +0300	[thread overview]
Message-ID: <20240524090030.336427-1-ramona.bolboaca13@gmail.com> (raw)

Add adis16501 and adis1657x support in adis16475.

Ramona Gradinariu (10):
  dt-bindings: iio: imu: Add ADIS16501 compatibles
  drivers: iio: imu: Add support for ADIS16501
  iio: imu: adis16475: Re-define ADIS16475_DATA
  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                   | 810 +++++++++++++++---
 drivers/iio/imu/adis_buffer.c                 |  32 +-
 drivers/iio/imu/adis_trigger.c                |  37 +-
 include/linux/iio/imu/adis.h                  |  20 +-
 6 files changed, 792 insertions(+), 142 deletions(-)

--
2.34.1


             reply	other threads:[~2024-05-24  9:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  9:00 Ramona Gradinariu [this message]
2024-05-24  9:00 ` [PATCH v4 01/10] dt-bindings: iio: imu: Add ADIS16501 compatibles Ramona Gradinariu
2024-05-24  9:00 ` [PATCH v4 02/10] drivers: iio: imu: Add support for ADIS16501 Ramona Gradinariu
2024-05-24 10:58   ` Nuno Sá
2024-05-24  9:00 ` [PATCH v4 03/10] iio: imu: adis16475: Re-define ADIS16475_DATA Ramona Gradinariu
2024-05-24  9:00 ` [PATCH v4 04/10] iio: imu: adis_buffer: Add buffer setup API with buffer attributes Ramona Gradinariu
2024-05-24 10:58   ` Nuno Sá
2024-05-26 12:38   ` Jonathan Cameron
2024-05-24  9:00 ` [PATCH v4 05/10] iio: imu: adis16475: Create push single sample API Ramona Gradinariu
2024-05-24 10:58   ` Nuno Sá
2024-05-24  9:00 ` [PATCH v4 06/10] drivers: iio: imu: adis16475: generic computation for sample rate Ramona Gradinariu
2024-05-24 10:59   ` Nuno Sá
2024-05-24  9:00 ` [PATCH v4 07/10] iio: imu: adis_trigger: Allow level interrupts for FIFO readings Ramona Gradinariu
2024-05-24 10:59   ` Nuno Sá
2024-05-24  9:00 ` [PATCH v4 08/10] iio: imu: adis16475: Re-define ADIS16475_DATA Ramona Gradinariu
2024-05-24 10:47   ` Nuno Sá
2024-05-26 12:43     ` Jonathan Cameron
2024-05-24  9:00 ` [PATCH v4 09/10] dt-bindings: iio: imu: Add ADIS1657X family devices compatibles Ramona Gradinariu

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=20240524090030.336427-1-ramona.bolboaca13@gmail.com \
    --to=ramona.bolboaca13@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@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=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