From: Jonathan Cameron <jic23@kernel.org>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: devicetree@vger.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>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Richard Fontana" <rfontana@redhat.com>,
"Alexios Zavras" <alexios.zavras@intel.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Alexandru Ardelean" <alexandru.ardelean@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>
Subject: Re: [PATCH v4 3/3] iio/dac: convert ltc2632.txt to lltc,ltc2632.yaml
Date: Sat, 18 Apr 2020 16:53:12 +0100 [thread overview]
Message-ID: <20200418165312.5ed6ddb8@archlinux> (raw)
In-Reply-To: <20200416012016.21422-4-chris.ruehl@gtsys.com.hk>
On Thu, 16 Apr 2020 09:20:11 +0800
Chris Ruehl <chris.ruehl@gtsys.com.hk> wrote:
> Conversion of the ltc2632 to yaml format and name the file 'lltc,ltc2632.yaml'.
>
> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
> ---
> V1-V4 patch set, no changes
>
> .../bindings/iio/dac/lltc,ltc2632.yaml | 78 +++++++++++++++++++
> .../devicetree/bindings/iio/dac/ltc2632.txt | 49 ------------
> 2 files changed, 78 insertions(+), 49 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ltc2632.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml b/Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml
> new file mode 100644
> index 000000000000..314bf700d934
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml
> @@ -0,0 +1,78 @@
> +# SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
> +# Copyright 2020 Christopher Ruehl <chris.ruehl@gtsys.com.hk>
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/iio/dac/lltc,ltc2632.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Linear Technology LTC263x 12-/10-/8-Bit Rail-to-Rail DAC
> +
> +maintainers:
> + - Jonathan Cameron <jic23@kernel.org>
Surely we can stich someone at analog up with this one rather than me?
Alex / Michael, who should we land this one on?
> +
> +description: |
> + Bindings for the Linear Technology LTC2632/2634/2636 DAC
> + Datasheet can be found here: https://www.analog.com/media/en/technical-documentation/data-sheets/LTC263[246].pdf
> +
> +properties:
> + compatible:
> + enum:
> + - lltc,ltc2632-l12
> + - lltc,ltc2632-l10
> + - lltc,ltc2632-l8
> + - lltc,ltc2632-h12
> + - lltc,ltc2632-h10
> + - lltc,ltc2632-h8
> + - lltc,ltc2634-l12
> + - lltc,ltc2634-l10
> + - lltc,ltc2634-l8
> + - lltc,ltc2634-h12
> + - lltc,ltc2634-h10
> + - lltc,ltc2634-h8
> + - lltc,ltc2636-l12
> + - lltc,ltc2636-l10
> + - lltc,ltc2636-l8
> + - lltc,ltc2636-h12
> + - lltc,ltc2636-h10
> + - lltc,ltc2636-h8
> +
> + reg:
> + maxItems: 1
> +
> + spi-max-frequency:
> + maximum: 2000000
> +
> + vref-supply:
> + description:
> + Phandle to the external reference voltage supply. This should
> + only be set if there is an external reference voltage connected to the VREF
> + pin. If the property is not set the internal reference is used.
> +
> +required:
> + - compatible
> + - reg
> + - vref-supply
No it isn't. See internal reference comment above...
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + vref: regulator-vref {
> + compatible = "regulator-fixed";
> + regulator-name = "vref-ltc2632";
> + regulator-min-microvolt = <1250000>;
> + regulator-max-microvolt = <1250000>;
> + regulator-always-on;
> + };
> +
> + spi_master {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + dac: ltc2632@0 {
> + compatible = "lltc,ltc2632";
> + reg = <0>; /* CS0 */
> + spi-max-frequency = <1000000>;
> + vref-supply = <&vref>;
> + };
> + };
> diff --git a/Documentation/devicetree/bindings/iio/dac/ltc2632.txt b/Documentation/devicetree/bindings/iio/dac/ltc2632.txt
> deleted file mode 100644
> index 1ab9570cf219..000000000000
> --- a/Documentation/devicetree/bindings/iio/dac/ltc2632.txt
> +++ /dev/null
> @@ -1,49 +0,0 @@
> -Linear Technology LTC2632/2634/2636 DAC
> -
> -Required properties:
> - - compatible: Has to contain one of the following:
> - lltc,ltc2632-l12
> - lltc,ltc2632-l10
> - lltc,ltc2632-l8
> - lltc,ltc2632-h12
> - lltc,ltc2632-h10
> - lltc,ltc2632-h8
> - lltc,ltc2634-l12
> - lltc,ltc2634-l10
> - lltc,ltc2634-l8
> - lltc,ltc2634-h12
> - lltc,ltc2634-h10
> - lltc,ltc2634-h8
> - lltc,ltc2636-l12
> - lltc,ltc2636-l10
> - lltc,ltc2636-l8
> - lltc,ltc2636-h12
> - lltc,ltc2636-h10
> - lltc,ltc2636-h8
> -
> -Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
> -apply. In particular, "reg" and "spi-max-frequency" properties must be given.
> -
> -Optional properties:
> - - vref-supply: Phandle to the external reference voltage supply. This should
> - only be set if there is an external reference voltage connected to the VREF
> - pin. If the property is not set the internal reference is used.
> -
> -Example:
> -
> - vref: regulator-vref {
> - compatible = "regulator-fixed";
> - regulator-name = "vref-ltc2632";
> - regulator-min-microvolt = <1250000>;
> - regulator-max-microvolt = <1250000>;
> - regulator-always-on;
> - };
> -
> - spi_master {
> - dac: ltc2632@0 {
> - compatible = "lltc,ltc2632-l12";
> - reg = <0>; /* CS0 */
> - spi-max-frequency = <1000000>;
> - vref-supply = <&vref>; /* optional */
> - };
> - };
prev parent reply other threads:[~2020-04-18 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 1:20 [PATCH v4] iio: patch set ltc2632 Chris Ruehl
2020-04-16 1:20 ` [PATCH v4 1/3] iio: documentation ltc2632_chip_info add num_channels Chris Ruehl
2020-04-18 15:46 ` Jonathan Cameron
2020-04-16 1:20 ` [PATCH v4 2/3] iio: DAC extension for ltc2634-12/10/8 Chris Ruehl
2020-04-16 6:56 ` Uwe Kleine-König
2020-04-16 7:14 ` Chris Ruehl
2020-04-17 10:27 ` Andy Shevchenko
2020-04-17 10:56 ` Lars-Peter Clausen
2020-04-17 10:57 ` Andy Shevchenko
2020-04-16 1:20 ` [PATCH v4 3/3] iio/dac: convert ltc2632.txt to lltc,ltc2632.yaml Chris Ruehl
2020-04-18 15:53 ` Jonathan Cameron [this message]
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=20200418165312.5ed6ddb8@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=alexios.zavras@intel.com \
--cc=chris.ruehl@gtsys.com.hk \
--cc=devicetree@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=rfontana@redhat.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.