From: Jonathan Cameron <jic23@kernel.org>
To: Julien Stephan <jstephan@baylibre.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 2/4] iio: adc: ad7380: fix oversampling formula
Date: Sun, 27 Oct 2024 09:22:17 +0000 [thread overview]
Message-ID: <20241027092217.2d4fbcb9@jic23-huawei> (raw)
In-Reply-To: <20241024-ad7380-add-adaq4380-4-support-v3-2-6a29bd0f79da@baylibre.com>
On Thu, 24 Oct 2024 10:16:57 +0200
Julien Stephan <jstephan@baylibre.com> wrote:
> The formula in the datasheet for oversampling time conversion seems to
> be valid when device is at full speed using the maximum number of SDO
> lines. The driver currently support only 1 SDO line. The formula will
The 'new or corrected' formula I assume not the one in the datasheet?
> produce larger delays than what is currently set, but some devices
> actually require it.
This series is I think backed up behind the fixes chasing through Greg's
trees so I'm being a little fussier than I might otherwise be (when I'd
maybe just change stuff whilst applying and ask you to check the result!)
Code here looks fine, just a comment on the comment dropped.
>
> Signed-off-by: Julien Stephan <jstephan@baylibre.com>
> ---
> drivers/iio/adc/ad7380.c | 19 ++++++++++++++-----
> 1 file changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/iio/adc/ad7380.c b/drivers/iio/adc/ad7380.c
> index fb728570debe6432d5f991595cb35e9e7af8b740..d57e17f38925da5fb7c8a0a2320a21474ba04b37 100644
> --- a/drivers/iio/adc/ad7380.c
> +++ b/drivers/iio/adc/ad7380.c
> @@ -77,6 +77,12 @@
> #define T_CONVERT_X_NS 500 /* xth conversion start time (oversampling) */
> #define T_POWERUP_US 5000 /* Power up */
>
> +/*
> + * AD738x support several SDO lines to increase throughput, but driver currently
> + * supports only 1 SDO line (standard SPI transaction)
> + */
> +#define AD7380_NUM_SDO_LINES 1
> +
> struct ad7380_timing_specs {
> const unsigned int t_csh_ns; /* CS minimum high time */
> };
> @@ -649,7 +655,8 @@ static int ad7380_set_ch(struct ad7380_state *st, unsigned int ch)
>
> if (st->oversampling_ratio > 1)
> xfer.delay.value = T_CONVERT_0_NS +
> - T_CONVERT_X_NS * (st->oversampling_ratio - 1);
> + T_CONVERT_X_NS * (st->oversampling_ratio - 1) *
> + st->chip_info->num_simult_channels / AD7380_NUM_SDO_LINES;
>
> return spi_sync_transfer(st->spi, &xfer, 1);
> }
> @@ -667,12 +674,13 @@ static void ad7380_update_xfers(struct ad7380_state *st,
>
> /*
> * In the case of oversampling, conversion time is higher than in normal
> - * mode. Technically T_CONVERT_X_NS is lower for some chips, but we use
> - * the maximum value for simplicity for now.
> + * mode: t_convert = T_CONVERT_0_NS + T_CONVERT_X_NS*(x - 1)*num_channel/number_of_sdo_lines
> + * where x is the oversampling ratio
Could drop the comment as the code is pretty clear. Is the statement about T_CONVERT_X_NS
being the max value of supported chips worth keeping?
> */
> if (st->oversampling_ratio > 1)
> t_convert = T_CONVERT_0_NS + T_CONVERT_X_NS *
> - (st->oversampling_ratio - 1);
> + (st->oversampling_ratio - 1) *
> + st->chip_info->num_simult_channels / AD7380_NUM_SDO_LINES;
>
> if (st->seq) {
> xfer[0].delay.value = xfer[1].delay.value = t_convert;
> @@ -1021,7 +1029,8 @@ static int ad7380_init(struct ad7380_state *st, bool external_ref_en)
> /* SPI 1-wire mode */
> return regmap_update_bits(st->regmap, AD7380_REG_ADDR_CONFIG2,
> AD7380_CONFIG2_SDO,
> - FIELD_PREP(AD7380_CONFIG2_SDO, 1));
> + FIELD_PREP(AD7380_CONFIG2_SDO,
> + AD7380_NUM_SDO_LINES));
> }
>
> static int ad7380_probe(struct spi_device *spi)
>
next prev parent reply other threads:[~2024-10-27 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 8:16 [PATCH v3 0/4] ad7380: add adaq4370-4 and adaq4380-4 support Julien Stephan
2024-10-24 8:16 ` [PATCH v3 1/4] dt-bindings: iio: adc: ad7380: add adaq4370-4 and adaq4380-4 compatible parts Julien Stephan
2024-10-24 16:41 ` Conor Dooley
2024-10-24 8:16 ` [PATCH v3 2/4] iio: adc: ad7380: fix oversampling formula Julien Stephan
2024-10-27 9:22 ` Jonathan Cameron [this message]
2024-10-24 8:16 ` [PATCH v3 3/4] iio: adc: ad7380: add support for adaq4370-4 and adaq4380-4 Julien Stephan
2024-10-27 9:29 ` Jonathan Cameron
2024-10-24 8:16 ` [PATCH v3 4/4] docs: iio: ad7380: add " Julien Stephan
2024-10-27 9:33 ` Jonathan Cameron
2024-10-27 19:41 ` David Lechner
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=20241027092217.2d4fbcb9@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=jstephan@baylibre.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=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;
as well as URLs for NNTP newsgroup(s).