net/can/Kconfig

   1 # SPDX-License-Identifier: GPL-2.0-only
   2 #
   3 # Controller Area Network (CAN) network layer core configuration
   4 #
   5
   6 menuconfig 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. Development of the CAN bus started in
  12           1983 at Robert Bosch GmbH, and the protocol was officially
  13           released in 1986. The CAN bus was originally mainly for automotive,
  14           but is now widely used in marine (NMEA2000), industrial, and medical
  15           applications. More information on the CAN network protocol family
  16           PF_CAN is contained in <Documentation/networking/can.rst>.
  17
  18           If you want CAN support you should say Y here and also to the
  19           specific driver for your controller(s) below.
  20
  21 if CAN
  22
  23 config 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
  33 config 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
  45 config 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
  56 source "net/can/j1939/Kconfig"
  57
  58 source "drivers/net/can/Kconfig"
  59
  60 endif