From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Jonathan Corbet" <corbet@lwn.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/5] iio: adc: ad7380: add ad7389-4 support
Date: Mon, 7 Apr 2025 19:46:20 +0100 [thread overview]
Message-ID: <20250407194620.7d5e92df@jic23-huawei> (raw)
In-Reply-To: <20250401-iio-ad7380-add-ad7389-4-v1-0-23d2568aa24f@baylibre.com>
On Tue, 01 Apr 2025 17:50:07 -0500
David Lechner <dlechner@baylibre.com> wrote:
> While developing this driver, we glossed over AD7389-4 since we didn't
> have hardware to test it. However, it should be trivial enough to add
> support without testing. It is basically the same as AD7380-4 but
> instead of no internal reference, it has no external reference. And we
> already have support for chips with internal reference only (ADAQ).
>
> We have the typical DT bindings/driver/documentation patches for it plus
> a few patches to shuffle around the existing code for supporting chips
> with internal-reference-only to make it generic enough to support this
> chip as well.
Series applied to the togreg branch of iio.git (which I just rebased on rc1)
Will initially push out as testing though to let 0-day have a first poke
at it.
Thanks,
Jonathan
>
> ---
> David Lechner (5):
> dt-bindings: iio: adc: ad7380: add AD7389-4
> iio: adc: ad7380: rename internal_ref_only
> iio: adc: ad7380: move internal reference voltage to chip_info
> iio: adc: ad7380: add ad7389-4
> Documentation: iio: ad7380: add AD7389-4
>
> .../devicetree/bindings/iio/adc/adi,ad7380.yaml | 11 +++++
> Documentation/iio/ad7380.rst | 7 +++
> drivers/iio/adc/ad7380.c | 50 +++++++++++++++++++---
> 3 files changed, 61 insertions(+), 7 deletions(-)
> ---
> base-commit: f8ffc92ae9052e6615896052f0c5b808bfc17520
> change-id: 20250401-iio-ad7380-add-ad7389-4-1f6d3d7dc749
>
> Best regards,
prev parent reply other threads:[~2025-04-07 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 22:50 [PATCH 0/5] iio: adc: ad7380: add ad7389-4 support David Lechner
2025-04-01 22:50 ` [PATCH 1/5] dt-bindings: iio: adc: ad7380: add AD7389-4 David Lechner
2025-04-02 8:25 ` Krzysztof Kozlowski
2025-04-02 14:39 ` David Lechner
2025-04-07 6:41 ` Krzysztof Kozlowski
2025-04-07 6:42 ` Krzysztof Kozlowski
2025-04-01 22:50 ` [PATCH 2/5] iio: adc: ad7380: rename internal_ref_only David Lechner
2025-04-03 18:53 ` Nuno Sá
2025-04-01 22:50 ` [PATCH 3/5] iio: adc: ad7380: move internal reference voltage to chip_info David Lechner
2025-04-03 18:56 ` Nuno Sá
2025-04-01 22:50 ` [PATCH 4/5] iio: adc: ad7380: add ad7389-4 David Lechner
2025-04-03 18:57 ` Nuno Sá
2025-04-01 22:50 ` [PATCH 5/5] Documentation: iio: ad7380: add AD7389-4 David Lechner
2025-04-07 18:46 ` 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=20250407194620.7d5e92df@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.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