mirror of
https://github.com/openwrt/openwrt.git
synced 2024-12-22 15:02:32 +00:00
103 lines
3.3 KiB
Diff
103 lines
3.3 KiB
Diff
From patchwork Tue Jul 30 20:21:08 2013
|
|
Content-Type: text/plain; charset="utf-8"
|
|
MIME-Version: 1.0
|
|
Content-Transfer-Encoding: 7bit
|
|
Subject: [v3] Documentation: dt: bindings: TI WiLink modules
|
|
From: Luciano Coelho <coelho@ti.com>
|
|
X-Patchwork-Id: 2835914
|
|
Message-Id: <1375215668-29171-1-git-send-email-coelho@ti.com>
|
|
To: <devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>
|
|
Cc: <mturquette@linaro.org>, <mark.rutland@arm.com>, <balbi@ti.com>,
|
|
<grant.likely@linaro.org>, <rob.herring@calxeda.com>,
|
|
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
|
|
<linux-wireless@vger.kernel.org>,
|
|
<linux-arm-kernel@lists.infradead.org>, <tony@atomide.com>,
|
|
<nm@ti.com>, <laurent.pinchart@ideasonboard.com>
|
|
Date: Tue, 30 Jul 2013 23:21:08 +0300
|
|
|
|
Add device tree bindings documentation for the TI WiLink modules.
|
|
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
|
|
modules is supported.
|
|
|
|
Signed-off-by: Luciano Coelho <coelho@ti.com>
|
|
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
|
|
|
|
---
|
|
In v3, use IRQ_TYPE_LEVEL_HIGH in the example, as suggested by Laurent.
|
|
|
|
.../devicetree/bindings/net/wireless/ti-wilink.txt | 68 ++++++++++++++++++++++
|
|
1 file changed, 68 insertions(+)
|
|
create mode 100644 Documentation/devicetree/bindings/net/wireless/ti-wilink.txt
|
|
|
|
--- /dev/null
|
|
+++ b/Documentation/devicetree/bindings/net/wireless/ti-wilink.txt
|
|
@@ -0,0 +1,68 @@
|
|
+TI WiLink Wireless Modules Device Tree Bindings
|
|
+===============================================
|
|
+
|
|
+The WiLink modules provide wireless connectivity, such as WLAN,
|
|
+Bluetooth, FM and NFC.
|
|
+
|
|
+There are several different modules available, which can be grouped by
|
|
+their generation: WiLink6, WiLink7 and WiLink8. WiLink4 is not
|
|
+currently supported with device tree.
|
|
+
|
|
+Currently, only the WLAN portion of the modules is supported with
|
|
+device tree.
|
|
+
|
|
+Required properties:
|
|
+--------------------
|
|
+
|
|
+- compatible: should be "ti,wilink6", "ti,wilink7" or "ti,wilink8"
|
|
+- interrupt-parent: the interrupt controller
|
|
+- interrupts: out-of-band WLAN interrupt
|
|
+ See the interrupt controller's bindings documentation for
|
|
+ detailed definition.
|
|
+
|
|
+Optional properties:
|
|
+--------------------
|
|
+
|
|
+- clocks: list of clocks needed by the chip as follows:
|
|
+
|
|
+ refclock: the internal WLAN reference clock frequency (required for
|
|
+ WiLink6 and WiLink7; not used for WiLink8).
|
|
+
|
|
+ tcxoclock: the internal WLAN TCXO clock frequency (required for
|
|
+ WiLink7 not used for WiLink6 and WiLink8).
|
|
+
|
|
+ The clocks must be defined and named accordingly. For example:
|
|
+
|
|
+ clocks = <&refclock>
|
|
+ clock-names = "refclock";
|
|
+
|
|
+ refclock: refclock {
|
|
+ compatible = "ti,wilink-clock";
|
|
+ #clock-cells = <0>;
|
|
+ clock-frequency = <38400000>;
|
|
+ };
|
|
+
|
|
+ Some modules that contain the WiLink chip provide clocks in the
|
|
+ module itself. In this case, we define a "ti,wilink-clock" as shown
|
|
+ above. But any other clock could in theory be used, so the proper
|
|
+ clock definition should be used.
|
|
+
|
|
+
|
|
+Example:
|
|
+--------
|
|
+
|
|
+Example definition that can be used in OMAP4 Panda:
|
|
+
|
|
+wlan {
|
|
+ compatible = "ti,wilink6";
|
|
+ interrupt-parent = <&gpio2>;
|
|
+ interrupts = <21 IRQ_TYPE_LEVEL_HIGH>; /* gpio line 53 */
|
|
+ clocks = <&refclock>;
|
|
+ clock-names = "refclock";
|
|
+
|
|
+ refclock: refclock {
|
|
+ compatible = "ti,wilink-clock";
|
|
+ #clock-cells = <0>;
|
|
+ clock-frequency = <38400000>;
|
|
+ };
|
|
+};
|