From: Krzysztof Kozlowski <krzk@kernel.org>
To: Janani Sunil <janani.sunil@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: iio: dac: Add max22007
Date: Fri, 19 Dec 2025 16:50:47 +0100 [thread overview]
Message-ID: <7ea6cb11-b9a7-4944-bfa1-63c063eb421e@kernel.org> (raw)
In-Reply-To: <20251219-max22007-dev-v1-1-242da2c2b868@analog.com>
On 19/12/2025 16:31, Janani Sunil wrote:
> Devicetree bindings for MAX22007 4-channel
> 12-bit DAC that drives a voltage or current
> output on each channel
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
> Signed-off-by: Janani Sunil <janani.sunil@analog.com>
> ---
> .../devicetree/bindings/iio/dac/adi,max22007.yaml | 116 +++++++++++++++++++++
> MAINTAINERS | 7 ++
> 2 files changed, 123 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/dac/adi,max22007.yaml b/Documentation/devicetree/bindings/iio/dac/adi,max22007.yaml
> new file mode 100644
> index 000000000000..c2f65d9e42d4
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/dac/adi,max22007.yaml
> @@ -0,0 +1,116 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/dac/adi,max22007.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Analog Devices MAX22007 DAC device driver
Bindings are for hardware, drop all device driver references.
> +
> +maintainers:
> + - Janani Sunil <janani.sunil@analog.com>
> +
> +description:
> + The MAX22007 is a quad-channel, 12-bit digital-to-analog converter (DAC)
> + with integrated precision output amplifiers and current output capability.
> + Each channel can be independently configured for voltage or current output.
> + Datasheet available at https://www.analog.com/en/products/max22007.html
> +
> +$ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +properties:
> + compatible:
> + const: adi,max22007
> +
> + reg:
> + maxItems: 1
> +
> + spi-max-frequency:
> + maximum: 500000
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + vdd-supply:
> + description: Low-Voltage Power Supply from +2.7V to +5.5V.
> +
> + hvdd-supply:
> + description:
> + Positive High-Voltage Power Supply from +8V to (HVSS +24V) for
> + the Output Channels.
> +
> + hvss-supply:
> + description:
> + Negative High-Voltage Power Supply from -2V to 0V for the Output Channels.
> +
> + reset-gpios:
> + maxItems: 1
> + description:
> + GPIO used for hardware reset of the device.
Drop description, redundant, because not saying anything other than
schema already said. You could say whether it is active low for example
if you wanted to add something useful.
> +
> +patternProperties:
> + "^channel@[0-3]$":
> + allOf:
> + - $ref: /schemas/iio/dac/dac.yaml#
> + - type: object
Drop allOf. I don't get where did you get this syntax, it's not needed.
> + description:
> + Represents the external channels which are connected to the DAC.
> + Channels not specified in the device tree will be powered off.
> +
> + properties:
> + reg:
> + description: Channel number
> + maxItems: 1
> +
> + adi,type:
> + description: Channel output type.
> + $ref: /schemas/types.yaml#/definitions/string
> + enum: [voltage, current]
Why would it matter if this is voltage or current? That's the first time
this property appears. Why none of existing fit?
> +
> + required:
> + - reg
> + - adi,type
> +
> + unevaluatedProperties: false
> +
> +required:
> + - compatible
> + - reg
> +
> +anyOf:
> + - required: [channel@0]
> + - required: [channel@1]
> + - required: [channel@2]
> + - required: [channel@3]
> +
> +unevaluatedProperties: false
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-19 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 15:31 [PATCH 0/3] Subject: [PATCH v1 0/3] iio: dac: Add support for MAX22007 DAC Janani Sunil
2025-12-19 15:31 ` [PATCH 1/3] dt-bindings: iio: dac: Add max22007 Janani Sunil
2025-12-19 15:50 ` Krzysztof Kozlowski [this message]
2025-12-19 16:40 ` Jonathan Cameron
2025-12-19 15:31 ` [PATCH 2/3] docs: iio: Add documentation for MAX22007 driver Janani Sunil
2025-12-19 16:47 ` Jonathan Cameron
2025-12-19 15:31 ` [PATCH 3/3] iio: dac: Add MAX22007 DAC driver support Janani Sunil
2025-12-19 17:25 ` 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=7ea6cb11-b9a7-4944-bfa1-63c063eb421e@kernel.org \
--to=krzk@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--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=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;
as well as URLs for NNTP newsgroup(s).