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