From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <marc.ferland@gmail.com>
Cc: <lars@metafoo.de>, <Michael.Hennerich@analog.com>,
<jic23@kernel.org>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Marc Ferland <marc.ferland@sonatest.com>
Subject: Re: [PATCH] iio: dac: ad5592r: fix temperature scale
Date: Tue, 30 Apr 2024 14:59:35 +0100 [thread overview]
Message-ID: <20240430145935.0000055d@Huawei.com> (raw)
In-Reply-To: <20240430131330.1555849-1-marc.ferland@sonatest.com>
On Tue, 30 Apr 2024 09:13:30 -0400
marc.ferland@gmail.com wrote:
> From: Marc Ferland <marc.ferland@sonatest.com>
>
> For temperature readings, the remainder is returned as nano Celsius
> _but_ we mark it as IIO_VAL_INT_PLUS_MICRO. This results in incorrect
> temperature reporting through hwmon for example. I have a board here
> which reports the following when running 'sensors':
>
> iio_hwmon-isa-0000
> Adapter: ISA adapter
> temp1: +93.3°C
>
> With the patch applied, it returns the correct temperature:
>
> iio_hwmon-isa-0000
> Adapter: ISA adapter
> temp1: +30.5°C
>
> Signed-off-by: Marc Ferland <marc.ferland@sonatest.com>
IIO temperature units are milli celcius, so I'm not following
the argument here. The driver might be reporting in pico celcius
I suppose? Call out that this is the scale factor though, so
it corresponds to 1LSB hence a small number is certainly plausible..
Reasonable to argue it's taking the integer and dividing by 10^9 hence
INT_PLUS_NANO is the right answer, but it isn't nano celsius.
Jonathan
> ---
> drivers/iio/dac/ad5592r-base.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/dac/ad5592r-base.c b/drivers/iio/dac/ad5592r-base.c
> index 076bc9ecfb49..4763402dbcd6 100644
> --- a/drivers/iio/dac/ad5592r-base.c
> +++ b/drivers/iio/dac/ad5592r-base.c
> @@ -415,7 +415,7 @@ static int ad5592r_read_raw(struct iio_dev *iio_dev,
> s64 tmp = *val * (3767897513LL / 25LL);
> *val = div_s64_rem(tmp, 1000000000LL, val2);
>
> - return IIO_VAL_INT_PLUS_MICRO;
> + return IIO_VAL_INT_PLUS_NANO;
> }
>
> mutex_lock(&st->lock);
>
> base-commit: 98369dccd2f8e16bf4c6621053af7aa4821dcf8e
next prev parent reply other threads:[~2024-04-30 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 13:13 marc.ferland
2024-04-30 13:59 ` Jonathan Cameron [this message]
2024-04-30 14:26 ` Marc Ferland
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=20240430145935.0000055d@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.ferland@gmail.com \
--cc=marc.ferland@sonatest.com \
/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®