Kconfig 3.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # Controller Area Network (CAN) network layer core configuration
  4. #
  5. menuconfig CAN
  6. tristate "CAN bus subsystem support"
  7. help
  8. Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
  9. communications protocol. Development of the CAN bus started in
  10. 1983 at Robert Bosch GmbH, and the protocol was officially
  11. released in 1986. The CAN bus was originally mainly for automotive,
  12. but is now widely used in marine (NMEA2000), industrial, and medical
  13. applications. More information on the CAN network protocol family
  14. PF_CAN is contained in <Documentation/networking/can.rst>.
  15. If you want CAN support you should say Y here and also to the
  16. specific driver for your controller(s) under the Network device
  17. support section.
  18. if CAN
  19. config CAN_RAW
  20. tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
  21. default y
  22. help
  23. The raw CAN protocol option offers access to the CAN bus via
  24. the BSD socket API. You probably want to use the raw socket in
  25. most cases where no higher level protocol is being used. The raw
  26. socket has several filter options e.g. ID masking / error frames.
  27. To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
  28. config CAN_BCM
  29. tristate "Broadcast Manager CAN Protocol (with content filtering)"
  30. default y
  31. help
  32. The Broadcast Manager offers content filtering, timeout monitoring,
  33. sending of RTR frames, and cyclic CAN messages without permanent user
  34. interaction. The BCM can be 'programmed' via the BSD socket API and
  35. informs you on demand e.g. only on content updates / timeouts.
  36. You probably want to use the bcm socket in most cases where cyclic
  37. CAN messages are used on the bus (e.g. in automotive environments).
  38. To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM.
  39. config CAN_GW
  40. tristate "CAN Gateway/Router (with netlink configuration)"
  41. default y
  42. help
  43. The CAN Gateway/Router is used to route (and modify) CAN frames.
  44. It is based on the PF_CAN core infrastructure for msg filtering and
  45. msg sending and can optionally modify routed CAN frames on the fly.
  46. CAN frames can be routed between CAN network interfaces (one hop).
  47. They can be modified with AND/OR/XOR/SET operations as configured
  48. by the netlink configuration interface known e.g. from iptables.
  49. source "net/can/j1939/Kconfig"
  50. config CAN_ISOTP
  51. tristate "ISO 15765-2:2016 CAN transport protocol"
  52. help
  53. CAN Transport Protocols offer support for segmented Point-to-Point
  54. communication between CAN nodes via two defined CAN Identifiers.
  55. As CAN frames can only transport a small amount of data bytes
  56. (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
  57. segmentation is needed to transport longer Protocol Data Units (PDU)
  58. as needed e.g. for vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN
  59. traffic.
  60. This protocol driver implements data transfers according to
  61. ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
  62. If you want to perform automotive vehicle diagnostic services (UDS),
  63. say 'y'.
  64. endif