From: Jonathan Cameron <jic23@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Andy Shevchenko" <andy@kernel.org>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>,
kernel@pengutronix.de, "David Jander" <david@protonic.nl>,
"David Lechner" <dlechner@baylibre.com>
Subject: Re: [PATCH v6 00/12] iio: dac: ds4424: add DS4402/DS4404 support and scale
Date: Thu, 26 Feb 2026 10:08:33 +0000 [thread overview]
Message-ID: <20260226100833.24fa15b5@jic23-huawei> (raw)
In-Reply-To: <aaAHbOVL-83tgIEc@pengutronix.de>
On Thu, 26 Feb 2026 09:42:20 +0100
Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> Hi Jonathan,
>
> Should I resend this patch series?
No need. For future reference I use patchwork.kernel.org to track
status of series. This one is sat there because I need to do a pull
request for the precursor fix (which I'll do shortly). That then needs
to loop around into a suitable upstream tree before I can pick this
series up on top of it.
Thanks,
Jonathan
>
> On Tue, Feb 10, 2026 at 02:50:58PM +0100, Oleksij Rempel wrote:
> > changes v6:
> > - rebase on top of iio/fixes-togreg
> > - drop "iio: dac: ds4424: reject -128 RAW value", already included
> >
> > This series extends the ds4424 IIO DAC driver and its devicetree binding
> > to support the DS4402 and DS4404 current DAC variants.
> >
> > DS440x devices share the same register map as DS442x but use a different
> > resolution (5-bit vs 7-bit) and a different full-scale current formula.
> > The full-scale current depends on external Rfs resistors connected to
> > the FS pins, so a new optional DT property is added to provide the
> > per-channel Rfs values and allow the driver to report a correct IIO
> > SCALE (mA/step).
> >
> > While adding DS440x support, a few related issues were addressed:
> > - Port to regmap
> > - Reject -128 in RAW writes on DS442x, which cannot be represented with
> > sign-magnitude encoding and could silently program an unintended
> > output.
> > - Preserve preconfigured values on probe.
> > - Ratelimit read error logging and use device context.
> >
> > David Jander (1):
> > iio: dac: ds4424: add DS4402/DS4404 device IDs
> >
> > Oleksij Rempel (11):
> > iio: dac: ds4424: refactor raw access to use bitwise operations
> > iio: dac: ds4424: ratelimit read errors and use device context
> > iio: dac: ds4424: sort headers alphabetically
> > iio: dac: ds4424: rename iio_info struct to avoid ambiguity
> > iio: dac: ds4424: use device match data for chip info
> > iio: dac: ds4424: use fsleep() instead of usleep_range()
> > dt-bindings: iio: dac: maxim,ds4424: add ds4402/ds4404
> > iio: dac: ds4424: support per-variant output range limits
> > iio: dac: ds4424: convert to regmap
> > dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property
> > iio: dac: ds4424: add Rfs-based scale and per-variant limits
> >
> > .../bindings/iio/dac/maxim,ds4424.yaml | 42 +-
> > drivers/iio/dac/Kconfig | 1 +
> > drivers/iio/dac/ds4424.c | 375 ++++++++++++------
> > 3 files changed, 287 insertions(+), 131 deletions(-)
> >
> > --
> > 2.47.3
> >
> >
> >
>
next prev parent reply other threads:[~2026-02-26 10:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:50 [PATCH v6 00/12] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-02-10 13:50 ` [PATCH v6 01/12] iio: dac: ds4424: refactor raw access to use bitwise operations Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 02/12] iio: dac: ds4424: ratelimit read errors and use device context Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 03/12] iio: dac: ds4424: sort headers alphabetically Oleksij Rempel
2026-03-22 12:43 ` Jonathan Cameron
2026-02-10 13:51 ` [PATCH v6 04/12] iio: dac: ds4424: rename iio_info struct to avoid ambiguity Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 05/12] iio: dac: ds4424: use device match data for chip info Oleksij Rempel
2026-02-10 14:50 ` Andy Shevchenko
2026-02-10 13:51 ` [PATCH v6 06/12] iio: dac: ds4424: use fsleep() instead of usleep_range() Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 07/12] dt-bindings: iio: dac: maxim,ds4424: add ds4402/ds4404 Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 08/12] iio: dac: ds4424: add DS4402/DS4404 device IDs Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 09/12] iio: dac: ds4424: support per-variant output range limits Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 10/12] iio: dac: ds4424: convert to regmap Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 11/12] dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 12/12] iio: dac: ds4424: add Rfs-based scale and per-variant limits Oleksij Rempel
2026-02-26 8:42 ` [PATCH v6 00/12] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-02-26 10:08 ` Jonathan Cameron [this message]
2026-03-22 12:45 ` Jonathan Cameron
2026-03-22 17:22 ` Oleksij Rempel
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=20260226100833.24fa15b5@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=o.rempel@pengutronix.de \
--cc=robh@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