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