1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Controller Area Network (CAN) network layer core configuration 4# 5 6menuconfig CAN 7 depends on NET 8 tristate "CAN bus subsystem support" 9 ---help--- 10 Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial 11 communications protocol which was developed by Bosch in 12 1991, mainly for automotive, but now widely used in marine 13 (NMEA2000), industrial, and medical applications. 14 More information on the CAN network protocol family PF_CAN 15 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) below. 19 20if CAN 21 22config CAN_RAW 23 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)" 24 default y 25 ---help--- 26 The raw CAN protocol option offers access to the CAN bus via 27 the BSD socket API. You probably want to use the raw socket in 28 most cases where no higher level protocol is being used. The raw 29 socket has several filter options e.g. ID masking / error frames. 30 To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW. 31 32config CAN_BCM 33 tristate "Broadcast Manager CAN Protocol (with content filtering)" 34 default y 35 ---help--- 36 The Broadcast Manager offers content filtering, timeout monitoring, 37 sending of RTR frames, and cyclic CAN messages without permanent user 38 interaction. The BCM can be 'programmed' via the BSD socket API and 39 informs you on demand e.g. only on content updates / timeouts. 40 You probably want to use the bcm socket in most cases where cyclic 41 CAN messages are used on the bus (e.g. in automotive environments). 42 To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM. 43 44config CAN_GW 45 tristate "CAN Gateway/Router (with netlink configuration)" 46 default y 47 ---help--- 48 The CAN Gateway/Router is used to route (and modify) CAN frames. 49 It is based on the PF_CAN core infrastructure for msg filtering and 50 msg sending and can optionally modify routed CAN frames on the fly. 51 CAN frames can be routed between CAN network interfaces (one hop). 52 They can be modified with AND/OR/XOR/SET operations as configured 53 by the netlink configuration interface known e.g. from iptables. 54 55source "drivers/net/can/Kconfig" 56 57endif 58