From: Jonathan Cameron <jic23@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Mathias Duckeck <m.duckeck@kunbus.de>,
Phil Elwell <phil@raspberrypi.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: iio: dac: ti-dac082s085: Document new driver
Date: Sat, 21 Oct 2017 20:27:44 +0100 [thread overview]
Message-ID: <20171021202738.13eeb611@archlinux> (raw)
In-Reply-To: <9825941ccc986a7fc45fd49c8c982f5cb935b079.1508232186.git.lukas@wunner.de>
On Tue, 17 Oct 2017 12:42:00 +0200
Lukas Wunner <lukas@wunner.de> wrote:
> Add device tree bindings for Texas Instruments 8/10/12-bit 2/4-channel
> DAC driver.
>
> Cc: Mathias Duckeck <m.duckeck@kunbus.de>
> Acked-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
Applied to the togreg branch of iio.git and pushed out as testing.
Thanks,
Jonathan
> ---
> .../devicetree/bindings/iio/dac/ti-dac082s085.txt | 34 ++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt b/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> new file mode 100644
> index 000000000000..9cb0e10df704
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> @@ -0,0 +1,34 @@
> +Texas Instruments 8/10/12-bit 2/4-channel DAC driver
> +
> +Required properties:
> + - compatible: Must be one of:
> + "ti,dac082s085"
> + "ti,dac102s085"
> + "ti,dac122s085"
> + "ti,dac084s085"
> + "ti,dac104s085"
> + "ti,dac124s085"
> + - reg: Chip select number.
> + - spi-cpha, spi-cpol: SPI mode (0,1) or (1,0) must be used, so specify
> + either spi-cpha or spi-cpol (but not both).
> + - vref-supply: Phandle to the external reference voltage supply.
> +
> +For other required and optional properties of SPI slave nodes please refer to
> +../../spi/spi-bus.txt.
> +
> +Example:
> + vref_2v5_reg: regulator-vref {
> + compatible = "regulator-fixed";
> + regulator-name = "2v5";
> + regulator-min-microvolt = <2500000>;
> + regulator-max-microvolt = <2500000>;
> + regulator-always-on;
> + };
> +
> + dac@0 {
> + compatible = "ti,dac082s085";
> + reg = <0>;
> + spi-max-frequency = <40000000>;
> + spi-cpol;
> + vref-supply = <&vref_2v5_reg>;
> + };
next prev parent reply other threads:[~2017-10-21 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 10:42 [PATCH v2 0/3] Texas Instruments 8/10/12-bit 2/4-channel DAC driver Lukas Wunner
2017-10-17 10:42 ` [PATCH v2 3/3] iio: dac: ti-dac082s085: Read chip spec from device table Lukas Wunner
2017-10-21 19:38 ` Jonathan Cameron
2017-10-17 10:42 ` [PATCH v2 1/3] dt-bindings: iio: dac: ti-dac082s085: Document new driver Lukas Wunner
2017-10-21 19:27 ` Jonathan Cameron [this message]
2017-10-17 10:42 ` [PATCH v2 2/3] iio: dac: Add Texas Instruments 8/10/12-bit 2/4-channel DAC driver Lukas Wunner
2017-10-21 19:33 ` Jonathan Cameron
2017-10-22 9:48 ` Lukas Wunner
2017-10-26 15:35 ` 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=20171021202738.13eeb611@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=m.duckeck@kunbus.de \
--cc=phil@raspberrypi.org \
--cc=pmeerw@pmeerw.net \
/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).