From: Liam Beguin <liambeguin@gmail.com>
To: Peter Rosin <peda@axentia.se>
Cc: jic23@kernel.org, andy.shevchenko@gmail.com, lars@metafoo.de,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v13 08/11] iio: afe: rescale: add RTD temperature sensor support
Date: Wed, 2 Feb 2022 15:56:28 -0500 [thread overview]
Message-ID: <Yfrv/K8ohqTINEED@shaak> (raw)
In-Reply-To: <cb48ec7c-da91-cadd-ee7f-02691671e7be@axentia.se>
Hi Peter,
On Wed, Feb 02, 2022 at 05:58:25PM +0100, Peter Rosin wrote:
> Hi!
>
> On 2022-01-30 17:10, Liam Beguin wrote:
> > An RTD (Resistance Temperature Detector) is a kind of temperature
> > sensor used to get a linear voltage to temperature reading within a
> > give range (usually 0 to 100 degrees Celsius). Common types of RTDs
> > include PT100, PT500, and PT1000.
> >
> > Signed-off-by: Liam Beguin <liambeguin@gmail.com>
> > Reviewed-by: Peter Rosin <peda@axentia.se>
> > ---
-- snip --
> > +
> > + tmp = r0 * iexc * alpha / MEGA;
> > + factor = gcd(tmp, MEGA);
> > + rescale->numerator = MEGA / factor;
> > + rescale->denominator = tmp / factor;
> > +
> > + rescale->offset = -1 * ((r0 * iexc) / MEGA * MILLI);
>
> The inner (unneeded) brackets are not helping with clarifying
> the precedence. The most "problematic" operation is the last
> multiplication inside the outer brackets. Extra brackets are
> more useful like this, methinks:
>
> rescale->offset = -1 * ((r0 * iexc / MEGA) * MILLI);
>
> But, what is more important is that you in v10 had:
>
> rescale->offset = -1 * ((r0 * iexc) / 1000);
>
> What you tricked yourself into writing when you converted to
> these prefix defines is not equivalent. You lose precision.
>
> I.e. dividing by 1000000 and then multiplying by 1000 is not
> the same as dividing directly with 1000. And you know this, but
> didn't notice perhaps exactly because you got yourself entangled
> in prefix macros that blurred the picture?
Apologies for this oversight. Your observation is correct, I looked at
the prefix changes and failed to catch this mistake.
Would you be okay with the following:
rescale->offset = -1 * ((r0 * iexc) / KILO);
This would keep things consistent with what I said here[1].
[1] https://lore.kernel.org/linux-iio/YfmJ3P1gYaEkVjlY@shaak/
> These macros have wasted quite a bit of review time. I'm not
> fully convinced they represent an improvement...
Sorry for the wasted cycles here.
Cheers,
Liam
> Cheers,
> Peter
>
> > +
> > + return 0;
> > +}
> > +
> > enum rescale_variant {
> > CURRENT_SENSE_AMPLIFIER,
> > CURRENT_SENSE_SHUNT,
> > VOLTAGE_DIVIDER,
> > + TEMP_SENSE_RTD,
> > };
> >
> > static const struct rescale_cfg rescale_cfg[] = {
> > @@ -414,6 +456,10 @@ static const struct rescale_cfg rescale_cfg[] = {
> > .type = IIO_VOLTAGE,
> > .props = rescale_voltage_divider_props,
> > },
> > + [TEMP_SENSE_RTD] = {
> > + .type = IIO_TEMP,
> > + .props = rescale_temp_sense_rtd_props,
> > + },
> > };
> >
> > static const struct of_device_id rescale_match[] = {
> > @@ -423,6 +469,8 @@ static const struct of_device_id rescale_match[] = {
> > .data = &rescale_cfg[CURRENT_SENSE_SHUNT], },
> > { .compatible = "voltage-divider",
> > .data = &rescale_cfg[VOLTAGE_DIVIDER], },
> > + { .compatible = "temperature-sense-rtd",
> > + .data = &rescale_cfg[TEMP_SENSE_RTD], },
> > { /* sentinel */ }
> > };
> > MODULE_DEVICE_TABLE(of, rescale_match);
next prev parent reply other threads:[~2022-02-02 20:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 16:10 [PATCH v13 00/11] iio: afe: add temperature rescaling support Liam Beguin
2022-01-30 16:10 ` [PATCH v13 01/11] iio: afe: rescale: expose scale processing function Liam Beguin
2022-01-30 16:10 ` [PATCH v13 02/11] iio: afe: rescale: add INT_PLUS_{MICRO,NANO} support Liam Beguin
2022-02-02 17:04 ` Peter Rosin
2022-02-02 21:13 ` Liam Beguin
2022-01-30 16:10 ` [PATCH v13 03/11] iio: afe: rescale: add offset support Liam Beguin
2022-01-30 16:10 ` [PATCH v13 04/11] iio: afe: rescale: fix accuracy for small fractional scales Liam Beguin
2022-01-30 16:10 ` [PATCH v13 05/11] iio: afe: rescale: reduce risk of integer overflow Liam Beguin
2022-01-30 16:10 ` [PATCH v13 06/11] iio: afe: rescale: make use of units.h Liam Beguin
2022-01-31 14:50 ` Peter Rosin
2022-01-31 15:23 ` Andy Shevchenko
2022-02-01 1:59 ` Peter Rosin
2022-02-01 9:20 ` Andy Shevchenko
2022-02-01 19:28 ` Liam Beguin
2022-02-05 17:54 ` Jonathan Cameron
2022-02-05 18:23 ` Andy Shevchenko
2022-02-07 14:05 ` Liam Beguin
2022-02-07 20:22 ` Jonathan Cameron
2022-01-30 16:10 ` [PATCH v13 07/11] iio: test: add basic tests for the iio-rescale driver Liam Beguin
2022-01-30 16:10 ` [PATCH v13 08/11] iio: afe: rescale: add RTD temperature sensor support Liam Beguin
2022-02-02 16:58 ` Peter Rosin
2022-02-02 20:56 ` Liam Beguin [this message]
2022-01-30 16:10 ` [PATCH v13 09/11] iio: afe: rescale: add temperature transducers Liam Beguin
2022-01-30 16:11 ` [PATCH v13 10/11] dt-bindings: iio: afe: add bindings for temperature-sense-rtd Liam Beguin
2022-01-30 16:11 ` [PATCH v13 11/11] dt-bindings: iio: afe: add bindings for temperature transducers Liam Beguin
2022-01-31 11:06 ` [PATCH v13 00/11] iio: afe: add temperature rescaling support Andy Shevchenko
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=Yfrv/K8ohqTINEED@shaak \
--to=liambeguin@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@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).