| 1 |
# SPDX-License-Identifier: ISC |
| 2 |
config WIL6210 |
| 3 |
tristate "Wilocity 60g WiFi card wil6210 support" |
| 4 |
select WANT_DEV_COREDUMP |
| 5 |
select CRC32 |
| 6 |
depends on CFG80211 |
| 7 |
depends on PCI |
| 8 |
default n |
| 9 |
help |
| 10 |
This module adds support for wireless adapter based on |
| 11 |
wil6210 chip by Wilocity. It supports operation on the |
| 12 |
60 GHz band, covered by the IEEE802.11ad standard. |
| 13 |
|
| 14 |
https://wireless.wiki.kernel.org/en/users/Drivers/wil6210 |
| 15 |
|
| 16 |
If you choose to build it as a module, it will be called |
| 17 |
wil6210 |
| 18 |
|
| 19 |
config WIL6210_ISR_COR |
| 20 |
bool "Use Clear-On-Read mode for ISR registers for wil6210" |
| 21 |
depends on WIL6210 |
| 22 |
default y |
| 23 |
help |
| 24 |
ISR registers on wil6210 chip may operate in either |
| 25 |
COR (Clear-On-Read) or W1C (Write-1-to-Clear) mode. |
| 26 |
For production code, use COR (say y); is default since |
| 27 |
it saves extra target transaction; |
| 28 |
For ISR debug, use W1C (say n); is allows to monitor ISR |
| 29 |
registers with debugfs. If COR were used, ISR would |
| 30 |
self-clear when accessed for debug purposes, it makes |
| 31 |
such monitoring impossible. |
| 32 |
Say y unless you debug interrupts |
| 33 |
|
| 34 |
config WIL6210_TRACING |
| 35 |
bool "wil6210 tracing support" |
| 36 |
depends on WIL6210 |
| 37 |
depends on EVENT_TRACING |
| 38 |
default n |
| 39 |
help |
| 40 |
Say Y here to enable tracepoints for the wil6210 driver |
| 41 |
using the kernel tracing infrastructure. Select this |
| 42 |
option if you are interested in debugging the driver. |
| 43 |
|
| 44 |
If unsure, say Y to make it easier to debug problems. |
| 45 |
|
| 46 |
config WIL6210_DEBUGFS |
| 47 |
bool "wil6210 debugfs support" |
| 48 |
depends on WIL6210 |
| 49 |
depends on DEBUG_FS |
| 50 |
default y |
| 51 |
help |
| 52 |
Say Y here to enable wil6210 debugfs support, using the |
| 53 |
kernel debugfs infrastructure. Select this |
| 54 |
option if you are interested in debugging the driver. |
| 55 |
|
| 56 |
If unsure, say Y to make it easier to debug problems. |