From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Cosmin Tanislav <demonsingur@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-iio <linux-iio@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Cosmin Tanislav <cosmin.tanislav@analog.com>
Subject: Re: [PATCH v7 2/2] iio: adc: ad4130: add AD4130 driver
Date: Tue, 28 Jun 2022 21:17:29 +0200 [thread overview]
Message-ID: <CAHp75Ve6f0dfMmctAwZ3UTA98MDs_injKik2C=wXpJ1zJyiPxA@mail.gmail.com> (raw)
In-Reply-To: <20220628144649.3957286-3-cosmin.tanislav@analog.com>
On Tue, Jun 28, 2022 at 4:49 PM Cosmin Tanislav <demonsingur@gmail.com> wrote:
>
> AD4130-8 is an ultra-low power, high precision, measurement solution for
> low bandwidth battery operated applications.
>
> The fully integrated AFE (Analog Front-End) includes a multiplexer for up
> to 16 single-ended or 8 differential inputs, PGA (Programmable Gain
> Amplifier), 24-bit Sigma-Delta ADC, on-chip reference and oscillator,
> selectable filter options, smart sequencer, sensor biasing and excitation
> options, diagnostics, and a FIFO buffer.
It would be respectful, if you include given tags. Why didn't you do
that? Any significant change that has to be re-reviewed?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-06-28 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 14:46 [PATCH v7 0/2] AD4130 Cosmin Tanislav
2022-06-28 14:46 ` [PATCH v7 1/2] dt-bindings: iio: adc: add AD4130 Cosmin Tanislav
2022-06-29 2:09 ` Rob Herring
2022-06-30 17:12 ` Rob Herring
2022-06-28 14:46 ` [PATCH v7 2/2] iio: adc: ad4130: add AD4130 driver Cosmin Tanislav
2022-06-28 19:17 ` Andy Shevchenko [this message]
2022-06-29 9:28 ` Cosmin Tanislav
2022-06-29 9:41 ` Andy Shevchenko
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='CAHp75Ve6f0dfMmctAwZ3UTA98MDs_injKik2C=wXpJ1zJyiPxA@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=cosmin.tanislav@analog.com \
--cc=demonsingur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.