devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolaus Schulz <nikolaus.schulz@avionic-design.de>
To: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Nikolaus Schulz <nikolaus.schulz@avionic-design.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Alban Bedel <alban.bedel@avionic-design.de>
Subject: [PATCH v2 1/2] iio: document ti-dac8554 devicetree bindings
Date: Mon, 24 Nov 2014 20:50:11 +0100	[thread overview]
Message-ID: <1416858614-32265-1-git-send-email-nikolaus.schulz@avionic-design.de> (raw)

Signed-off-by: Nikolaus Schulz <nikolaus.schulz@avionic-design.de>
---
 .../devicetree/bindings/iio/dac/ti-dac8554.txt     | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/iio/dac/ti-dac8554.txt

diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac8554.txt b/Documentation/devicetree/bindings/iio/dac/ti-dac8554.txt
new file mode 100644
index 0000000..16f7178
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/ti-dac8554.txt
@@ -0,0 +1,22 @@
+TI DAC8554 Digital to Analog Converter
+
+This driver supports the SPI bus.
+
+Required properties:
+	- compatible: must be "ti,dac8554"
+	- vref-supply: the vref power supply
+	- address: the additional 2-bit chip address
+
+For required properties on SPI, please consult
+Documentation/devicetree/bindings/spi/spi-bus.txt
+
+Example:
+
+	dac8554@0 {
+		compatible = "ti,dac8554";
+		reg = <0>;
+		spi-max-frequency = <50000000>;
+
+		vref-supply = <&vdd_vref>;
+		address = <0>;
+	};
-- 
2.1.3

             reply	other threads:[~2014-11-24 19:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 19:50 Nikolaus Schulz [this message]
2014-11-24 19:50 ` [PATCH v2 2/2] iio: add driver for the TI DAC8554 Nikolaus Schulz
     [not found]   ` <1416858614-32265-2-git-send-email-nikolaus.schulz-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2014-12-06 11:36     ` Hartmut Knaack
     [not found]       ` <5482EA33.7020305-Mmb7MZpHnFY@public.gmane.org>
2014-12-12 11:57         ` Jonathan Cameron
     [not found]           ` <548AD814.2060206-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2014-12-12 16:15             ` Nikolaus Schulz
2014-12-13 11:32         ` Lars-Peter Clausen
2014-12-12 15:58       ` Nikolaus Schulz
     [not found]         ` <20141212155804.GA1142-RM9K5IK7kjJNqqvv04100KcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2014-12-12 18:14           ` Jonathan Cameron
2014-12-13 11:18           ` Hartmut Knaack
     [not found]             ` <548C209A.7000904-Mmb7MZpHnFY@public.gmane.org>
2014-12-13 11:24               ` Hartmut Knaack
2014-12-13 11:25               ` Lars-Peter Clausen
2014-12-15 10:02               ` Nikolaus Schulz
2014-12-13 11:29     ` Lars-Peter Clausen
     [not found]       ` <548C2335.7080301-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2014-12-15 10:22         ` Nikolaus Schulz

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=1416858614-32265-1-git-send-email-nikolaus.schulz@avionic-design.de \
    --to=nikolaus.schulz@avionic-design.de \
    --cc=alban.bedel@avionic-design.de \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).