From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: <robh@kernel.org>, <krzk+dt@kernel.org>, <nuno.sa@analog.com>,
<conor+dt@kernel.org>, <ukleinek@kernel.org>,
<dragos.bogdan@analog.com>, <linux-iio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pwm@vger.kernel.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 5/6] dt-bindings: iio: adc: add ad4851
Date: Sat, 19 Oct 2024 14:42:01 +0100 [thread overview]
Message-ID: <20241019144201.7f274e09@jic23-huawei> (raw)
In-Reply-To: <20241018104210.51659-5-antoniu.miclaus@analog.com>
On Fri, 18 Oct 2024 13:42:09 +0300
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Add devicetree bindings for ad485x family.
>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
One question inline.
> +examples:
> + - |
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + adc@0{
> + compatible = "adi,ad4858";
> + reg = <0>;
> + spi-max-frequency = <10000000>;
> + vcc-supply = <&vcc>;
> + vdd-supply = <&vdd>;
> + vee-supply = <&vee>;
> + vddh-supply = <&vddh>;
> + vddl-supply = <&vddh>;
I was curious what these supplies are giving h and l naming.
Seems vddh is the supply for an LDO and vddhl is a way of supplying
an alternative 1.8V to the output from that LDO.
Superficially it looks like an either or situation. I'm not that
worried if the binding enforces that detail though it would be nice
to do so. However this example seems misleading as I don't think you
would ever connect them to the same supply.
> + vio-supply = <&vio>;
> + pwms = <&pwm_gen 0 0>;
> + io-backends = <&iio_backend>;
> + };
> + };
> +...
next prev parent reply other threads:[~2024-10-19 13:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 10:42 [PATCH v4 1/6] iio: backend: add API for interface get Antoniu Miclaus
2024-10-18 10:42 ` [PATCH v4 2/6] iio: backend: add support for data size set Antoniu Miclaus
2024-10-18 10:42 ` [PATCH v4 3/6] iio: adc: adi-axi-adc: add interface type Antoniu Miclaus
2024-10-22 21:22 ` David Lechner
2024-10-18 10:42 ` [PATCH v4 4/6] iio: adc: adi-axi-adc: set data format Antoniu Miclaus
2024-10-18 10:42 ` [PATCH v4 5/6] dt-bindings: iio: adc: add ad4851 Antoniu Miclaus
2024-10-19 13:42 ` Jonathan Cameron [this message]
2024-10-18 10:42 ` [PATCH v4 6/6] iio: adc: ad4851: add ad485x driver Antoniu Miclaus
2024-10-19 13:49 ` Jonathan Cameron
2024-10-22 22:28 ` David Lechner
2024-10-22 21:20 ` [PATCH v4 1/6] iio: backend: add API for interface get David Lechner
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=20241019144201.7f274e09@jic23-huawei \
--to=jic23@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dragos.bogdan@analog.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=ukleinek@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