| Subash Abhinov Kasiviswanathan | 2139ce8a | 2016-10-14 11:01:48 -0600 | [diff] [blame] | 1 | # |
| 2 | # RMNET Data and MAP driver |
| 3 | # |
| 4 | |
| 5 | menuconfig RMNET_DATA |
| 6 | depends on NETDEVICES |
| 7 | bool "RmNet Data and MAP driver" |
| 8 | ---help--- |
| 9 | If you say Y here, then the rmnet_data module will be statically |
| 10 | compiled into the kernel. The rmnet data module provides MAP |
| 11 | functionality for embedded and bridged traffic. |
| 12 | if RMNET_DATA |
| 13 | |
| 14 | config RMNET_DATA_FC |
| 15 | bool "RmNet Data Flow Control" |
| 16 | depends on NET_SCHED && NET_SCH_PRIO |
| 17 | ---help--- |
| 18 | Say Y here if you want RmNet data to handle in-band flow control and |
| 19 | ioctl based flow control. This depends on net scheduler and prio queue |
| 20 | capability being present in the kernel. In-band flow control requires |
| 21 | MAP protocol be used. |
| 22 | config RMNET_DATA_DEBUG_PKT |
| 23 | bool "Packet Debug Logging" |
| 24 | ---help--- |
| 25 | Say Y here if you want RmNet data to be able to log packets in main |
| 26 | system log. This should not be enabled on production builds as it can |
| 27 | impact system performance. Note that simply enabling it here will not |
| 28 | enable the logging; it must be enabled at run-time as well. |
| 29 | endif # RMNET_DATA |