From: Luciano Coelho <coelho@ti.com>
To: <tony@atomide.com>, <linux-omap@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-wireless@vger.kernel.org>, <coelho@ti.com>,
<luca@coelho.fi>, <balbi@ti.com>
Subject: [PATCH 2/4] arm: dts: omap4-panda-common: add WiLink6 device tree nodes
Date: Tue, 30 Jul 2013 20:27:26 +0300 [thread overview]
Message-ID: <1375205248-25708-3-git-send-email-coelho@ti.com> (raw)
In-Reply-To: <1375205248-25708-1-git-send-email-coelho@ti.com>
Add the WiLink device tree nodes. On omap4-panda, a WiLink6 module is
connected on MMC5 and a GPIO interrupt is used. The refclock
frequency is 38.4MHz.
Signed-off-by: Luciano Coelho <coelho@ti.com>
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi b/arch/arm/boot/dts/omap4-panda-common.dtsi
index b3f6e1f..77e4a42 100644
--- a/arch/arm/boot/dts/omap4-panda-common.dtsi
+++ b/arch/arm/boot/dts/omap4-panda-common.dtsi
@@ -117,6 +117,20 @@
startup-delay-us = <70000>;
enable-active-high;
};
+
+ wlan {
+ compatible = "ti,wilink6";
+ interrupt-parent = <&gpio2>;
+ interrupts = <21 0x4>; /* gpio line 53, high level triggered */
+ clocks = <&refclock>;
+ clock-names = "refclock";
+
+ refclock: refclock {
+ compatible = "ti,wilink-clock";
+ #clock-cells = <0>;
+ clock-frequency = <38400000>;
+ };
+ };
};
&omap4_pmx_wkup {
--
1.8.3.2
next prev parent reply other threads:[~2013-07-30 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 17:27 [PATCH 0/4] ARM: dts: add WiLink support to panda and omap4-sdp Luciano Coelho
2013-07-30 17:27 ` [PATCH 1/4] ARM: dts: omap4-panda: add MMC5 (WiLink WLAN) configuration Luciano Coelho
2013-07-30 17:27 ` Luciano Coelho [this message]
2013-07-30 17:27 ` [PATCH 3/4] ARM: dts: omap4-sdp: " Luciano Coelho
2013-07-30 17:27 ` [PATCH 4/4] arm: dts: omap4-sdp: add WiLink7 device tree node Luciano Coelho
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=1375205248-25708-3-git-send-email-coelho@ti.com \
--to=coelho@ti.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=tony@atomide.com \
/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