PageRenderTime 19ms CodeModel.GetById 17ms app.highlight 1ms RepoModel.GetById 0ms app.codeStats 0ms

/drivers/net/wireless/iwlwifi/Kconfig

https://bitbucket.org/cyanogenmod/android_kernel_asus_tf300t
#! | 130 lines | 103 code | 27 blank | 0 comment | 0 complexity | 3ba5b292ac43b96e08f04c22edbd3b18 MD5 | raw file
Possible License(s): LGPL-2.0, AGPL-1.0, GPL-2.0
  1config IWLAGN
  2	tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlagn) "
  3	depends on PCI && MAC80211
  4	select FW_LOADER
  5	select NEW_LEDS
  6	select LEDS_CLASS
  7	select LEDS_TRIGGERS
  8	select MAC80211_LEDS
  9	---help---
 10	  Select to build the driver supporting the:
 11
 12	  Intel Wireless WiFi Link Next-Gen AGN
 13
 14	  This option enables support for use with the following hardware:
 15		Intel Wireless WiFi Link 6250AGN Adapter
 16		Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
 17		Intel WiFi Link 1000BGN
 18		Intel Wireless WiFi 5150AGN
 19		Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
 20		Intel 6005 Series Wi-Fi Adapters
 21		Intel 6030 Series Wi-Fi Adapters
 22		Intel Wireless WiFi Link 6150BGN 2 Adapter
 23		Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
 24		Intel 2000 Series Wi-Fi Adapters
 25
 26
 27	  This driver uses the kernel's mac80211 subsystem.
 28
 29	  In order to use this driver, you will need a microcode (uCode)
 30	  image for it. You can obtain the microcode from:
 31
 32	          <http://intellinuxwireless.org/>.
 33
 34	  The microcode is typically installed in /lib/firmware. You can
 35	  look in the hotplug script /etc/hotplug/firmware.agent to
 36	  determine which directory FIRMWARE_DIR is set to when the script
 37	  runs.
 38
 39	  If you want to compile the driver as a module ( = code which can be
 40	  inserted in and removed from the running kernel whenever you want),
 41	  say M here and read <file:Documentation/kbuild/modules.txt>.  The
 42	  module will be called iwlagn.
 43
 44menu "Debugging Options"
 45	depends on IWLAGN
 46
 47config IWLWIFI_DEBUG
 48	bool "Enable full debugging output in the iwlagn driver"
 49	depends on IWLAGN
 50	---help---
 51	  This option will enable debug tracing output for the iwlwifi drivers
 52
 53	  This will result in the kernel module being ~100k larger.  You can
 54	  control which debug output is sent to the kernel log by setting the
 55	  value in
 56
 57		/sys/class/net/wlan0/device/debug_level
 58
 59	  This entry will only exist if this option is enabled.
 60
 61	  To set a value, simply echo an 8-byte hex value to the same file:
 62
 63		  % echo 0x43fff > /sys/class/net/wlan0/device/debug_level
 64
 65	  You can find the list of debug mask values in:
 66		  drivers/net/wireless/iwlwifi/iwl-debug.h
 67
 68	  If this is your first time using this driver, you should say Y here
 69	  as the debug information can assist others in helping you resolve
 70	  any problems you may encounter.
 71
 72config IWLWIFI_DEBUGFS
 73        bool "iwlagn debugfs support"
 74        depends on IWLAGN && MAC80211_DEBUGFS
 75        ---help---
 76	  Enable creation of debugfs files for the iwlwifi drivers. This
 77	  is a low-impact option that allows getting insight into the
 78	  driver's state at runtime.
 79
 80config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
 81        bool "Experimental uCode support"
 82        depends on IWLAGN && IWLWIFI_DEBUG
 83        ---help---
 84	  Enable use of experimental ucode for testing and debugging.
 85
 86config IWLWIFI_DEVICE_TRACING
 87	bool "iwlwifi device access tracing"
 88	depends on IWLAGN
 89	depends on EVENT_TRACING
 90	help
 91	  Say Y here to trace all commands, including TX frames and IO
 92	  accesses, sent to the device. If you say yes, iwlwifi will
 93	  register with the ftrace framework for event tracing and dump
 94	  all this information to the ringbuffer, you may need to
 95	  increase the ringbuffer size. See the ftrace documentation
 96	  for more information.
 97
 98	  When tracing is not enabled, this option still has some
 99	  (though rather small) overhead.
100
101	  If unsure, say Y so we can help you better when problems
102	  occur.
103endmenu
104
105config IWLWIFI_DEVICE_SVTOOL
106	bool "iwlwifi device svtool support"
107	depends on IWLAGN
108	select NL80211_TESTMODE
109	help
110	  This option enables the svtool support for iwlwifi device through
111	  NL80211_TESTMODE. svtool is a software validation tool that runs in
112	  the user space and interacts with the device in the kernel space
113	  through the generic netlink message via NL80211_TESTMODE channel.
114
115config IWL_P2P
116	bool "iwlwifi experimental P2P support"
117	depends on IWLAGN
118	help
119	  This option enables experimental P2P support for some devices
120	  based on microcode support. Since P2P support is still under
121	  development, this option may even enable it for some devices
122	  now that turn out to not support it in the future due to
123	  microcode restrictions.
124
125	  To determine if your microcode supports the experimental P2P
126	  offered by this option, check if the driver advertises AP
127	  support when it is loaded.
128
129	  Say Y only if you want to experiment with P2P.
130