From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: "Arka Mondal" <arka@arkamondal.net>,
"Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"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>,
linux@analog.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
arkamondalofficial@gmail.com
Subject: Re: [PATCH 0/5] iio: dac: ad5758: fix DMA alignment, raw range, offset and 4-20 mA
Date: Sun, 20 Sep 2026 19:41:07 +0100 [thread overview]
Message-ID: <20260920194107.12173789@jic23-hlaptop> (raw)
In-Reply-To: <5cd6b31da1f8cbd5b004888cb0df22061fe86a2b.camel@gmail.com>
On Fri, 18 Sep 2026 16:22:27 +0100
Nuno Sá <noname.nuno@gmail.com> wrote:
> On Fri, 2026-09-18 at 21:20 +0900, Arka Mondal wrote:
> > The first attempt to send this series on 2026-09-18 was rejected by
> > the kernel.org mail servers, so it did not reach the lists. The patches
> > are unchanged.
> >
> > This series fixes four bugs in the AD5758 driver, all present since
> > commit 28d1a7ac2a0d ("iio: dac: Add AD5758 support"). The last bug
> > takes two patches, one for the binding and one for the driver.
> >
> > Patch 1 marks the SPI receive buffer __aligned(IIO_DMA_MINALIGN), so
> > it no longer shares a cacheline with other driver state. The 2022
> > conversion of IIO drivers to IIO_DMA_MINALIGN only changed existing
> > ____cacheline_aligned markings, and this driver had none.
> >
> > Patch 2 rejects raw values outside 0 to U16_MAX. Writing -1 currently
> > gives full-scale output.
> >
> > Patch 3 fixes the offset for every range that does not start at 0.
> > The +-20 mA range reports -32 instead of -32768.
> >
> > Patches 4 and 5 fix the 4 mA to 20 mA range. The binding and the
> > driver give it 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. The old value is still accepted: the binding marks
> > it deprecated and the driver maps it to the corrected range, so
> > existing device trees keep working.
> >
> > Compile tested only; no relevant hardware available. The binding was
> > checked with make dt_binding_check and with test device trees:
> > <4000 20000> and <4 24000> are accepted; <4 20000> is rejected.
> >
> > Arka Mondal (5):
> > iio: dac: ad5758: Fix alignment for DMA safety
> > iio: dac: ad5758: Reject out-of-range raw values
> > iio: dac: ad5758: Fix the offset calculation
> > 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
> >
> > .../bindings/iio/dac/adi,ad5758.yaml | 4 ++++
> > drivers/iio/dac/ad5758.c | 18 ++++++++++++++----
> > 2 files changed, 18 insertions(+), 4 deletions(-)
> >
> >
> > base-commit: 08df884136f1c1197bab2a27814404fd329d9aac
>
> LGTM,
>
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
Other than the one thing on the dt-binding that is more policy than anything
else these all look good to me. I'll wait for that to resolve though before
picking these up.
Thanks,
Jonathan
next prev parent reply other threads:[~2026-09-20 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 12:20 Arka Mondal
2026-09-18 12:20 ` [PATCH 1/5] iio: dac: ad5758: Fix alignment for DMA safety Arka Mondal
2026-09-18 12:20 ` [PATCH 2/5] iio: dac: ad5758: Reject out-of-range raw values Arka Mondal
2026-09-18 12:20 ` [PATCH 3/5] iio: dac: ad5758: Fix the offset calculation Arka Mondal
2026-09-18 12:20 ` [PATCH 4/5] dt-bindings: iio: dac: adi,ad5758: Fix the 4 mA to 20 mA current range Arka Mondal
2026-09-20 18:39 ` Jonathan Cameron
2026-09-28 19:34 ` Rob Herring
2026-09-18 12:20 ` [PATCH 5/5] iio: dac: ad5758: " Arka Mondal
2026-09-18 15:22 ` [PATCH 0/5] iio: dac: ad5758: fix DMA alignment, raw range, offset and 4-20 mA Nuno Sá
2026-09-20 18:41 ` Jonathan Cameron [this message]
2026-09-27 20:52 ` Jonathan Cameron
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=20260920194107.12173789@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=arka@arkamondal.net \
--cc=arkamondalofficial@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=noname.nuno@gmail.com \
--cc=nuno.sa@analog.com \
--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
all inboxes | Powered by JetHome®