From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>
Cc: Marcelo Schmitt <marcelo.schmitt1@gmail.com>,
antoniu.miclaus@analog.com, lars@metafoo.de,
Michael.Hennerich@analog.com, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] iio: adc: ad4030: fix calibscale read/write unit mismatch
Date: Wed, 25 Feb 2026 17:02:19 +0200 [thread overview]
Message-ID: <aZ8O-zFh38Woy73q@smile.fi.intel.com> (raw)
In-Reply-To: <CAE7dp2rOa4H5yL9qT5kJj3vF3FkNy_sv87Cma9JkgYXGQ5ERWA@mail.gmail.com>
On Wed, Feb 25, 2026 at 04:21:53PM +0400, Giorgi Tchankvetadze wrote:
> Hi Marcelo, Thanks for the pointer to your pending series. As for
> keeping NANO precision, the hardware register is 16-bit with a step of
> 1/0x8000 ≈ 30 µ, so NANO doesn't provide any additional precision that
> the hardware can actually represent. MICRO is sufficient.
>
> Btw, I checked and found that no driver in the entire IIO tree uses
> NANO for calibscale.
> Drivers use either IIO_VAL_INT (raw register value) or IIO_VAL_INT_PLUS_MICRO.
>
> That said, if your series is already adding write_raw_get_fmt(), I'm
> happy to drop this patch and let yours handle it - as long as the
> mismatch gets fixed either way.
- Please, do not top-post!
- Remove context which is unrelated to the replies.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-25 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 11:30 Giorgi Tchankvetadze
2026-02-25 11:53 ` Marcelo Schmitt
2026-02-25 12:21 ` Giorgi Tchankvetadze
2026-02-25 15:02 ` Andy Shevchenko [this message]
2026-02-25 15:20 ` David Lechner
2026-02-26 9:32 ` Nuno Sá
2026-02-28 16:28 ` Jonathan Cameron
2026-02-28 16:27 ` 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=aZ8O-zFh38Woy73q@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=giorgitchankvetadze1997@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=nuno.sa@analog.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®