forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'wireless-drivers-next-for-davem-2016-07-22' of git://git.k…
…ernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next Kalle Valo says: ==================== pull-request: wireless-drivers-next 2016-07-22 I'm sick so I have to keep this short, but here's the last pull request to net-next. This time there's a trivial conflict with mtd tree: http://lkml.kernel.org/g/[email protected] We concluded with Brian (CCed) that it's best that we ask Linus to fix this. The patches have been in linux-next for a couple of days. This time I haven't done any merge tests so I don't know if there are any other conflicts etc. Please let me know if there are any problems. wireless-drivers-next patches for 4.8 Major changes: wl18xx * add initial mesh support bcma * serial flash support on non-MIPS SoCs ath10k * enable support for QCA9888 * disable wake_tx_queue() mac80211 op for older devices to workaround throughput regression ath9k * implement temperature compensation support for AR9003+ ==================== Signed-off-by: David S. Miller <[email protected]>
- Loading branch information
Showing
78 changed files
with
1,178 additions
and
644 deletions.
There are no files selected for viewing
41 changes: 32 additions & 9 deletions
41
Documentation/devicetree/bindings/net/wireless/ti,wlcore,spi.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,36 +1,59 @@ | ||
* Texas Instruments wl1271 wireless lan controller | ||
* Texas Instruments wl12xx/wl18xx wireless lan controller | ||
|
||
The wl1271 chip can be connected via SPI or via SDIO. This | ||
The wl12xx/wl18xx chips can be connected via SPI or via SDIO. This | ||
document describes the binding for the SPI connected chip. | ||
|
||
Required properties: | ||
- compatible : Should be "ti,wl1271" | ||
- compatible : Should be one of the following: | ||
* "ti,wl1271" | ||
* "ti,wl1273" | ||
* "ti,wl1281" | ||
* "ti,wl1283" | ||
* "ti,wl1801" | ||
* "ti,wl1805" | ||
* "ti,wl1807" | ||
* "ti,wl1831" | ||
* "ti,wl1835" | ||
* "ti,wl1837" | ||
- reg : Chip select address of device | ||
- spi-max-frequency : Maximum SPI clocking speed of device in Hz | ||
- ref-clock-frequency : Reference clock frequency | ||
- interrupt-parent, interrupts : | ||
Should contain parameters for 1 interrupt line. | ||
Interrupt parameters: parent, line number, type. | ||
- vwlan-supply : Point the node of the regulator that powers/enable the wl1271 chip | ||
- vwlan-supply : Point the node of the regulator that powers/enable the | ||
wl12xx/wl18xx chip | ||
|
||
Optional properties: | ||
- ref-clock-frequency : Reference clock frequency (should be set for wl12xx) | ||
- clock-xtal : boolean, clock is generated from XTAL | ||
|
||
- Please consult Documentation/devicetree/bindings/spi/spi-bus.txt | ||
for optional SPI connection related properties, | ||
|
||
Examples: | ||
|
||
For wl12xx family: | ||
&spi1 { | ||
wl1271@1 { | ||
wlcore: wlcore@1 { | ||
compatible = "ti,wl1271"; | ||
|
||
reg = <1>; | ||
spi-max-frequency = <48000000>; | ||
clock-xtal; | ||
ref-clock-frequency = <38400000>; | ||
interrupt-parent = <&gpio3>; | ||
interrupts = <8 IRQ_TYPE_LEVEL_HIGH>; | ||
vwlan-supply = <&vwlan_fixed>; | ||
clock-xtal; | ||
ref-clock-frequency = <38400000>; | ||
}; | ||
}; | ||
|
||
For wl18xx family: | ||
&spi0 { | ||
wlcore: wlcore@0 { | ||
compatible = "ti,wl1835"; | ||
reg = <0>; | ||
spi-max-frequency = <48000000>; | ||
interrupt-parent = <&gpio0>; | ||
interrupts = <27 IRQ_TYPE_EDGE_RISING>; | ||
vwlan-supply = <&vwlan_fixed>; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.