From: Conor Dooley <conor@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Janani Sunil" <janani.sunil@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
"Janani Sunil" <jan.sun97@gmail.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: dac: Add AD5529R
Date: Mon, 25 May 2026 17:30:02 +0100 [thread overview]
Message-ID: <20260525-dedicator-strut-6f7618a92180@spud> (raw)
In-Reply-To: <20260522180207.63b725fb@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 3127 bytes --]
On Fri, May 22, 2026 at 06:02:07PM +0100, Jonathan Cameron wrote:
> On Tue, 19 May 2026 17:42:58 +0200
> Janani Sunil <janani.sunil@analog.com> wrote:
>
> > Devicetree bindings for AD5529R 16 channel 12/16 bit high voltage,
> > buffered voltage output digital-to-analog converter (DAC) with an
> > integrated precision reference.
>
> Note that I'm seeing this as Changes Requested in the DT-binding patchwork
> but didn't see any replies.
>
> Seems I didn't get the sashiko reply - nor did the IIO patchwork.
> Hopefully Janani did!
> https://patchwork.kernel.org/project/devicetree/patch/20260519-ad5529r-driver-v3-1-267c0731aa68@analog.com/
The sashiko stuff is per subsystem or something, so dt stuff only goes
to us and the submitters. I think that's kinda stupid but also probably
required to avoid pissing people off. There's quite a bit of noise
generated by it, especially with it repeating the same incorrect stuff
on every version.
>
> >
> > Signed-off-by: Janani Sunil <janani.sunil@analog.com>
> > ---
> > .../devicetree/bindings/iio/dac/adi,ad5529r.yaml | 217 +++++++++++++++++++++
> > MAINTAINERS | 7 +
> > 2 files changed, 224 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/dac/adi,ad5529r.yaml b/Documentation/devicetree/bindings/iio/dac/adi,ad5529r.yaml
> > new file mode 100644
> > index 000000000000..eb66f6ca063d
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/dac/adi,ad5529r.yaml
> > @@ -0,0 +1,217 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/dac/adi,ad5529r.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Analog Devices AD5529R 16-Channel 12/16-bit High Voltage DAC
> > +
> > +maintainers:
> > + - Janani Sunil <janani.sunil@analog.com>
> > +
> > +description: |
> > + The AD5529R is a 16-channel, 12-bit or 16-bit, high voltage, buffered voltage output
>
> Long line. Check the wrap.
>
> > + digital-to-analog converter (DAC) with an integrated precision reference.
> > + The device operates from unipolar and bipolar supplies. It is guaranteed
> > + monotonic and has built-in rail-to-rail output buffers that can source or
> > + sink up to 25mA.
> > +
> > + Specifications:
> > + * 16 independent 12-bit or 16-bit DAC channels
> > + * Independently programmable output ranges: 0V to 5V, 0V to 10V, 0V to 20V,
> > + 0V to 40V, ±5V, ±10V, ±15V, and ±20V
> > + * The device supports SPI communication with Mode 0 and Mode 3.
> > + * 4.096V precision reference, 12ppm/°C maximum
> > + * Built-in function generation: Toggle, Sinusoidal Dither, and Ramp waveforms
> > + * Multiplexer for output voltage, load current sense and die temperature
> > +
> > + Datasheet: https://www.analog.com/media/en/technical-documentation/data-sheets/ad5529r.pdf
> > +
>
> > +patternProperties:
> > + "^channel@([0-9]|1[0-5])$":
>
> Sashiko commented that this should be hex. Why the forcing to decimal?
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-25 16:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 15:42 [PATCH v3 0/2] iio: dac: Add support for AD5529R DAC Janani Sunil
2026-05-19 15:42 ` [PATCH v3 1/2] dt-bindings: iio: dac: Add AD5529R Janani Sunil
2026-05-22 17:02 ` Jonathan Cameron
2026-05-25 16:30 ` Conor Dooley [this message]
2026-05-26 12:35 ` Jonathan Cameron
2026-05-26 13:11 ` Rodrigo Alencar
2026-06-09 14:47 ` Janani Sunil
2026-06-14 19:44 ` Jonathan Cameron
2026-06-19 10:33 ` Janani Sunil
2026-06-19 11:31 ` Nuno Sá
2026-06-19 11:36 ` Conor Dooley
2026-06-19 11:40 ` Conor Dooley
2026-06-19 13:01 ` Nuno Sá
2026-06-19 14:12 ` Conor Dooley
2026-06-19 15:54 ` Nuno Sá
2026-06-21 14:33 ` Jonathan Cameron
2026-06-21 18:35 ` Conor Dooley
2026-05-19 15:42 ` [PATCH v3 2/2] iio: dac: Add AD5529R DAC driver support Janani Sunil
2026-05-22 17:24 ` 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=20260525-dedicator-strut-6f7618a92180@spud \
--to=conor@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jan.sun97@gmail.com \
--cc=janani.sunil@analog.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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