From: David Lechner <dlechner@baylibre.com>
To: Jonathan Cameron <jic23@kernel.org>,
Jorge Marques <jorge.marques@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH v3 4/8] iio: adc: Add support for ad4052
Date: Mon, 16 Jun 2025 09:54:52 -0500 [thread overview]
Message-ID: <c89f4b2f-0892-4f63-b9b4-5ae55b477c01@baylibre.com> (raw)
In-Reply-To: <20250614110812.39af2c41@jic23-huawei>
On 6/14/25 5:08 AM, Jonathan Cameron wrote:
> On Tue, 10 Jun 2025 09:34:37 +0200
> Jorge Marques <jorge.marques@analog.com> wrote:
>
>> The AD4052/AD4058/AD4050/AD4056 are versatile, 16-bit/12-bit, successive
>> approximation register (SAR) analog-to-digital converter (ADC) that
>> enables low-power, high-density data acquisition solutions without
>> sacrificing precision. This ADC offers a unique balance of performance
>> and power efficiency, plus innovative features for seamlessly switching
>> between high-resolution and low-power modes tailored to the immediate
>> needs of the system. The AD4052/AD4058/AD4050/AD4056 are ideal for
>> battery-powered, compact data acquisition and edge sensing applications.
>>
...
>> +static int ad4052_update_xfer_raw(struct iio_dev *indio_dev,
>> + struct iio_chan_spec const *chan)
>> +{
>> + struct ad4052_state *st = iio_priv(indio_dev);
>> + const struct iio_scan_type *scan_type;
>> + struct spi_transfer *xfer = &st->xfer;
>> +
>> + scan_type = iio_get_current_scan_type(indio_dev, chan);
>> + if (IS_ERR(scan_type))
>> + return PTR_ERR(scan_type);
>> +
>> + xfer->rx_buf = st->raw;
>> + xfer->bits_per_word = scan_type->realbits;
>> + xfer->len = scan_type->realbits == 24 ? 4 : 2;
>
> This is a little odd. I'm not sure what happens with len not dividing
> into a whole number of bits per word chunks.
> Maybe a comment?
Even better, there is now spi_bpw_to_bytes() for this.
>
>> + xfer->speed_hz = AD4052_SPI_MAX_ADC_XFER_SPEED(st->vio_uv);
>> +
>> + return 0;
>> +}
>
>
...
>
>> +static int __ad4052_read_chan_raw(struct ad4052_state *st, int *val)
>> +{
>> + struct spi_device *spi = st->spi;
>> + struct spi_transfer t_cnv = {};
>> + int ret;
>> +
>> + reinit_completion(&st->completion);
>> +
>> + if (st->cnv_gp) {
>> + gpiod_set_value_cansleep(st->cnv_gp, 1);
>> + gpiod_set_value_cansleep(st->cnv_gp, 0);
>> + } else {
>> + ret = spi_sync_transfer(spi, &t_cnv, 1);
>
> Add a comment for this. I can't immediately spot documentation on what
> a content free transfer actually does. I assume pulses the chip select?
> is that true for all SPI controllers?
Should be. Setting .delay in the xfer would also make it more
clear that this is doing.
>
>> + if (ret)
>> + return ret;
>> + }
>> + /*
>> + * Single sample read should be used only for oversampling and
>> + * sampling frequency pairs that take less than 1 sec.
>> + */
>> + if (st->gp1_irq) {
>> + ret = wait_for_completion_timeout(&st->completion,
>> + msecs_to_jiffies(1000));
>> + if (!ret)
>> + return -ETIMEDOUT;
>> + }
>> +
>> + ret = spi_sync_transfer(spi, &st->xfer, 1);
>> + if (ret)
>> + return ret;
>> +
>> + if (st->xfer.len == 2)
>> + *val = sign_extend32(*(u16 *)(st->raw), 15);
>> + else
>> + *val = sign_extend32(*(u32 *)(st->raw), 23);
>> +
>> + return ret;
>> +}
>
...
>> +
>> +static int ad4052_debugfs_reg_access(struct iio_dev *indio_dev, unsigned int reg,
>> + unsigned int writeval, unsigned int *readval)
>> +{
>> + struct ad4052_state *st = iio_priv(indio_dev);
>> + int ret;
>> +
>> + if (!iio_device_claim_direct(indio_dev))
>
> For these guards in the debugfs callback, please add a comment on why they
> are needed. We've had a lot of questions about these recently and I'd
> like it to be clear to people when they should cut and paste these and when
> not.
The reason I started doing this is that running the iio_info command attemps
to read register 0x00 via the debug attribute of every single iio device. So
if you run iio_info during a buffered read, and 0x00 is a valid register, it
would break things without this check.
Ideally, general purpose commands wouldn't be poking debug registers, but
that isn't the case. But I suppose we could "fix" iio_info instead.
>
>> + return -EBUSY;
>> +
>> + if (readval)
>> + ret = regmap_read(st->regmap, reg, readval);
>> + else
>> + ret = regmap_write(st->regmap, reg, writeval);
>> + iio_device_release_direct(indio_dev);
>> + return ret;
>> +}
>
next prev parent reply other threads:[~2025-06-16 14:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 7:34 [PATCH v3 0/8] Add support for AD4052 device family Jorge Marques
2025-06-10 7:34 ` [PATCH v3 1/8] Documentation: ABI: add oversampling frequency in sysfs-bus-iio Jorge Marques
2025-06-11 17:02 ` Jonathan Cameron
2025-06-12 10:10 ` Jorge Marques
2025-06-10 7:34 ` [PATCH v3 2/8] dt-bindings: iio: adc: Add adi,ad4052 Jorge Marques
2025-06-11 17:18 ` Jonathan Cameron
2025-06-12 10:11 ` Jorge Marques
2025-06-12 15:03 ` David Lechner
2025-06-12 19:42 ` Jorge Marques
2025-06-12 20:20 ` David Lechner
2025-06-13 11:17 ` Jorge Marques
2025-06-14 10:14 ` Jonathan Cameron
2025-06-10 7:34 ` [PATCH v3 3/8] docs: iio: New docs for ad4052 driver Jorge Marques
2025-06-10 7:34 ` [PATCH v3 4/8] iio: adc: Add support for ad4052 Jorge Marques
2025-06-14 10:08 ` Jonathan Cameron
2025-06-16 14:54 ` David Lechner [this message]
2025-06-21 16:08 ` Jonathan Cameron
2025-06-21 16:13 ` David Lechner
2025-06-22 14:28 ` Jonathan Cameron
2025-06-17 14:59 ` Uwe Kleine-König
2025-06-17 15:34 ` Jorge Marques
2025-06-18 17:55 ` Uwe Kleine-König
2025-06-10 7:34 ` [PATCH v3 5/8] docs: iio: ad4052: Add offload support documentation Jorge Marques
2025-06-10 7:34 ` [PATCH v3 6/8] iio: adc: Add offload support for ad4052 Jorge Marques
2025-06-14 10:20 ` Jonathan Cameron
2025-06-20 18:52 ` Jorge Marques
2025-06-21 16:16 ` Jonathan Cameron
2025-06-10 7:34 ` [PATCH v3 7/8] docs: iio: ad4052: Add event documentation Jorge Marques
2025-06-10 7:34 ` [PATCH v3 8/8] iio: adc: Add events support to ad4052 Jorge Marques
2025-06-12 19:38 ` David Lechner
2025-06-13 10:02 ` Jorge Marques
2025-06-13 16:03 ` David Lechner
2025-06-14 10:25 ` Jonathan Cameron
2025-06-14 10:40 ` Jonathan Cameron
2025-06-14 10:36 ` Jonathan Cameron
2025-06-16 13:54 ` Jorge Marques
2025-06-21 16:20 ` Jonathan Cameron
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=c89f4b2f-0892-4f63-b9b4-5ae55b477c01@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jorge.marques@analog.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@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=robh@kernel.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
all inboxes | Powered by JetHome®