Kconfig 1.5 KB

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