From: Jonathan Cameron <jic23@kernel.org>
To: Jean-Baptiste Maneyrol via B4 Relay
<devnull+jean-baptiste.maneyrol.tdk.com@kernel.org>
Cc: jean-baptiste.maneyrol@tdk.com,
"Remi Buisson" <remi.buisson@tdk.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: imu: inv_icm45600: fix temperature offset reporting
Date: Sun, 21 Dec 2025 18:41:39 +0000 [thread overview]
Message-ID: <20251221184139.7b253cdd@jic23-huawei> (raw)
In-Reply-To: <20251218-inv-icm45600-fix-temperature-offset-reporting-v1-1-4872f381cbc2@tdk.com>
On Thu, 18 Dec 2025 11:30:59 +0100
Jean-Baptiste Maneyrol via B4 Relay <devnull+jean-baptiste.maneyrol.tdk.com@kernel.org> wrote:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
>
> Correct temperature computation is (raw + offset) * scale and not
> apply scale and offset afterward.
> Fix temperature offset reporting to the correct value and update
> commentaries for the new computation.
>
> Fixes: 27e072bc34d1 ("iio: imu: inv_icm45600: add IMU IIO gyroscope device")
>
No blank line here. That breaks a bunch of scripts and is checked for
in upstream trees so with the line break this would be rejected.
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> Cc: stable@vger.kernel.org
Applied to the fixes-togreg tree.
Thanks,
Jonathan
> ---
> drivers/iio/imu/inv_icm45600/inv_icm45600_core.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/imu/inv_icm45600/inv_icm45600_core.c b/drivers/iio/imu/inv_icm45600/inv_icm45600_core.c
> index ab1cb7b9dba435a3280e50ab77cd16e903c7816c..25bd9757a594d0180d7f53b49f959a49a50c64a9 100644
> --- a/drivers/iio/imu/inv_icm45600/inv_icm45600_core.c
> +++ b/drivers/iio/imu/inv_icm45600/inv_icm45600_core.c
> @@ -960,16 +960,17 @@ int inv_icm45600_temp_read_raw(struct iio_dev *indio_dev,
> return IIO_VAL_INT;
> /*
> * T°C = (temp / 128) + 25
> - * Tm°C = 1000 * ((temp * 100 / 12800) + 25)
> - * scale: 100000 / 13248 = 7.8125
> - * offset: 25000
> + * Tm°C = ((temp + 25 * 128) / 128)) * 1000
> + * Tm°C = (temp + 3200) * (1000 / 128)
> + * scale: 1000 / 128 = 7.8125
> + * offset: 3200
> */
> case IIO_CHAN_INFO_SCALE:
> *val = 7;
> *val2 = 812500;
> return IIO_VAL_INT_PLUS_MICRO;
> case IIO_CHAN_INFO_OFFSET:
> - *val = 25000;
> + *val = 3200;
> return IIO_VAL_INT;
> default:
> return -EINVAL;
>
> ---
> base-commit: a7b10f0963c651a6406d958a5f64b9c5594f84da
> change-id: 20251218-inv-icm45600-fix-temperature-offset-reporting-190a09adfdad
>
> Best regards,
prev parent reply other threads:[~2025-12-21 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 10:30 [PATCH] iio: imu: inv_icm45600: fix temperature offset reporting Jean-Baptiste Maneyrol via B4 Relay
2025-12-21 18:41 ` Jonathan Cameron [this message]
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=20251221184139.7b253cdd@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy@kernel.org \
--cc=devnull+jean-baptiste.maneyrol.tdk.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=remi.buisson@tdk.com \
--cc=stable@vger.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