From: Jonathan Cameron <jic23@kernel.org>
To: Julien Stephan <jstephan@baylibre.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"kernel test robot" <lkp@intel.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Conor Dooley" <conor.dooley@microchip.com>,
"Stefan Popa" <stefan.popa@analog.com>
Subject: Re: [PATCH v7 0/7] iio: adc: add new ad7380 driver
Date: Sun, 2 Jun 2024 10:34:28 +0100 [thread overview]
Message-ID: <20240602103428.59608407@jic23-huawei> (raw)
In-Reply-To: <20240528-adding-new-ad738x-driver-v7-0-4cd70a4c12c8@baylibre.com>
On Tue, 28 May 2024 16:20:27 +0200
Julien Stephan <jstephan@baylibre.com> wrote:
> Taking over this series with David Lechner's approval, to add some
> fixes, proper handling of pseudo differential parts and
> some extra commits to add support for 4-channel compatible parts.
>
> Here is David's cover letter:
>
> This series is adding a new driver for the Analog Devices Inc. AD7380,
> AD7381, AD7383, and AD7384 ADCs. These chips are part of a family of
> simultaneous sampling SAR ADCs.
>
> To keep things simple, the initial driver implementation only supports
> the 2/4-channel differential chips listed above. There are also 4-channel
> single-ended chips in the family that can be added later.
>
> Furthermore, the driver is just implementing basic support for capturing
> data. Additional features like interrupts, CRC, etc. can be added later.
>
> This work is being done by BayLibre and on behalf of Analog Devices Inc.
> hence the maintainers are @analog.com.
>
Applied + I'll pick up the series David posted with oversampling support
now I have the precursor! A tiny bit of noise in this one because
of the reordering of the adc/Makefile
Thanks,
prev parent reply other threads:[~2024-06-02 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 14:20 [PATCH v7 0/7] iio: adc: add new ad7380 driver Julien Stephan
2024-05-28 14:20 ` [PATCH v7 1/7] dt-bindings: iio: adc: Add binding for AD7380 ADCs Julien Stephan
2024-05-28 14:20 ` [PATCH v7 2/7] iio: adc: ad7380: new driver " Julien Stephan
2024-05-28 14:20 ` [PATCH v7 3/7] dt-bindings: iio: adc: ad7380: add pseudo-differential parts Julien Stephan
2024-05-28 14:20 ` [PATCH v7 4/7] iio: adc: ad7380: add support for " Julien Stephan
2024-05-28 14:20 ` [PATCH v7 5/7] iio: adc: ad7380: prepare for parts with more channels Julien Stephan
2024-05-28 14:20 ` [PATCH v7 6/7] dt-bindings: iio: adc: ad7380: add support for ad738x-4 4 channels variants Julien Stephan
2024-05-28 14:20 ` [PATCH v7 7/7] " Julien Stephan
2024-06-02 9:34 ` 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=20240602103428.59608407@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jstephan@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=stefan.popa@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