From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Trevor Gamblin" <tgamblin@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@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>,
"David Lechner" <dlechner@baylibre.com>,
"Uwe Kleine-Konig" <u.kleine-koenig@baylibre.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH RFC 1/3] dt-bindings: iio: adc: add AD762x/AD796x ADCs
Date: Wed, 31 Jul 2024 16:11:45 +0200 [thread overview]
Message-ID: <387b4028-7f8a-46df-a7f1-168d1700074d@kernel.org> (raw)
In-Reply-To: <20240731-ad7625_r1-v1-1-a1efef5a2ab9@baylibre.com>
On 31/07/2024 15:48, Trevor Gamblin wrote:
> This adds a binding specification for the Analog Devices Inc. AD7625,
> AD7626, AD7960, and AD7961 ADCs.
Please do not use "This commit/patch/change", but imperative mood. See
longer explanation here:
https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95
Why this is not ready, but RFC? What exactly needs to be commented here?
>
> Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
> ---
> .../devicetree/bindings/iio/adc/adi,ad7625.yaml | 176 +++++++++++++++++++++
> MAINTAINERS | 9 ++
> 2 files changed, 185 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7625.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad7625.yaml
> new file mode 100644
> index 000000000000..e88db0ac2534
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad7625.yaml
> @@ -0,0 +1,176 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/adc/adi,ad7625.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Analog Devices Fast PulSAR Analog to Digital Converters
> +
> +maintainers:
> + - Michael Hennerich <Michael.Hennerich@analog.com>
> + - Nuno Sá <nuno.sa@analog.com>
> +
> +description: |
> + A family of single channel differential analog to digital converters
> + in a LFCSP package. Note that these bindings are for the device when
> + used with the PulSAR LVDS project:
> + http://analogdevicesinc.github.io/hdl/projects/pulsar_lvds/index.html.
Eh? And what could be other case - used for what? What are the
differences? Why mentioning it?
> +
> + * https://www.analog.com/en/products/ad7625.html
> + * https://www.analog.com/en/products/ad7626.html
> + * https://www.analog.com/en/products/ad7960.html
> + * https://www.analog.com/en/products/ad7961.html
> +
> +properties:
> + compatible:
> + enum:
> + - adi,ad7625
> + - adi,ad7626
> + - adi,ad7960
> + - adi,ad7961
> +
> + vdd1-supply:
> + description: A supply that powers the analog and digital circuitry.
> +
> + vdd2-supply:
> + description: A supply that powers the analog and digital circuitry.
> +
> + vio-supply:
> + description: A supply for the inputs and outputs.
> +
> + ref-supply:
> + description:
> + Voltage regulator for the external reference voltage (REF).
> +
> + refin-supply:
> + description:
> + Voltage regulator for the reference buffer input (REFIN).
> +
> + clocks:
> + description:
> + The clock connected to the CLK pins, gated by the clk_gate PWM.
> + maxItems: 1
> +
> + pwms:
> + maxItems: 2
> +
> + pwm-names:
> + maxItems: 2
> + items:
> + - const: cnv
> + description: PWM connected to the CNV input on the ADC.
> + - const: clk_gate
> + description: PWM that gates the clock connected to the ADC's CLK input.
> +
> + io-backends:
> + description:
> + The AXI ADC IP block connected to the D+/- and DCO+/- lines of the ADC.
> + maxItems: 1
> +
> + adi,en0-always-on:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description:
> + Indicates if EN0 is hard-wired to the high state. If neither this
> + nor en0-gpios are present, then EN0 is hard-wired low.
> +
> + adi,en1-always-on:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description:
> + Indicates if EN1 is hard-wired to the high state. If neither this
> + nor en1-gpios are present, then EN1 is hard-wired low.
> +
> + adi,en2-always-on:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description:
> + Indicates if EN2 is hard-wired to the high state. If neither this
> + nor en2-gpios are present, then EN2 is hard-wired low.
> +
> + adi,en3-always-on:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description:
> + Indicates if EN3 is hard-wired to the high state. If neither this
> + nor en3-gpios are present, then EN3 is hard-wired low.
> +
> + en0-gpios:
> + description:
> + Configurable EN0 pin.
> +
> + en1-gpios:
> + description:
> + Configurable EN1 pin.
> +
> + en2-gpios:
> + description:
> + Configurable EN2 pin.
> +
> + en3-gpios:
> + description:
> + Configurable EN3 pin.
> +
> +required:
> + - compatible
> + - vdd1-supply
> + - vdd2-supply
> + - vio-supply
> + - clocks
> + - pwms
> + - pwm-names
> + - io-backends
> +
> +- if:
> + properties:
I don't think this was ever tested. Please use existing bindings or
example-schema as template.
> + compatible:
> + contains:
> + enum:
> + - adi,ad7625
> + - adi,ad7626
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-31 14:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 13:48 [PATCH RFC 0/3] iio: adc: add new ad7625 driver Trevor Gamblin
2024-07-31 13:48 ` [PATCH RFC 1/3] dt-bindings: iio: adc: add AD762x/AD796x ADCs Trevor Gamblin
2024-07-31 14:11 ` Krzysztof Kozlowski [this message]
2024-07-31 15:22 ` Trevor Gamblin
2024-07-31 16:58 ` Krzysztof Kozlowski
2024-07-31 15:19 ` Rob Herring (Arm)
2024-08-03 14:35 ` Jonathan Cameron
2024-08-06 13:17 ` Trevor Gamblin
2024-08-06 16:57 ` Jonathan Cameron
2024-07-31 13:48 ` [PATCH RFC 2/3] iio: adc: ad7625: add driver Trevor Gamblin
2024-08-03 14:57 ` Jonathan Cameron
2024-07-31 13:48 ` [PATCH RFC 3/3] docs: iio: new docs for ad7625 driver Trevor Gamblin
2024-08-03 15:00 ` Jonathan Cameron
2024-07-31 14:03 ` [PATCH RFC 0/3] iio: adc: add new " Trevor Gamblin
2024-08-03 14: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=387b4028-7f8a-46df-a7f1-168d1700074d@kernel.org \
--to=krzk@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.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=robh@kernel.org \
--cc=tgamblin@baylibre.com \
--cc=u.kleine-koenig@baylibre.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