From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Salah Triki" <salah.triki@gmail.com>,
"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: temperature: max30208: fix wrong scale value
Date: Tue, 28 Apr 2026 18:43:47 +0300 [thread overview]
Message-ID: <afDVs3Zk-pCajNnH@ashevche-desk.local> (raw)
In-Reply-To: <20260428163458.477eda9b@jic23-huawei>
On Tue, Apr 28, 2026 at 04:34:58PM +0100, Jonathan Cameron wrote:
> On Tue, 28 Apr 2026 14:36:00 +0100
> Salah Triki <salah.triki@gmail.com> wrote:
> > On Tue, Apr 28, 2026 at 02:00:48PM +0300, Andy Shevchenko wrote:
> > > On Tue, Apr 28, 2026 at 09:54:15AM +0100, Salah Triki wrote:
...
> > > Isn't it an ABI change?
> >
> > Yes, it technically changes the value exposed to user space. However, the
> > current scale (5) is objectively incorrect according to the datasheet
> > (0.005°C per LSB).
> >
> > With the current scale, a raw reading of 5000 (25°C) is reported as
> > 25000°C by user space tools. This makes the driver practically unusable
> > for standard IIO consumers without custom workarounds. Since the driver is
> > relatively recent, I believe fixing it now to match the hardware
> > specification is preferable to keeping a broken ABI.
>
> Yes. It's fine to fix completely wrong ABI like this. It can get messier
> in more subtle corners but out by a factor of 1000 is an easy one!
>
> > What do you think?
I think you need to write a wrap-up of the above and add to the commit message.
With that it will be justified as far as I am concerned.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-28 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 8:54 [PATCH] iio: temperature: max30208: fix wrong scale value Salah Triki
2026-04-28 11:00 ` Andy Shevchenko
2026-04-28 13:36 ` Salah Triki
2026-04-28 15:34 ` Jonathan Cameron
2026-04-28 15:43 ` Andy Shevchenko [this message]
2026-04-28 15:56 ` Jonathan Cameron
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=afDVs3Zk-pCajNnH@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=nuno.sa@analog.com \
--cc=salah.triki@gmail.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