From: Arka Mondal <arka@arkamondal.net>
To: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>
Cc: David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Stefan Popa <stefan.popa@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@analog.com,
arkamondalofficial@gmail.com, Arka Mondal <arka@arkamondal.net>
Subject: [PATCH v2 0/5] iio: dac: ad5758: fix the 4 mA to 20 mA current range
Date: Wed, 7 Oct 2026 00:32:08 +0900 [thread overview]
Message-ID: <20261006153210.364862-1-arka@arkamondal.net> (raw)
These are patches 4 and 5 of the v1 series, with the deprecated
<4 24000> value dropped as Rob Herring <robh@kernel.org> and
Jonathan Cameron <jic23@kernel.org> asked. Patches 1 to 3 are already
applied on togreg and are not resent.
The binding and the driver give the 4 mA to 20 mA range as <4 24000>,
which is 4 uA to 24 mA. The data sheet (Rev. B, Table 32) and the
original text binding say range code 1010 is 4 mA to 20 mA.
Changes since v1:
- binding: replace <4 24000> with <4000 20000>, instead of adding the
correct pair and marking the old one deprecated.
- driver: drop the mapping from <4 24000> to the corrected range.
A device tree that still has <4 24000> now fails the binding check, and
probe stops with "range invalid".
Compile tested only; no relevant hardware available. The binding was
checked with make dt_binding_check and with test device trees:
<4000 20000> is accepted, <4 24000> is now rejected.
Link: https://lore.kernel.org/r/20260918122032.134947-1-arka@arkamondal.net
Arka Mondal (2):
dt-bindings: iio: dac: adi,ad5758: Fix the 4 mA to 20 mA current range
iio: dac: ad5758: Fix the 4 mA to 20 mA current range
Documentation/devicetree/bindings/iio/dac/adi,ad5758.yaml | 4 ++--
drivers/iio/dac/ad5758.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
base-commit: a3b3580713f3ac5a32dc2874ee546828977a1d68
--
2.55.0
next reply other threads:[~2026-10-06 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 15:32 Arka Mondal [this message]
2026-10-06 15:32 ` [PATCH v2 4/5] dt-bindings: iio: dac: adi,ad5758: Fix the 4 mA to 20 mA current range Arka Mondal
2026-10-07 10:24 ` Conor Dooley
2026-10-06 15:32 ` [PATCH v2 5/5] iio: dac: ad5758: " Arka Mondal
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=20261006153210.364862-1-arka@arkamondal.net \
--to=arka@arkamondal.net \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=arkamondalofficial@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=stefan.popa@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