From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Marcelo Schmitt <marcelo.schmitt@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
nuno.sa@analog.com, dlechner@baylibre.com, andy@kernel.org,
Michael.Hennerich@analog.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, tomas.melin@vaisala.com,
marcelo.schmitt1@gmail.com
Subject: Re: [PATCH v4 2/2] iio: adc: Initial support for AD4134
Date: Sun, 11 Jan 2026 13:31:00 +0000 [thread overview]
Message-ID: <20260111133100.373d9b92@jic23-huawei> (raw)
In-Reply-To: <aV6IP3T3Q3z3aTVa@smile.fi.intel.com>
On Wed, 7 Jan 2026 18:22:23 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Wed, Jan 07, 2026 at 11:47:59AM -0300, Marcelo Schmitt wrote:
> > AD4134 is a 24-bit, 4-channel, simultaneous sampling, precision
> > analog-to-digital converter (ADC). The device can be managed through SPI or
> > direct control of pin logical levels (pin control mode). The AD4134 design
> > also features a dedicated bus for ADC sample data output. Though, this
> > initial driver for AD4134 only supports usual SPI connections.
> >
> > Add basic support for AD4134 that enables single-shot ADC sample read.
>
> I have been on a few weeks leave and do not remember much, but it looks like
> this version has all my previous comments being addressed.
>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
I tweaked to drop the explicit bits.h include and applied to the togreg
branch of iio.git, initially pushed out as testing.
thanks,
Jonathan
>
> ...
>
> > +#include <linux/array_size.h>
> > +#include <linux/bitfield.h>
>
> > +#include <linux/bitops.h>
>
> > +#include <linux/bits.h>
>
> No need, as bitops.h implies (and guarantees) that BIT()/GENMASK() are provided
> with it.
>
> > +#include <linux/clk.h>
> > +#include <linux/crc8.h>
> > +#include <linux/delay.h>
> > +#include <linux/dev_printk.h>
> > +#include <linux/err.h>
> > +#include <linux/export.h>
> > +#include <linux/gpio/consumer.h>
> > +#include <linux/iio/iio.h>
> > +#include <linux/iio/types.h>
> > +#include <linux/module.h>
> > +#include <linux/mod_devicetable.h>
> > +#include <linux/regmap.h>
> > +#include <linux/regulator/consumer.h>
> > +#include <linux/reset.h>
> > +#include <linux/spi/spi.h>
> > +#include <linux/time.h>
> > +#include <linux/types.h>
> > +#include <linux/unaligned.h>
> > +#include <linux/units.h>
>
prev parent reply other threads:[~2026-01-11 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:47 [PATCH v4 0/2] iio: adc: Add AD4134 minimum I/O support Marcelo Schmitt
2026-01-07 14:47 ` [PATCH v4 1/2] dt-bindings: iio: adc: Add AD4134 Marcelo Schmitt
2026-01-07 14:47 ` [PATCH v4 2/2] iio: adc: Initial support for AD4134 Marcelo Schmitt
2026-01-07 16:22 ` Andy Shevchenko
2026-01-11 13:31 ` 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=20260111133100.373d9b92@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--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=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=tomas.melin@vaisala.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