Kconfig 5.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172
  1. config IWLWIFI
  2. tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) "
  3. depends on PCI && MAC80211 && HAS_IOMEM
  4. select FW_LOADER
  5. ---help---
  6. Select to build the driver supporting the:
  7. Intel Wireless WiFi Link Next-Gen AGN
  8. This option enables support for use with the following hardware:
  9. Intel Wireless WiFi Link 6250AGN Adapter
  10. Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
  11. Intel WiFi Link 1000BGN
  12. Intel Wireless WiFi 5150AGN
  13. Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
  14. Intel 6005 Series Wi-Fi Adapters
  15. Intel 6030 Series Wi-Fi Adapters
  16. Intel Wireless WiFi Link 6150BGN 2 Adapter
  17. Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
  18. Intel 2000 Series Wi-Fi Adapters
  19. Intel 7260 Wi-Fi Adapter
  20. Intel 3160 Wi-Fi Adapter
  21. Intel 7265 Wi-Fi Adapter
  22. Intel 8260 Wi-Fi Adapter
  23. Intel 3165 Wi-Fi Adapter
  24. This driver uses the kernel's mac80211 subsystem.
  25. In order to use this driver, you will need a firmware
  26. image for it. You can obtain the microcode from:
  27. <http://wireless.kernel.org/en/users/Drivers/iwlwifi>.
  28. The firmware is typically installed in /lib/firmware. You can
  29. look in the hotplug script /etc/hotplug/firmware.agent to
  30. determine which directory FIRMWARE_DIR is set to when the script
  31. runs.
  32. If you want to compile the driver as a module ( = code which can be
  33. inserted in and removed from the running kernel whenever you want),
  34. say M here and read <file:Documentation/kbuild/modules.txt>. The
  35. module will be called iwlwifi.
  36. if IWLWIFI
  37. config IWLWIFI_LEDS
  38. bool
  39. depends on LEDS_CLASS=y || LEDS_CLASS=IWLWIFI
  40. select LEDS_TRIGGERS
  41. select MAC80211_LEDS
  42. default y
  43. config IWLDVM
  44. tristate "Intel Wireless WiFi DVM Firmware support"
  45. help
  46. This is the driver that supports the DVM firmware. The list
  47. of the devices that use this firmware is available here:
  48. https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
  49. config IWLMVM
  50. tristate "Intel Wireless WiFi MVM Firmware support"
  51. select WANT_DEV_COREDUMP
  52. help
  53. This is the driver that supports the MVM firmware. The list
  54. of the devices that use this firmware is available here:
  55. https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
  56. # don't call it _MODULE -- will confuse Kconfig/fixdep/...
  57. config IWLWIFI_OPMODE_MODULAR
  58. bool
  59. default y if IWLDVM=m
  60. default y if IWLMVM=m
  61. comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM"
  62. depends on IWLDVM=n && IWLMVM=n
  63. config IWLWIFI_BCAST_FILTERING
  64. bool "Enable broadcast filtering"
  65. depends on IWLMVM
  66. help
  67. Say Y here to enable default bcast filtering configuration.
  68. Enabling broadcast filtering will drop any incoming wireless
  69. broadcast frames, except some very specific predefined
  70. patterns (e.g. incoming arp requests).
  71. If unsure, don't enable this option, as some programs might
  72. expect incoming broadcasts for their normal operations.
  73. config IWLWIFI_UAPSD
  74. bool "enable U-APSD by default"
  75. depends on IWLMVM
  76. help
  77. Say Y here to enable U-APSD by default. This may cause
  78. interoperability problems with some APs, manifesting in lower than
  79. expected throughput due to those APs not enabling aggregation
  80. If unsure, say N.
  81. config IWLWIFI_PCIE_RTPM
  82. bool "Enable runtime power management mode for PCIe devices"
  83. depends on IWLMVM && PM
  84. default false
  85. help
  86. Say Y here to enable runtime power management for PCIe
  87. devices. If enabled, the device will go into low power mode
  88. when idle for a short period of time, allowing for improved
  89. power saving during runtime.
  90. If unsure, say N.
  91. menu "Debugging Options"
  92. config IWLWIFI_DEBUG
  93. bool "Enable full debugging output in the iwlwifi driver"
  94. ---help---
  95. This option will enable debug tracing output for the iwlwifi drivers
  96. This will result in the kernel module being ~100k larger. You can
  97. control which debug output is sent to the kernel log by setting the
  98. value in
  99. /sys/module/iwlwifi/parameters/debug
  100. This entry will only exist if this option is enabled.
  101. To set a value, simply echo an 8-byte hex value to the same file:
  102. % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
  103. You can find the list of debug mask values in:
  104. drivers/net/wireless/iwlwifi/iwl-debug.h
  105. If this is your first time using this driver, you should say Y here
  106. as the debug information can assist others in helping you resolve
  107. any problems you may encounter.
  108. config IWLWIFI_DEBUGFS
  109. bool "iwlwifi debugfs support"
  110. depends on MAC80211_DEBUGFS
  111. ---help---
  112. Enable creation of debugfs files for the iwlwifi drivers. This
  113. is a low-impact option that allows getting insight into the
  114. driver's state at runtime.
  115. config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
  116. bool "Experimental uCode support"
  117. depends on IWLWIFI_DEBUG
  118. ---help---
  119. Enable use of experimental ucode for testing and debugging.
  120. config IWLWIFI_DEVICE_TRACING
  121. bool "iwlwifi device access tracing"
  122. depends on EVENT_TRACING
  123. default y
  124. help
  125. Say Y here to trace all commands, including TX frames and IO
  126. accesses, sent to the device. If you say yes, iwlwifi will
  127. register with the ftrace framework for event tracing and dump
  128. all this information to the ringbuffer, you may need to
  129. increase the ringbuffer size. See the ftrace documentation
  130. for more information.
  131. When tracing is not enabled, this option still has some
  132. (though rather small) overhead.
  133. If unsure, say Y so we can help you better when problems
  134. occur.
  135. endmenu
  136. endif