linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <marcelo.schmitt@analog.com>
To: <beniamin.bia@analog.com>, <paul.cercueil@analog.com>,
	<Michael.Hennerich@analog.com>, <lars@metafoo.de>,
	<jic23@kernel.org>, <marcelo.schmitt1@gmail.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/7] Add support for AD7091R-2/-4/-8
Date: Tue, 21 Nov 2023 18:33:49 -0300	[thread overview]
Message-ID: <cover.1700595310.git.marcelo.schmitt1@gmail.com> (raw)

From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>

This series adds support for AD7091R-2/-4/-8 ADCs which can do single shot
or sequenced readings. Threshold events are also supported.
Overall, AD7091R-2/-4/-8 are very similar to AD7091R-5 except they use SPI interface.

This has been tested with raspberrypi and eval board on kernel 6.1 from ADI fork.
Link: https://wiki.analog.com/resources/tools-software/linux-drivers/iio-adc/ad7091r8

Marcelo Schmitt (7):
  iio: adc: ad7091r-base: Set alert config and drvdata
  MAINTAINERS: Add MAINTAINERS entry for AD7091R
  iio: adc: ad7091r: Move defines to header file
  iio: adc: ad7091r: Alloc IIO device before generic probe
  dt-bindings: iio: Add binding documentation for AD7091R-8
  iio: adc: Add support for AD7091R-8
  iio: adc: ad7091r-base: Add debugfs reg access

 .../bindings/iio/adc/adi,ad7091r8.yaml        | 101 +++++++
 MAINTAINERS                                   |  12 +
 drivers/iio/adc/Kconfig                       |  16 ++
 drivers/iio/adc/Makefile                      |   4 +-
 drivers/iio/adc/ad7091r-base.c                |  98 ++++---
 drivers/iio/adc/ad7091r-base.h                |  82 +++++-
 drivers/iio/adc/ad7091r5.c                    |  55 ++--
 drivers/iio/adc/ad7091r8.c                    | 272 ++++++++++++++++++
 8 files changed, 551 insertions(+), 89 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7091r8.yaml
 create mode 100644 drivers/iio/adc/ad7091r8.c

-- 
2.42.0


             reply	other threads:[~2023-11-21 21:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 21:33 marcelo.schmitt [this message]
2023-11-21 21:34 ` [PATCH 1/7] iio: adc: ad7091r-base: Set alert config and drvdata marcelo.schmitt
2023-11-21 21:35 ` [PATCH 2/7] MAINTAINERS: Add MAINTAINERS entry for AD7091R marcelo.schmitt
2023-11-21 21:35 ` [PATCH 3/7] iio: adc: ad7091r: Move defines to header file marcelo.schmitt
2023-11-22 12:40   ` kernel test robot
2023-11-21 21:35 ` [PATCH 4/7] iio: adc: ad7091r: Alloc IIO device before generic probe marcelo.schmitt
2023-11-21 21:36 ` [PATCH 5/7] dt-bindings: iio: Add binding documentation for AD7091R-8 marcelo.schmitt
2023-11-22  9:57   ` Krzysztof Kozlowski
2023-11-22 12:40   ` kernel test robot
2023-11-21 21:36 ` [PATCH 6/7] iio: adc: Add support " marcelo.schmitt
2023-11-22 10:01   ` Krzysztof Kozlowski
2023-11-23  6:30   ` Dan Carpenter
2023-11-21 21:36 ` [PATCH 7/7] iio: adc: ad7091r-base: Add debugfs reg access marcelo.schmitt

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=cover.1700595310.git.marcelo.schmitt1@gmail.com \
    --to=marcelo.schmitt@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=beniamin.bia@analog.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=paul.cercueil@analog.com \
    /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;
as well as URLs for NNTP newsgroup(s).