[GitHub/exynos8895/android_kernel_samsung_universal8895.git] / net / caif / Kconfig

#
# CAIF net configurations
#

menuconfig CAIF
	tristate "CAIF support"
	select CRC_CCITT
	default n
	---help---
	The "Communication CPU to Application CPU Interface" (CAIF) is a packet
	based connection-oriented MUX protocol developed by ST-Ericsson for use
	with its modems. It is accessed from user space as sockets (PF_CAIF).

	Say Y (or M) here if you build for a phone product (e.g. Android or
	MeeGo ) that uses CAIF as transport, if unsure say N.

	If you select to build it as module then CAIF_NETDEV also needs to be
	built as modules. You will also need to say yes to any CAIF physical
	devices that your platform requires.

	See Documentation/networking/caif for a further explanation on how to
	use and configure CAIF.

config  CAIF_DEBUG
	bool "Enable Debug"
	depends on CAIF
	default n
	---help---
	Enable the inclusion of debug code in the CAIF stack.
	Be aware that doing this will impact performance.
	If unsure say N.

config CAIF_NETDEV
	tristate "CAIF GPRS Network device"
	depends on CAIF
	default CAIF
	---help---
	Say Y if you will be using a CAIF based GPRS network device.
	This can be either built-in or a loadable module,
	If you select to build it as a built-in then the main CAIF device must
	also be a built-in.
	If unsure say Y.

config CAIF_USB
	tristate "CAIF USB support"
	depends on CAIF
	default n
	---help---
	Say Y if you are using CAIF over USB CDC NCM.
	This can be either built-in or a loadable module,
	If you select to build it as a built-in then the main CAIF device must
	also be a built-in.
	If unsure say N.
Commit	Line	Data
	1	#
	2	# CAIF net configurations
	3	#
	4
	5	menuconfig CAIF
	6	tristate "CAIF support"
	7	select CRC_CCITT
	8	default n
	9	---help---
	10	The "Communication CPU to Application CPU Interface" (CAIF) is a packet
	11	based connection-oriented MUX protocol developed by ST-Ericsson for use
	12	with its modems. It is accessed from user space as sockets (PF_CAIF).
	13
	14	Say Y (or M) here if you build for a phone product (e.g. Android or
	15	MeeGo ) that uses CAIF as transport, if unsure say N.
	16
	17	If you select to build it as module then CAIF_NETDEV also needs to be
	18	built as modules. You will also need to say yes to any CAIF physical
	19	devices that your platform requires.
	20
	21	See Documentation/networking/caif for a further explanation on how to
	22	use and configure CAIF.
	23
	24	config CAIF_DEBUG
	25	bool "Enable Debug"
	26	depends on CAIF
	27	default n
	28	---help---
	29	Enable the inclusion of debug code in the CAIF stack.
	30	Be aware that doing this will impact performance.
	31	If unsure say N.
	32
	33	config CAIF_NETDEV
	34	tristate "CAIF GPRS Network device"
	35	depends on CAIF
	36	default CAIF
	37	---help---
	38	Say Y if you will be using a CAIF based GPRS network device.
	39	This can be either built-in or a loadable module,
	40	If you select to build it as a built-in then the main CAIF device must
	41	also be a built-in.
	42	If unsure say Y.
	43
	44	config CAIF_USB
	45	tristate "CAIF USB support"
	46	depends on CAIF
	47	default n
	48	---help---
	49	Say Y if you are using CAIF over USB CDC NCM.
	50	This can be either built-in or a loadable module,
	51	If you select to build it as a built-in then the main CAIF device must
	52	also be a built-in.
	53	If unsure say N.