From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "Popa, Stefan Serban" <StefanSerban.Popa@analog.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"jic23@kernel.org" <jic23@kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "kernel@pengutronix.de" <kernel@pengutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 1/3] iio: adc: ltc2496: provide device tree binding document
Date: Tue, 12 Nov 2019 06:57:49 +0000 [thread overview]
Message-ID: <b6ed43afbfb0128301f11198eb83a8f72b7661e9.camel@analog.com> (raw)
In-Reply-To: <20191111214025.18310-1-u.kleine-koenig@pengutronix.de>
On Mon, 2019-11-11 at 22:40 +0100, Uwe Kleine-König wrote:
> The ADC only requires the standard stuff for spi devices and a reference
> voltage.
>
Hey,
Thanks for the patch.
DT bindings must be in YAML format.
But in this case, you can probably extend the existing
"Documentation/devicetree/bindings/iio/adc/ltc2497.txt".
You don't need to create new file altogether.
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> .../devicetree/bindings/iio/adc/ltc2496.txt | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/adc/ltc2496.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/ltc2496.txt
> b/Documentation/devicetree/bindings/iio/adc/ltc2496.txt
> new file mode 100644
> index 000000000000..d44ab45b26ea
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/ltc2496.txt
> @@ -0,0 +1,15 @@
> +* Linear Technology / Analog Devices LTC2496 ADC
> +
> +Required properties:
> + - compatible: Must be "lltc,ltc2496"
> + - vref-supply: The regulator supply for ADC reference voltage
> + - further properties required for spi device nodes according to
> + Documentation/devicetree/bindings/spi/spi-controller.yaml
> +
> +Example:
> + ltc2497: adc@76 {
> + compatible = "lltc,ltc2496";
> + reg = <0>;
> + vref-supply = <<c249x_reg>;
> + spi-max-frequency = <2000000>;
> + };
next prev parent reply other threads:[~2019-11-12 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 21:40 [PATCH 1/3] iio: adc: ltc2496: provide device tree binding document Uwe Kleine-König
2019-11-11 21:40 ` [PATCH 2/3] iio: adc: ltc2497: split channel definition in a separate module Uwe Kleine-König
2019-11-12 7:14 ` Ardelean, Alexandru
2019-11-11 21:40 ` [PATCH 3/3] iio: adc: new driver to support Linear technology's ltc2496 Uwe Kleine-König
2019-11-12 7:54 ` Ardelean, Alexandru
2019-11-12 6:57 ` Ardelean, Alexandru [this message]
2019-11-12 7:04 ` [PATCH 1/3] iio: adc: ltc2496: provide device tree binding document Uwe Kleine-König
2019-11-12 11:56 ` Ardelean, Alexandru
2019-11-16 15: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=b6ed43afbfb0128301f11198eb83a8f72b7661e9.camel@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=StefanSerban.Popa@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).