From: David Lechner <dlechner@baylibre.com>
To: "Romain Gantois" <romain.gantois@bootlin.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/4] iio: add processed write API
Date: Tue, 16 Sep 2025 14:23:04 -0500 [thread overview]
Message-ID: <decdb75c-b61e-4e0f-bddd-cfc8986f3b6f@baylibre.com> (raw)
In-Reply-To: <20250916-ltm8054-driver-v1-2-fd4e781d33b9@bootlin.com>
On 9/16/25 5:24 AM, Romain Gantois wrote:
> Add a function to allow IIO consumers to write a processed value to a
> channel.
>
> Signed-off-by: Romain Gantois <romain.gantois@bootlin.com>
> ---
> drivers/iio/inkern.c | 99 ++++++++++++++++++++++++++++++++++++++++++++
> include/linux/iio/consumer.h | 17 ++++++++
> 2 files changed, 116 insertions(+)
>
> diff --git a/drivers/iio/inkern.c b/drivers/iio/inkern.c
> index c174ebb7d5e6d183674b7ffb15c4ce0f65fa3aed..6486fdb7c66a4c84312541f0f42cc24469972a9c 100644
> --- a/drivers/iio/inkern.c
> +++ b/drivers/iio/inkern.c
> @@ -598,6 +598,85 @@ int iio_read_channel_average_raw(struct iio_channel *chan, int *val)
> }
> EXPORT_SYMBOL_GPL(iio_read_channel_average_raw);
>
> +static int iio_convert_processed_to_raw_unlocked(struct iio_channel *chan,
> + int processed, int *raw,
> + unsigned int scale)
> +{
> + int scale_type, scale_val, scale_val2;
> + int offset_type, offset_val, offset_val2;
> + s64 tmp_num, tmp_den;
> +
> + scale_type = iio_channel_read(chan, &scale_val, &scale_val2,
> + IIO_CHAN_INFO_SCALE);
> + if (scale_type >= 0) {
> + switch (scale_type) {
> + case IIO_VAL_INT:
> + tmp_num = processed;
> + tmp_den = scale_val;
> + break;
> + case IIO_VAL_INT_PLUS_MICRO:
> + tmp_num = (s64)processed * 1000000LL;
> +
> + if (scale_val2 < 0) {
> + tmp_den = (s64)scale_val * 1000000LL - (s64)scale_val2;
> + tmp_den *= -1;
> + } else {
> + tmp_den = (s64)scale_val * 1000000LL + (s64)scale_val2;
> + }
> +
> + break;
> + case IIO_VAL_INT_PLUS_NANO:
> + tmp_num = (s64)processed * 1000000000LL;
> +
> + if (scale_val2 < 0) {
> + tmp_den = (s64)scale_val * 1000000000LL - (s64)scale_val2;
> + tmp_den *= -1;
> + } else {
> + tmp_den = (s64)scale_val * 1000000000LL + (s64)scale_val2;
> + }
> +
> + break;
> + case IIO_VAL_FRACTIONAL:
> + tmp_num = (s64)processed * (s64)scale_val2;
> + tmp_den = scale_val;
> + break;
> + case IIO_VAL_FRACTIONAL_LOG2:
> + tmp_num = (s64)processed << scale_val2;
> + tmp_den = scale_val;
> + break;
> + default:
> + return -EINVAL;
> + }
> +
> + tmp_den *= scale;
> +
> + *raw = div64_s64(tmp_num, tmp_den);
> + }
It can be quite tricky to get all of these combinations right. I would
prefer if added some unit tests like we did in [1].
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=testing&id=c732e60ee10ed0611a59513cbf9c8d35fbe7cf65
> +
> + offset_type = iio_channel_read(chan, &offset_val, &offset_val2,
> + IIO_CHAN_INFO_OFFSET);
> + if (offset_type >= 0) {
> + switch (offset_type) {
> + case IIO_VAL_INT:
> + case IIO_VAL_INT_PLUS_MICRO:
> + case IIO_VAL_INT_PLUS_NANO:
> + break;
> + case IIO_VAL_FRACTIONAL:
> + offset_val /= offset_val2;
> + break;
> + case IIO_VAL_FRACTIONAL_LOG2:
> + offset_val >>= offset_val2;
> + break;
> + default:
> + return -EINVAL;
> + }
> +
> + *raw -= offset_val;
> + }
> +
> + return 0;
> +}
next prev parent reply other threads:[~2025-09-16 19:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 10:24 [PATCH 0/4] Add support for the LTM8054 voltage regulator Romain Gantois
2025-09-16 10:24 ` [PATCH 1/4] regulator: dt-bindings: Add Linear Technology LTM8054 regulator Romain Gantois
2025-09-16 13:25 ` Rob Herring (Arm)
2025-09-16 19:24 ` David Lechner
2025-09-17 15:51 ` Romain Gantois
2025-09-18 7:30 ` Romain Gantois
2025-09-16 10:24 ` [PATCH 2/4] iio: add processed write API Romain Gantois
2025-09-16 11:19 ` Mark Brown
2025-09-16 13:00 ` Romain Gantois
2025-09-16 13:03 ` Andy Shevchenko
2025-09-16 19:23 ` David Lechner [this message]
2025-09-17 15:46 ` Romain Gantois
2025-09-20 11:56 ` Jonathan Cameron
2025-09-16 10:24 ` [PATCH 3/4] regulator: Support the LTM8054 voltage regulator Romain Gantois
2025-09-16 13:12 ` Andy Shevchenko
2025-09-16 13:20 ` Andy Shevchenko
2025-09-16 14:17 ` Romain Gantois
2025-09-18 9:31 ` Romain Gantois
2025-09-18 19:17 ` Andy Shevchenko
2025-09-19 8:19 ` Romain Gantois
2025-09-16 10:24 ` [PATCH 4/4] regulator: ltm8054: Support output current limit control Romain Gantois
2025-09-16 13:19 ` Andy Shevchenko
2025-09-16 14:27 ` Romain Gantois
2025-09-17 7:02 ` Andy Shevchenko
2025-09-17 7:03 ` Andy Shevchenko
2025-09-25 7:54 ` Romain Gantois
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=decdb75c-b61e-4e0f-bddd-cfc8986f3b6f@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.