From: Jonathan Cameron <jic23@kernel.org>
To: Radu Sabau via B4 Relay <devnull+radu.sabau.analog.com@kernel.org>
Cc: radu.sabau@analog.com, "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
"Conor Dooley" <conor.dooley@microchip.com>
Subject: Re: [PATCH v8 0/6] iio: adc: ad4691: add driver for AD4691 multichannel SAR ADC family
Date: Sat, 25 Apr 2026 19:31:52 +0100 [thread overview]
Message-ID: <20260425193152.38f80bf1@jic23-huawei> (raw)
In-Reply-To: <20260416-ad4692-multichannel-sar-adc-driver-v8-0-c415bd048fa3@analog.com>
On Thu, 16 Apr 2026 12:18:45 +0300
Radu Sabau via B4 Relay <devnull+radu.sabau.analog.com@kernel.org> wrote:
> This series adds support for the Analog Devices AD4691 family of
> high-speed, low-power multichannel successive approximation register
> (SAR) ADCs with an SPI-compatible serial interface.
>
> The family includes:
> - AD4691: 16-channel, 500 kSPS
> - AD4692: 16-channel, 1 MSPS
> - AD4693: 8-channel, 500 kSPS
> - AD4694: 8-channel, 1 MSPS
>
> The devices support two operating modes, auto-detected from the device
> tree:
> - CNV Burst Mode: external PWM drives CNV independently of SPI;
> DATA_READY on a GP pin signals end of conversion
> - Manual Mode: CNV tied to SPI CS; each SPI transfer reads
> the previous conversion result and starts the
> next (pipelined N+1 scheme)
>
> A new driver is warranted rather than extending ad4695: the AD4691
> data path uses an accumulator-register model — results are read from
> AVG_IN registers, with ACC_MASK, ADC_SETUP, DEVICE_SETUP, and
> GPIO_MODE registers controlling the sequencer — none of which exist
> in AD4695. CNV Burst Mode (PWM drives CNV independently of SPI) and
> Manual Mode (pipelined N+1 transfers) also have no equivalent in
> AD4695's command-embedded single-cycle protocol.
>
> The series is structured as follows:
> 1/6 - DT bindings (YAML schema) and MAINTAINERS entry
> 2/6 - Initial driver: register map via custom regmap callbacks,
> IIO read_raw/write_raw, both operating modes, single-channel
> reads via internal oscillator (Autonomous Mode)
> 3/6 - Triggered buffer support: IRQ-driven (DATA_READY on a GP pin
> selected via interrupt-names) for CNV Burst Mode; external IIO
> trigger for Manual Mode to handle the pipelined N+1 SPI protocol
> 4/6 - SPI Engine offload support: DMA-backed high-throughput
> capture path using the SPI offload subsystem
> 5/6 - Per-channel oversampling ratio support for CNV Burst Mode
> 6/6 - Driver documentation (Documentation/iio/ad4691.rst)
>
> Datasheets:
> https://www.analog.com/en/products/ad4691.html
> https://www.analog.com/en/products/ad4692.html
> https://www.analog.com/en/products/ad4693.html
> https://www.analog.com/en/products/ad4694.html
>
> Signed-off-by: Radu Sabau <radu.sabau@analog.com>
drivers/iio/adc/ad4691.c: note: in included file:
./include/linux/bitmap.h:845:55: warning: shift too big (64) for type unsigned long
./include/linux/bitmap.h:845:55: warning: shift too big (64) for type unsigned long
./include/linux/bitmap.h:845:55: warning: shift too big (64) for type unsigned long
./include/linux/bitmap.h:845:55: warning: shift too big (64) for type unsigned long
From sparse. I think it's a false positive.
It's the bitmap_read() calls - probably the the nbits parameter.
Using bitmap_read() to copy the whole bitmap is unusual so maybe this is a corner
case that isn't handled.
Any ideas? I'm going to assume it's a false positive due to the ACCESS_PRIVATE()
confusing sparse.
So with that in mind, series applied to the testing branch of iio.git.
thanks,
Jonathan
prev parent reply other threads:[~2026-04-25 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 9:18 [PATCH v8 0/6] iio: adc: ad4691: add driver for AD4691 multichannel SAR ADC family Radu Sabau via B4 Relay
2026-04-16 9:18 ` [PATCH v8 1/6] dt-bindings: iio: adc: add AD4691 family Radu Sabau via B4 Relay
2026-04-16 9:18 ` [PATCH v8 2/6] iio: adc: ad4691: add initial driver for " Radu Sabau via B4 Relay
2026-04-16 9:18 ` [PATCH v8 3/6] iio: adc: ad4691: add triggered buffer support Radu Sabau via B4 Relay
2026-04-25 17:50 ` Jonathan Cameron
2026-04-16 9:18 ` [PATCH v8 4/6] iio: adc: ad4691: add SPI offload support Radu Sabau via B4 Relay
2026-04-25 17:54 ` Jonathan Cameron
2026-04-16 9:18 ` [PATCH v8 5/6] iio: adc: ad4691: add oversampling support Radu Sabau via B4 Relay
2026-04-16 9:18 ` [PATCH v8 6/6] docs: iio: adc: ad4691: add driver documentation Radu Sabau via B4 Relay
2026-04-25 18: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=20260425193152.38f80bf1@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=devnull+radu.sabau.analog.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=p.zabel@pengutronix.de \
--cc=radu.sabau@analog.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=ukleinek@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