From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt@analog.com>
Cc: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<nuno.sa@analog.com>, <dlechner@baylibre.com>, <andy@kernel.org>,
<Michael.Hennerich@analog.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <corbet@lwn.net>,
<marcelo.schmitt1@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: iio: adc: Add AD4134
Date: Sun, 7 Dec 2025 13:22:05 +0000 [thread overview]
Message-ID: <20251207132205.402f36d4@jic23-huawei> (raw)
In-Reply-To: <06d7be2af0f6520c23f612fa0249ff6a26655cb7.1764708608.git.marcelo.schmitt@analog.com>
On Tue, 2 Dec 2025 17:55:03 -0300
Marcelo Schmitt <marcelo.schmitt@analog.com> wrote:
> Add device tree documentation for AD4134 24-Bit, 4-channel simultaneous
> sampling, precision ADC.
>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Marcelo Schmitt <marcelo.schmitt@analog.com>
A few comments inline. Not necessarily anything to change.
Thanks
Jonathan
> ---
> Change log v2 -> v3:
> - fixed typo in powerdown-gpios description.
> - picked up Conor's review tag.
>
> .../bindings/iio/adc/adi,ad4134.yaml | 198 ++++++++++++++++++
> MAINTAINERS | 7 +
> 2 files changed, 205 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad4134.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad4134.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad4134.yaml
> new file mode 100644
> index 000000000000..69a6ddf6ca92
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad4134.yaml
>
> +allOf:
> + - if:
> + not:
> + required:
> + - ldoin-supply
> + then:
> + required:
> + - avdd1v8-supply
> + - dvdd1v8-supply
> + - clkvdd-supply
Conor gave a tag, so I'm sure this is fine, but could we do this as
a oneOf given it's a pick between two options?
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + adc@0 {
> + compatible = "adi,ad4134";
> + reg = <0>;
> +
> + spi-max-frequency = <1000000>;
> +
> + reset-gpios = <&gpio0 86 GPIO_ACTIVE_LOW>;
> + odr-gpios = <&gpio0 87 GPIO_ACTIVE_HIGH>;
> + powerdown-gpios = <&gpio0 88 GPIO_ACTIVE_LOW>;
> +
> + clocks = <&sys_clk>;
> + clock-names = "clkin";
> +
> + avdd5-supply = <&avdd5>;
> + dvdd5-supply = <&dvdd5>;
> + iovdd-supply = <&iovdd>;
> + refin-supply = <&refin>;
> + avdd1v8-supply = <&avdd1v8>;
> + dvdd1v8-supply = <&dvdd1v8>;
> + clkvdd-supply = <&clkvdd>;
> +
> + adi,asrc-mode = "low";
> + adi,dclkio = "in";
> + adi,dclkmode = "gated";
Interesting question on whether it is worth adding properties
to examples if they are set to the defaults. Generally we wouldn't
expect actual DT files to set them. Meh, doesn't matter much to me
either way!
> +
> + regulators {
> + vcm_reg: vcm-output {
> + regulator-name = "ad4134-vcm";
> + };
> + };
> +
> + };
> + };
> +...
next prev parent reply other threads:[~2025-12-07 13:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 20:54 [PATCH v3 0/3] iio: adc: Add AD4134 minimum I/O support Marcelo Schmitt
2025-12-02 20:55 ` [PATCH v3 1/3] dt-bindings: iio: adc: Add AD4134 Marcelo Schmitt
2025-12-05 7:52 ` Tomas Melin
2025-12-05 12:50 ` Marcelo Schmitt
2025-12-07 13:13 ` Jonathan Cameron
2025-12-07 13:22 ` Jonathan Cameron [this message]
2025-12-02 20:55 ` [PATCH v3 2/3] iio: adc: Initial support for AD4134 Marcelo Schmitt
2025-12-02 21:26 ` Andy Shevchenko
2025-12-03 11:02 ` Nuno Sá
2025-12-03 12:59 ` Andy Shevchenko
2025-12-03 14:48 ` Nuno Sá
2025-12-03 14:56 ` Andy Shevchenko
2025-12-04 14:58 ` Marcelo Schmitt
2025-12-07 13:41 ` Jonathan Cameron
2025-12-02 20:55 ` [PATCH v3 3/3] Docs: iio: Add AD4134 Marcelo Schmitt
2025-12-03 11:57 ` Tomas Melin
2025-12-04 15:32 ` Marcelo Schmitt
2025-12-05 7:58 ` Tomas Melin
2025-12-05 12:32 ` Marcelo Schmitt
2025-12-07 13:28 ` 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=20251207132205.402f36d4@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.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;
as well as URLs for NNTP newsgroup(s).