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