From: Andy Shevchenko <andy@kernel.org>
To: Angelo Dureghello <adureghello@baylibre.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"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>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 3/5] iio: adc: ad7606: add offset and phase calibration support
Date: Thu, 8 May 2025 21:39:38 +0300 [thread overview]
Message-ID: <aBz6am83scKywvkn@smile.fi.intel.com> (raw)
In-Reply-To: <20250508-wip-bl-ad7606-calibration-v4-3-91a3f2837e6b@baylibre.com>
On Thu, May 08, 2025 at 12:06:07PM +0200, Angelo Dureghello wrote:
> From: Angelo Dureghello <adureghello@baylibre.com>
>
> Add support for offset and phase calibration, only for
> devices that support software mode, that are:
>
> ad7606b
> ad7606c-16
> ad7606c-18
...
> +static int ad7606_get_calib_offset(struct ad7606_state *st, int ch, int *val)
> +{
> + int ret;
> +
> + ret = st->bops->reg_read(st, AD7606_CALIB_OFFSET(ch));
> + if (ret < 0)
> + return ret;
> + *val = st->chip_info->calib_offset_avail[0] + ret *
> + st->chip_info->calib_offset_avail[1];
You are too fast with new versions... As I pointed out, this is not a logical
split. My only concern was the column, i.e. to be as
*val = st->chip_info->calib_offset_avail[0] +
ret * st->chip_info->calib_offset_avail[1];
> + return 0;
> +}
...
> + val -= start_val;
> + val /= step_val;
Hmm...
To me the
val = (val - start_val) / step_val;
looks better as it immediately gives an idea of the initial content of the val.
Ideally I would even add a new temporary variable for this, so the operand and
the assignee won't be the same variable.
> + return st->bops->reg_write(st, AD7606_CALIB_OFFSET(ch), val);
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-05-08 18:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 10:06 [PATCH v4 0/5] iio: adc: add ad7606 calibration support Angelo Dureghello
2025-05-08 10:06 ` [PATCH v4 1/5] Documentation: ABI: IIO: add calibconv_delay documentation Angelo Dureghello
2025-05-08 18:35 ` Andy Shevchenko
2025-05-11 15:37 ` Jonathan Cameron
2025-05-08 10:06 ` [PATCH v4 2/5] iio: core: add ADC delay calibration definition Angelo Dureghello
2025-05-08 10:06 ` [PATCH v4 3/5] iio: adc: ad7606: add offset and phase calibration support Angelo Dureghello
2025-05-08 18:39 ` Andy Shevchenko [this message]
2025-05-08 10:06 ` [PATCH v4 4/5] dt-bindings: iio: adc: adi,ad7606: add gain " Angelo Dureghello
2025-05-08 11:11 ` Rob Herring (Arm)
2025-05-08 12:09 ` Angelo Dureghello
2025-05-08 14:48 ` Conor Dooley
2025-05-08 10:06 ` [PATCH v4 5/5] iio: adc: ad7606: " Angelo Dureghello
2025-05-08 19:00 ` Andy Shevchenko
2025-05-19 9:40 ` Angelo Dureghello
2025-05-19 10:14 ` Andy Shevchenko
2025-05-22 12:47 ` Angelo Dureghello
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=aBz6am83scKywvkn@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=adureghello@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--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