From: John Crispin <blogic@openwrt.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, linux-gpio@vger.kernel.org
Subject: [PATCH 1/5] DT: Add documentation for gpio-rt2880
Date: Fri, 10 Oct 2014 22:28:46 +0200 [thread overview]
Message-ID: <1412972930-16777-1-git-send-email-blogic@openwrt.org> (raw)
Describe gpio-rt2880 binding.
Signed-off-by: John Crispin <blogic@openwrt.org>
Cc: linux-mips@linux-mips.org
Cc: devicetree@vger.kernel.org
Cc: linux-gpio@vger.kernel.org
---
.../devicetree/bindings/gpio/gpio-rt2880.txt | 40 ++++++++++++++++++++
1 file changed, 40 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-rt2880.txt
diff --git a/Documentation/devicetree/bindings/gpio/gpio-rt2880.txt b/Documentation/devicetree/bindings/gpio/gpio-rt2880.txt
new file mode 100644
index 0000000..b4acf02
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/gpio-rt2880.txt
@@ -0,0 +1,40 @@
+Ralink SoC GPIO controller bindings
+
+Required properties:
+- compatible:
+ - "ralink,rt2880-gpio" for Ralink controllers
+- #gpio-cells : Should be two.
+ - first cell is the pin number
+ - second cell is used to specify optional parameters (unused)
+- gpio-controller : Marks the device node as a GPIO controller
+- reg : Physical base address and length of the controller's registers
+- interrupt-parent: phandle to the INTC device node
+- interrupts : Specify the INTC interrupt number
+- ralink,num-gpios : Specify the number of GPIOs
+- ralink,register-map : The register layout depends on the GPIO bank and actual
+ SoC type. Register offsets need to be in this order.
+ [ INT, EDGE, RENA, FENA, DATA, DIR, POL, SET, RESET, TOGGLE ]
+
+Optional properties:
+- ralink,gpio-base : Specify the GPIO chips base number
+
+Example:
+
+ gpio0: gpio@600 {
+ compatible = "ralink,rt5350-gpio", "ralink,rt2880-gpio";
+
+ #gpio-cells = <2>;
+ gpio-controller;
+
+ reg = <0x600 0x34>;
+
+ interrupt-parent = <&intc>;
+ interrupts = <6>;
+
+ ralink,gpio-base = <0>;
+ ralink,num-gpios = <24>;
+ ralink,register-map = [ 00 04 08 0c
+ 20 24 28 2c
+ 30 34 ];
+
+ };
--
1.7.10.4
next reply other threads:[~2014-10-10 20:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 20:28 John Crispin [this message]
2014-10-10 20:28 ` [PATCH 2/5] GPIO: MIPS: ralink: add gpio driver for ralink rt2880 SoC John Crispin
2014-10-20 4:41 ` Alexandre Courbot
2014-10-20 5:27 ` John Crispin
2014-10-20 6:19 ` Alexandre Courbot
2014-10-28 9:39 ` Linus Walleij
2014-10-10 20:28 ` [PATCH 3/5] DT: Add documentation for gpio-mt7621 John Crispin
2014-10-28 9:37 ` Linus Walleij
2014-10-10 20:28 ` [PATCH 4/5] GPIO: MIPS: ralink: add gpio driver for ralink MT762x SoC John Crispin
2014-10-20 4:57 ` Alexandre Courbot
2014-10-20 5:31 ` John Crispin
2014-10-20 6:27 ` Alexandre Courbot
2014-10-28 9:44 ` Linus Walleij
2014-10-10 20:28 ` [PATCH 5/5] MIPS: ralink: we require gpiolib John Crispin
2014-10-27 16:42 ` Linus Walleij
2014-10-27 16:41 ` [PATCH 1/5] DT: Add documentation for gpio-rt2880 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=1412972930-16777-1-git-send-email-blogic@openwrt.org \
--to=blogic@openwrt.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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).