From: Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>
To: ssantosh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
t-kristo-l0cyMroinI0@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
fcooper-l0cyMroinI0@public.gmane.org,
s-anna-l0cyMroinI0@public.gmane.org,
nsekhar-l0cyMroinI0@public.gmane.org,
j-keerthy-l0cyMroinI0@public.gmane.org
Subject: [PATCH v3 1/2] gpio: davinci: Add keystone-k2g compatible
Date: Wed, 26 Jul 2017 12:15:23 +0530 [thread overview]
Message-ID: <1501051524-5990-1-git-send-email-j-keerthy@ti.com> (raw)
The patch adds keystone-k2g compatible, specific properties and
an example.
Signed-off-by: Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>
---
Changes in v3:
* Added details about family of SoCs corresponding to compatibles.
.../devicetree/bindings/gpio/gpio-davinci.txt | 40 +++++++++++++++++++++-
1 file changed, 39 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/gpio/gpio-davinci.txt b/Documentation/devicetree/bindings/gpio/gpio-davinci.txt
index 5079ba7..fb9efee 100644
--- a/Documentation/devicetree/bindings/gpio/gpio-davinci.txt
+++ b/Documentation/devicetree/bindings/gpio/gpio-davinci.txt
@@ -1,7 +1,10 @@
Davinci/Keystone GPIO controller bindings
Required Properties:
-- compatible: should be "ti,dm6441-gpio", "ti,keystone-gpio"
+- compatible: should be "ti,dm6441-gpio": for Davinci da850 SoCs
+ "ti,keystone-gpio": for Keystone 2 66AK2H/K, 66AK2L,
+ 66AK2E SoCs
+ "ti,keystone-k2g-gpio", "ti,keystone-gpio": for 66AK2G
- reg: Physical base address of the controller and the size of memory mapped
registers.
@@ -26,6 +29,17 @@ The GPIO controller also acts as an interrupt controller. It uses the default
two cells specifier as described in Documentation/devicetree/bindings/
interrupt-controller/interrupts.txt.
+Required Properties specific to keystone-k2g
+
+- clocks: Should contain devices input clock. The first parameter
+ is a handle to k2g_clks. The second parameter is the
+ device ID and the third parameter is the clock ID. One can
+ refer: http://processors.wiki.ti.com/index.php/TISCI#66AK2G02_Data
+
+ Example: <&k2g_clks 0x001c 0x0>;
+
+- clock-names: The driver expects the clock name to be "gpio";
+
Example:
gpio: gpio@1e26000 {
@@ -60,3 +74,27 @@ leds {
...
};
};
+
+Example for keystone-k2g:
+
+gpio0: gpio@2603000 {
+ compatible = "ti,keystone-k2g-gpio", "ti,keystone-gpio";
+ reg = <0x02603000 0x100>;
+ gpio-controller;
+ #gpio-cells = <2>;
+ interrupts = <GIC_SPI 432 IRQ_TYPE_EDGE_RISING>,
+ <GIC_SPI 433 IRQ_TYPE_EDGE_RISING>,
+ <GIC_SPI 434 IRQ_TYPE_EDGE_RISING>,
+ <GIC_SPI 435 IRQ_TYPE_EDGE_RISING>,
+ <GIC_SPI 436 IRQ_TYPE_EDGE_RISING>,
+ <GIC_SPI 437 IRQ_TYPE_EDGE_RISING>,
+ <GIC_SPI 438 IRQ_TYPE_EDGE_RISING>,
+ <GIC_SPI 439 IRQ_TYPE_EDGE_RISING>,
+ <GIC_SPI 440 IRQ_TYPE_EDGE_RISING>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ ti,ngpio = <144>;
+ ti,davinci-gpio-unbanked = <0>;
+ clocks = <&k2g_clks 0x001b 0x0>;
+ clock-names = "gpio";
+};
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-07-26 6:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 6:45 Keerthy [this message]
[not found] ` <1501051524-5990-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2017-07-26 6:45 ` [PATCH v3 2/2] ARM: dts: keystone-k2g-evm: Add gpio nodes Keerthy
2017-07-26 13:03 ` Suman Anna
2017-07-26 13:29 ` Keerthy
[not found] ` <ecb45045-057a-98c1-9c22-bc6c0df6f5bd-l0cyMroinI0@public.gmane.org>
2017-07-26 13:33 ` Russell King - ARM Linux
2017-07-26 13:43 ` Keerthy
2017-07-26 13:00 ` [PATCH v3 1/2] gpio: davinci: Add keystone-k2g compatible Suman Anna
[not found] ` <5aa0d273-8e05-a5ff-7931-b9a94acade36-l0cyMroinI0@public.gmane.org>
2017-07-26 13:27 ` Franklin S Cooper Jr
2017-07-26 13:35 ` Suman Anna
2017-07-26 13:36 ` Keerthy
2017-07-26 14:20 ` Suman Anna
[not found] ` <da92fe60-d70b-6a37-6b88-2ac95dd67b6a-l0cyMroinI0@public.gmane.org>
2017-07-26 18:37 ` Franklin S Cooper Jr
2017-07-31 13:44 ` Keerthy
[not found] ` <90337754-8670-6df7-5421-7100e31755b1-l0cyMroinI0@public.gmane.org>
2017-08-01 6:12 ` Vignesh R
2017-08-01 14:30 ` Suman Anna
2017-08-01 15:49 ` Franklin S Cooper Jr
2017-07-26 13:33 ` Keerthy
2017-08-02 9:29 ` Linus Walleij
2017-08-03 16:17 ` Rob Herring
2017-08-04 4:16 ` Keerthy
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=1501051524-5990-1-git-send-email-j-keerthy@ti.com \
--to=j-keerthy-l0cymroini0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=fcooper-l0cyMroinI0@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nsekhar-l0cyMroinI0@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=s-anna-l0cyMroinI0@public.gmane.org \
--cc=ssantosh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=t-kristo-l0cyMroinI0@public.gmane.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).