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

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