From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Stefan Popa <stefan.popa@analog.com>,
Alexandru Ardelean <alexandru.Ardelean@analog.com>
Cc: linux-iio@vger.kernel.org, kernel@pengutronix.de
Subject: [RFC PATCH v2 1/3] iio: adc: ltc2496: provide device tree binding document
Date: Thu, 14 Nov 2019 11:51:57 +0100 [thread overview]
Message-ID: <20191114105159.14195-2-u.kleine-koenig@pengutronix.de> (raw)
In-Reply-To: <20191114105159.14195-1-u.kleine-koenig@pengutronix.de>
The ADC only requires the standard stuff for spi devices and a reference
voltage.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
Hello,
I didn't say anything about stuff like spi-max-frequency, spi-cpha etc
and even reg because I wonder if there is something I can write into the
document to just reference the generic spi device binding. So I marked
as RFC.
Best regards
Uwe
.../bindings/iio/adc/lltc,ltc2496.yaml | 30 +++++++++++++++++++
1 file changed, 30 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/adc/lltc,ltc2496.yaml
diff --git a/Documentation/devicetree/bindings/iio/adc/lltc,ltc2496.yaml b/Documentation/devicetree/bindings/iio/adc/lltc,ltc2496.yaml
new file mode 100644
index 000000000000..e8acab5f04ec
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/adc/lltc,ltc2496.yaml
@@ -0,0 +1,30 @@
+# SPDX-License-Identifier: GPL-2.0
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/adc/lltc,ltc2496.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Linear Technology / Analog Devices LTC2496 ADC
+
+properties:
+ compatible:
+ enum:
+ - lltc,ltc2496
+
+ vref-supply:
+ description: phandle to an external regulator providing the reference voltage
+ allOf:
+ - $ref: /schemas/types.yaml#/definitions/phandle
+
+required:
+ - compatible
+ - vref-supply
+
+examples:
+ - |
+ adc@0 {
+ compatible = "lltc,ltc2496";
+ reg = <0>;
+ vref-supply = <<c249x_reg>;
+ spi-max-frequency = <2000000>;
+ };
--
2.24.0
next prev parent reply other threads:[~2019-11-14 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 10:51 [PATCH v2 0/3] iio: adc: add support for ltc2496 Uwe Kleine-König
2019-11-14 10:51 ` Uwe Kleine-König [this message]
2019-11-14 10:51 ` [PATCH v2 2/3] iio: adc: ltc2497: split protocol independent part in a separate module Uwe Kleine-König
2019-11-16 15:58 ` Jonathan Cameron
2019-11-16 16:00 ` Jonathan Cameron
2019-11-14 10:51 ` [PATCH v2 3/3] iio: adc: new driver to support Linear technology's ltc2496 Uwe Kleine-König
2019-11-16 16:09 ` Jonathan Cameron
2019-11-16 15:31 ` [PATCH v2 0/3] iio: adc: add support for ltc2496 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=20191114105159.14195-2-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.Ardelean@analog.com \
--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=stefan.popa@analog.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;
as well as URLs for NNTP newsgroup(s).