From: Conor Dooley <conor@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
"Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"David Jander" <david@protonic.nl>
Subject: Re: [PATCH v3 5/8] dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property
Date: Wed, 28 Jan 2026 17:34:20 +0000 [thread overview]
Message-ID: <20260128-relative-wistful-a31575a2fdbc@spud> (raw)
In-Reply-To: <20260128153824.3679187-6-o.rempel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
On Wed, Jan 28, 2026 at 04:38:21PM +0100, Oleksij Rempel wrote:
> The Maxim DS4422/DS4424 and DS4402/DS4404 current DACs determine their
> full-scale output current via external resistors (Rfs) connected to the
> FSx pins. Without knowing these values, the full-scale range of the
> hardware is undefined.
>
> Add the 'maxim,rfs-ohms' property to describe these physical components.
> This property is required to provide a complete description of the
> hardware configuration.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-01-28 17:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 15:38 [PATCH v3 0/8] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-01-28 15:38 ` [PATCH v3 1/8] iio: dac: ds4424: fix -128 rejection and refactor raw access Oleksij Rempel
2026-01-29 17:58 ` Jonathan Cameron
2026-02-01 12:40 ` Oleksij Rempel
2026-02-01 14:42 ` Jonathan Cameron
2026-01-28 15:38 ` [PATCH v3 2/8] iio: dac: ds4424: ratelimit read errors and use device context Oleksij Rempel
2026-01-28 15:38 ` [PATCH v3 3/8] iio: dac: ds4424: sort headers alphabetically Oleksij Rempel
2026-01-28 15:38 ` [PATCH v3 4/8] dt-bindings: iio: dac: maxim,ds4424: add ds4402/ds4404 Oleksij Rempel
2026-01-28 15:38 ` [PATCH v3 5/8] dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property Oleksij Rempel
2026-01-28 17:34 ` Conor Dooley [this message]
2026-01-28 15:38 ` [PATCH v3 6/8] iio: dac: ds4424: add DS4402/DS4404 device IDs Oleksij Rempel
2026-01-31 21:31 ` David Lechner
2026-01-28 15:38 ` [PATCH v3 7/8] iio: dac: ds4424: convert to regmap Oleksij Rempel
2026-01-28 22:17 ` Andy Shevchenko
2026-01-29 18:04 ` Jonathan Cameron
2026-02-01 19:35 ` Sander Vanheule
2026-01-28 15:38 ` [PATCH v3 8/8] iio: dac: ds4424: add Rfs-based scale and per-variant limits Oleksij Rempel
2026-01-29 18:19 ` Jonathan Cameron
2026-01-28 22:19 ` [PATCH v3 0/8] iio: dac: ds4424: add DS4402/DS4404 support and scale Andy Shevchenko
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=20260128-relative-wistful-a31575a2fdbc@spud \
--to=conor@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=jic23@kernel.org \
--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