[deliverable/linux.git] / drivers / net / wireless / iwlwifi / Kconfig

config IWLAGN
	tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlagn) "
	depends on PCI && MAC80211
	select FW_LOADER
	select NEW_LEDS
	select LEDS_CLASS
	select LEDS_TRIGGERS
	select MAC80211_LEDS
	---help---
	  Select to build the driver supporting the:

	  Intel Wireless WiFi Link Next-Gen AGN

	  This option enables support for use with the following hardware:
		Intel Wireless WiFi Link 6250AGN Adapter
		Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
		Intel WiFi Link 1000BGN
		Intel Wireless WiFi 5150AGN
		Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
		Intel 6005 Series Wi-Fi Adapters
		Intel 6030 Series Wi-Fi Adapters
		Intel Wireless WiFi Link 6150BGN 2 Adapter
		Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
		Intel 2000 Series Wi-Fi Adapters


	  This driver uses the kernel's mac80211 subsystem.

	  In order to use this driver, you will need a microcode (uCode)
	  image for it. You can obtain the microcode from:

	          <http://intellinuxwireless.org/>.

	  The microcode is typically installed in /lib/firmware. You can
	  look in the hotplug script /etc/hotplug/firmware.agent to
	  determine which directory FIRMWARE_DIR is set to when the script
	  runs.

	  If you want to compile the driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/kbuild/modules.txt>.  The
	  module will be called iwlagn.

menu "Debugging Options"
	depends on IWLAGN

config IWLWIFI_DEBUG
	bool "Enable full debugging output in the iwlagn driver"
	depends on IWLAGN
	---help---
	  This option will enable debug tracing output for the iwlwifi drivers

	  This will result in the kernel module being ~100k larger.  You can
	  control which debug output is sent to the kernel log by setting the
	  value in

		/sys/class/net/wlan0/device/debug_level

	  This entry will only exist if this option is enabled.

	  To set a value, simply echo an 8-byte hex value to the same file:

		  % echo 0x43fff > /sys/class/net/wlan0/device/debug_level

	  You can find the list of debug mask values in:
		  drivers/net/wireless/iwlwifi/iwl-debug.h

	  If this is your first time using this driver, you should say Y here
	  as the debug information can assist others in helping you resolve
	  any problems you may encounter.

config IWLWIFI_DEBUGFS
        bool "iwlagn debugfs support"
        depends on IWLAGN && MAC80211_DEBUGFS
        ---help---
	  Enable creation of debugfs files for the iwlwifi drivers. This
	  is a low-impact option that allows getting insight into the
	  driver's state at runtime.

config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
        bool "Experimental uCode support"
        depends on IWLAGN && IWLWIFI_DEBUG
        ---help---
	  Enable use of experimental ucode for testing and debugging.

config IWLWIFI_DEVICE_TRACING
	bool "iwlwifi device access tracing"
	depends on IWLAGN
	depends on EVENT_TRACING
	help
	  Say Y here to trace all commands, including TX frames and IO
	  accesses, sent to the device. If you say yes, iwlwifi will
	  register with the ftrace framework for event tracing and dump
	  all this information to the ringbuffer, you may need to
	  increase the ringbuffer size. See the ftrace documentation
	  for more information.

	  When tracing is not enabled, this option still has some
	  (though rather small) overhead.

	  If unsure, say Y so we can help you better when problems
	  occur.
endmenu

config IWL_P2P
	bool "iwlwifi experimental P2P support"
	depends on IWLAGN
	help
	  This option enables experimental P2P support for some devices
	  based on microcode support. Since P2P support is still under
	  development, this option may even enable it for some devices
	  now that turn out to not support it in the future due to
	  microcode restrictions.

	  To determine if your microcode supports the experimental P2P
	  offered by this option, check if the driver advertises AP
	  support when it is loaded.

	  Say Y only if you want to experiment with P2P.
Commit	Line	Data
be663ab6 WYG	1	config IWLAGN
be663ab6 WYG	2	tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlagn) "
1d8c4ae9	3	depends on PCI && MAC80211
80bc5393	4	select FW_LOADER
5ed540ae WYG	5	select NEW_LEDS
	6	select LEDS_CLASS
	7	select LEDS_TRIGGERS
	8	select MAC80211_LEDS
be663ab6 WYG	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.
ab53d8af	43
110ff6db	44	menu "Debugging Options"
be663ab6	45	depends on IWLAGN
110ff6db	46
4fc22b21	47	config IWLWIFI_DEBUG
be663ab6 WYG	48	bool "Enable full debugging output in the iwlagn driver"
be663ab6 WYG	49	depends on IWLAGN
4fc22b21 TW	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
	72	config IWLWIFI_DEBUGFS
80bc5393	73	bool "iwlagn debugfs support"
be663ab6	74	depends on IWLAGN && MAC80211_DEBUGFS
4fc22b21	75	---help---
d73e4923 JB	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.
4fc22b21	79
39396085 JS	80	config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
39396085 JS	81	bool "Experimental uCode support"
be663ab6	82	depends on IWLAGN && IWLWIFI_DEBUG
39396085 JS	83	---help---
	84	Enable use of experimental ucode for testing and debugging.
	85
be1a71a1 JB	86	config IWLWIFI_DEVICE_TRACING
be1a71a1 JB	87	bool "iwlwifi device access tracing"
be663ab6	88	depends on IWLAGN
be1a71a1 JB	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.
110ff6db	103	endmenu
be1a71a1	104
f35c0c56 WYG	105	config IWL_P2P
f35c0c56 WYG	106	bool "iwlwifi experimental P2P support"
be663ab6	107	depends on IWLAGN
f35c0c56 WYG	108	help
	109	This option enables experimental P2P support for some devices
	110	based on microcode support. Since P2P support is still under
	111	development, this option may even enable it for some devices
	112	now that turn out to not support it in the future due to
	113	microcode restrictions.
	114
	115	To determine if your microcode supports the experimental P2P
	116	offered by this option, check if the driver advertises AP
	117	support when it is loaded.
	118
	119	Say Y only if you want to experiment with P2P.
	120