1 # SPDX-License-Identifier: GPL-2.0-only <<
2 # 1 #
3 # Controller Area Network (CAN) network layer 2 # Controller Area Network (CAN) network layer core configuration
4 # 3 #
5 4
6 menuconfig CAN 5 menuconfig CAN
>> 6 depends on NET
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 which was developed by Bosch in
11 1983 at Robert Bosch GmbH, and the p !! 11 1991, mainly for automotive, but now widely used in marine
12 released in 1986. The CAN bus was or !! 12 (NMEA2000), industrial, and medical applications.
13 but is now widely used in marine (NM !! 13 More information on the CAN network protocol family PF_CAN
14 applications. More information on th !! 14 is contained in <Documentation/networking/can.txt>.
15 PF_CAN is contained in <Documentatio <<
16 15
17 If you want CAN support you should s 16 If you want CAN support you should say Y here and also to the
18 specific driver for your controller( !! 17 specific driver for your controller(s) below.
19 support section. <<
20 18
21 if CAN 19 if CAN
22 20
23 config CAN_RAW 21 config CAN_RAW
24 tristate "Raw CAN Protocol (raw access 22 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
25 default y 23 default y
26 help !! 24 ---help---
27 The raw CAN protocol option offers a 25 The raw CAN protocol option offers access to the CAN bus via
28 the BSD socket API. You probably wan 26 the BSD socket API. You probably want to use the raw socket in
29 most cases where no higher level pro 27 most cases where no higher level protocol is being used. The raw
30 socket has several filter options e. 28 socket has several filter options e.g. ID masking / error frames.
31 To receive/send raw CAN messages, us 29 To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
32 30
33 config CAN_BCM 31 config CAN_BCM
34 tristate "Broadcast Manager CAN Protoc 32 tristate "Broadcast Manager CAN Protocol (with content filtering)"
35 default y 33 default y
36 help !! 34 ---help---
37 The Broadcast Manager offers content 35 The Broadcast Manager offers content filtering, timeout monitoring,
38 sending of RTR frames, and cyclic CA 36 sending of RTR frames, and cyclic CAN messages without permanent user
39 interaction. The BCM can be 'program 37 interaction. The BCM can be 'programmed' via the BSD socket API and
40 informs you on demand e.g. only on c 38 informs you on demand e.g. only on content updates / timeouts.
41 You probably want to use the bcm soc 39 You probably want to use the bcm socket in most cases where cyclic
42 CAN messages are used on the bus (e. 40 CAN messages are used on the bus (e.g. in automotive environments).
43 To use the Broadcast Manager, use AF 41 To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM.
44 42
45 config CAN_GW 43 config CAN_GW
46 tristate "CAN Gateway/Router (with net 44 tristate "CAN Gateway/Router (with netlink configuration)"
47 default y 45 default y
48 help !! 46 ---help---
49 The CAN Gateway/Router is used to ro 47 The CAN Gateway/Router is used to route (and modify) CAN frames.
50 It is based on the PF_CAN core infra 48 It is based on the PF_CAN core infrastructure for msg filtering and
51 msg sending and can optionally modif 49 msg sending and can optionally modify routed CAN frames on the fly.
52 CAN frames can be routed between CAN 50 CAN frames can be routed between CAN network interfaces (one hop).
53 They can be modified with AND/OR/XOR 51 They can be modified with AND/OR/XOR/SET operations as configured
54 by the netlink configuration interfa 52 by the netlink configuration interface known e.g. from iptables.
55 53
56 source "net/can/j1939/Kconfig" !! 54 source "drivers/net/can/Kconfig"
57 <<
58 config CAN_ISOTP <<
59 tristate "ISO 15765-2 CAN transport pr <<
60 help <<
61 CAN Transport Protocols offer suppor <<
62 communication between CAN nodes via <<
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 <<
67 (max. 8 bytes for CAN CC and max. 64 <<
68 segmentation is needed to transport <<
69 as needed e.g. for vehicle diagnosis <<
70 traffic. <<
71 55
72 endif 56 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.