Vladimir Kondratiev | 2be7d22 | 2012-12-20 13:13:19 -0800 | [diff] [blame] | 1 | config WIL6210 |
| 2 | tristate "Wilocity 60g WiFi card wil6210 support" |
| 3 | depends on CFG80211 |
| 4 | depends on PCI |
| 5 | default n |
| 6 | ---help--- |
| 7 | This module adds support for wireless adapter based on |
| 8 | wil6210 chip by Wilocity. It supports operation on the |
| 9 | 60 GHz band, covered by the IEEE802.11ad standard. |
| 10 | |
| 11 | http://wireless.kernel.org/en/users/Drivers/wil6210 |
| 12 | |
| 13 | If you choose to build it as a module, it will be called |
| 14 | wil6210 |
| 15 | |
| 16 | config WIL6210_ISR_COR |
| 17 | bool "Use Clear-On-Read mode for ISR registers for wil6210" |
| 18 | depends on WIL6210 |
| 19 | default y |
| 20 | ---help--- |
| 21 | ISR registers on wil6210 chip may operate in either |
| 22 | COR (Clear-On-Read) or W1C (Write-1-to-Clear) mode. |
| 23 | For production code, use COR (say y); is default since |
| 24 | it saves extra target transaction; |
| 25 | For ISR debug, use W1C (say n); is allows to monitor ISR |
| 26 | registers with debugfs. If COR were used, ISR would |
| 27 | self-clear when accessed for debug purposes, it makes |
| 28 | such monitoring impossible. |
| 29 | Say y unless you debug interrupts |