From: Conor Dooley <conor@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Kim Seer Paller" <kimseer.paller@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@analog.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: iio: dac: add adi,ad5710r.yaml
Date: Tue, 28 Jul 2026 16:41:26 +0100 [thread overview]
Message-ID: <20260728-selected-pancake-8fa8a066f95d@spud> (raw)
In-Reply-To: <20260724225738.2e090842@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
On Fri, Jul 24, 2026 at 10:57:38PM +0100, Jonathan Cameron wrote:
> On Tue, 21 Jul 2026 16:52:10 +0100
> Conor Dooley <conor@kernel.org> wrote:
>
> > On Tue, Jul 21, 2026 at 04:47:11PM +0800, Kim Seer Paller wrote:
> > > Add device tree bindings for the Analog Devices AD5710R/AD5711R
> > > 8-channel 12-/16-bit Configurable IDAC/VDAC.
> > >
> > > Signed-off-by: Kim Seer Paller <kimseer.paller@analog.com>
> > > ---
> > > .../devicetree/bindings/iio/dac/adi,ad5710r.yaml | 143 +++++++++++++++++++++
> >
> > > +patternProperties:
> > > + "^channel@[0-7]$":
> > > + $ref: /schemas/iio/dac/dac.yaml#
> > > + type: object
> > > + description:
> > > + Represents the external channels which are connected to the DAC.
> > > +
> > > + properties:
> > > + reg:
> > > + description: Channel number
> > > + items:
> > > + minimum: 0
> > > + maximum: 7
> > > +
> > > + adi,ch-func:
> > > + description:
> > > + Channel output type. Use CH_FUNC_VOLTAGE_OUTPUT for voltage
> > > + output or CH_FUNC_CURRENT_OUTPUT for current output.
> > > + $ref: /schemas/types.yaml#/definitions/uint32
> > > + enum: [1, 2]
> >
> > Please make this property a string.
>
> It's an existing binding. I guess it is generic enough that perhaps we
> should make it a generic channel property and as part of that we can
> flip over to a string.
Ah, if it is something already established then it can stay as-is.
> We may need to create a top level channels.yaml to cover both ADC and DAC
> channels though and reference that from both files.
I mean yeah, that was one thought I had originally about the
spi-device-address property. I'm surprised there's already not more
commonality to begin with.
Just how common is some sort of "channel function" property and how
many devices are bastardising other properties like diff-channel with a
virtual channel to achieve the same result?
>
> I guess we don't need to do that yet though given this is a DAC only device.
> The original place we added adi,ch-func is a combined ADC / DAC and
> has a lot more possible functions.
>
> Jonathan
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-28 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 8:47 [PATCH v2 0/4] Add support for AD5710R/AD5711R DAC Kim Seer Paller
2026-07-21 8:47 ` [PATCH v2 1/4] iio: ABI: Add DAC current powerdown attributes and 15kohm_to_gnd mode Kim Seer Paller
2026-07-21 8:47 ` [PATCH v2 2/4] dt-bindings: iio: dac: add adi,ad5710r.yaml Kim Seer Paller
2026-07-21 15:52 ` Conor Dooley
2026-07-24 21:57 ` Jonathan Cameron
2026-07-28 15:41 ` Conor Dooley [this message]
2026-07-24 22:10 ` Jonathan Cameron
2026-07-21 8:47 ` [PATCH v2 3/4] iio: dac: ad3530r: parameterize DAC resolution Kim Seer Paller
2026-07-28 16:40 ` Nuno Sá
2026-07-21 8:47 ` [PATCH v2 4/4] iio: dac: ad3530r: add support for AD5710R/AD5711R Kim Seer Paller
2026-07-21 10:38 ` Andy Shevchenko
2026-07-23 4:54 ` Kim Seer Paller
2026-07-24 22:26 ` 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=20260728-selected-pancake-8fa8a066f95d@spud \
--to=conor@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=kimseer.paller@analog.com \
--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=p.zabel@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