From: Harini Katakam <harinik@xilinx.com>
To: linus.walleij@linaro.org, gnurou@gmail.com,
michal.simek@xilinx.com, grant.likely@linaro.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rob@landley.net
Cc: linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, michals@xilinx.com,
Harini Katakam <harinik@xilinx.com>
Subject: [PATCH 2/2] Devicetree: Add Zynq GPIO devicetree bindings documentation
Date: Thu, 27 Mar 2014 20:55:06 +0530 [thread overview]
Message-ID: <1395933906-2268-2-git-send-email-harinik@xilinx.com> (raw)
In-Reply-To: <1395933906-2268-1-git-send-email-harinik@xilinx.com>
Add gpio-zynq bindings documentation.
Signed-off-by: Harini Katakam <harinik@xilinx.com>
---
.../devicetree/bindings/gpio/gpio-zynq.txt | 24 ++++++++++++++++++++
1 file changed, 24 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-zynq.txt
diff --git a/Documentation/devicetree/bindings/gpio/gpio-zynq.txt b/Documentation/devicetree/bindings/gpio/gpio-zynq.txt
new file mode 100644
index 0000000..1b6e83f
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/gpio-zynq.txt
@@ -0,0 +1,24 @@
+Xilinx Zynq GPIO controller Device Tree Bindings
+-------------------------------------------
+
+Required properties:
+- #gpio-cells : Should be two. First cell is used to mention
+ pin number.
+- compatible : Should be "xlnx,zynq-gpio-1.0"
+- clocks : Clock phandles (see clock bindings for details)
+- gpio-controller : Marks the device node as a GPIO controller.
+- interrupts : Property with a value describing the interrupt
+ number.
+- interrupt-parent : Must be core interrupt controller
+- reg : Address and length of the register set for the device
+
+Example:
+ gpio@e000a000 {
+ #gpio-cells = <2>;
+ compatible = "xlnx,zynq-gpio-1.0";
+ clocks = <&clkc 42>;
+ gpio-controller ;
+ interrupt-parent = <&intc>;
+ interrupts = <0 20 4>;
+ reg = <0xe000a000 0x1000>;
+ } ;
--
1.7.9.5
next prev parent reply other threads:[~2014-03-27 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 15:25 [PATCH 1/2] GPIO: Add driver for Zynq GPIO controller Harini Katakam
2014-03-27 15:25 ` Harini Katakam [this message]
2014-03-28 21:51 ` [PATCH 2/2] Devicetree: Add Zynq GPIO devicetree bindings documentation Linus Walleij
2014-03-28 21:50 ` [PATCH 1/2] GPIO: Add driver for Zynq GPIO controller Linus Walleij
2014-03-29 4:44 ` Harini Katakam
[not found] ` <CAFcVECJsEp_s2V5=oK_UJahGRUpWYWMCxTMxqdpX+O0qebP41A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-31 8:22 ` Linus Walleij
2014-04-02 5:56 ` Michal Simek
2014-04-10 17:52 ` Linus Walleij
2014-04-11 6:57 ` Michal Simek
2014-03-31 9:23 ` Ulf Hansson
2014-04-07 19:00 ` Sören Brinkmann
2014-04-10 17:54 ` Linus Walleij
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=1395933906-2268-2-git-send-email-harinik@xilinx.com \
--to=harinik@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=michals@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--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).