From: Romain Gantois <romain.gantois@bootlin.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "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>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 3/6] iio: add processed write API
Date: Mon, 08 Dec 2025 09:44:48 +0100 [thread overview]
Message-ID: <1942442.tdWV9SEqCh@fw-rgant> (raw)
In-Reply-To: <20251207185216.7498ab0f@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
Hello Jonathan,
On Sunday, 7 December 2025 19:52:16 CET Jonathan Cameron wrote:
> On Mon, 24 Nov 2025 15:48:07 +0100
>
> Romain Gantois <romain.gantois@bootlin.com> 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>
>
> I'm lazy so I'll just ask the question rather than try to find an answer.
> Is there any existing consumer of DAC channels that can use this?
I'm currently considering upstreaming an extension of iio-rescale which
supports writing to the channel. This could be used to represent some frontend
to a DAC output e.g. an OpAmp inverter, which would be useful for my regulator
use case. At first glance, this looks like it could require this processed
write API, but I'm not 100% sure yet.
> It might be easier to land as a refactor than with the new driver and
> reduce what is in the more controversial patch for the regulator.
Agreed. For now, I'll be sidelining the regulator driver and focusing on
upstreaming support for IIO channels with analog front ends, so that there is
at least a way for userspace to directly write the require current/voltage
levels to an IIO channel.
Thanks,
--
Romain Gantois, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-08 8:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 14:48 [PATCH v4 0/6] Add support for the LTM8054 voltage regulator Romain Gantois
2025-11-24 14:48 ` [PATCH v4 1/6] regulator: dt-bindings: Add Linear Technology LTM8054 regulator Romain Gantois
2025-11-24 14:48 ` [PATCH v4 2/6] iio: inkern: Use namespaced exports Romain Gantois
2025-11-24 14:48 ` [PATCH v4 3/6] iio: add processed write API Romain Gantois
2025-12-07 18:52 ` Jonathan Cameron
2025-12-08 8:44 ` Romain Gantois [this message]
2025-11-24 14:48 ` [PATCH v4 4/6] iio: test: Add kunit tests for iio_divide_by_value() Romain Gantois
2025-11-24 14:48 ` [PATCH v4 5/6] regulator: Support the LTM8054 voltage regulator Romain Gantois
2025-11-24 14:48 ` [PATCH v4 6/6] regulator: ltm8054: Support output current limit control Romain Gantois
2025-11-24 14:57 ` [PATCH v4 0/6] Add support for the LTM8054 voltage regulator Guenter Roeck
2025-11-24 15:07 ` Andy Shevchenko
2025-11-24 15:13 ` Romain Gantois
2025-11-24 15:35 ` H. Nikolaus Schaller
2025-11-24 15:57 ` Romain Gantois
2025-11-24 16:19 ` H. Nikolaus Schaller
2025-11-25 8:41 ` Romain Gantois
2025-11-25 10:25 ` H. Nikolaus Schaller
2025-11-25 16:37 ` Guenter Roeck
2025-12-07 18:48 ` Jonathan Cameron
2025-12-08 8:57 ` Romain Gantois
2025-11-27 15:06 ` Romain Gantois
2025-11-25 8:49 ` Romain Gantois
2025-11-24 15:40 ` Guenter Roeck
2025-11-24 16:02 ` 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=1942442.tdWV9SEqCh@fw-rgant \
--to=romain.gantois@bootlin.com \
--cc=andy@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox