drivers/net/can/Kconfig

   1 menu "CAN Device Drivers"
   2
   3 config CAN_VCAN
   4         tristate "Virtual Local CAN Interface (vcan)"
   5         ---help---
   6           Similar to the network loopback devices, vcan offers a
   7           virtual local CAN interface.
   8
   9           This driver can also be built as a module.  If so, the module
  10           will be called vcan.
  11
  12 config CAN_VXCAN
  13         tristate "Virtual CAN Tunnel (vxcan)"
  14         ---help---
  15           Similar to the virtual ethernet driver veth, vxcan implements a
  16           local CAN traffic tunnel between two virtual CAN network devices.
  17           When creating a vxcan, two vxcan devices are created as pair.
  18           When one end receives the packet it appears on its pair and vice
  19           versa. The vxcan can be used for cross namespace communication.
  20
  21           In opposite to vcan loopback devices the vxcan only forwards CAN
  22           frames to its pair and does *not* provide a local echo of sent
  23           CAN frames. To disable a potential echo in af_can.c the vxcan driver
  24           announces IFF_ECHO in the interface flags. To have a clean start
  25           in each namespace the CAN GW hop counter is set to zero.
  26
  27           This driver can also be built as a module.  If so, the module
  28           will be called vxcan.
  29
  30 config CAN_SLCAN
  31         tristate "Serial / USB serial CAN Adaptors (slcan)"
  32         depends on TTY
  33         ---help---
  34           CAN driver for several 'low cost' CAN interfaces that are attached
  35           via serial lines or via USB-to-serial adapters using the LAWICEL
  36           ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
  37
  38           As only the sending and receiving of CAN frames is implemented, this
  39           driver should work with the (serial/USB) CAN hardware from:
  40           www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
  41
  42           Userspace tools to attach the SLCAN line discipline (slcan_attach,
  43           slcand) can be found in the can-utils at the SocketCAN SVN, see
  44           http://developer.berlios.de/projects/socketcan for details.
  45
  46           The slcan driver supports up to 10 CAN netdevices by default which
  47           can be changed by the 'maxdev=xx' module option. This driver can
  48           also be built as a module. If so, the module will be called slcan.
  49
  50 config CAN_DEV
  51         tristate "Platform CAN drivers with Netlink support"
  52         default y
  53         ---help---
  54           Enables the common framework for platform CAN drivers with Netlink
  55           support. This is the standard library for CAN drivers.
  56           If unsure, say Y.
  57
  58 if CAN_DEV
  59
  60 config CAN_CALC_BITTIMING
  61         bool "CAN bit-timing calculation"
  62         default y
  63         ---help---
  64           If enabled, CAN bit-timing parameters will be calculated for the
  65           bit-rate specified via Netlink argument "bitrate" when the device
  66           get started. This works fine for the most common CAN controllers
  67           with standard bit-rates but may fail for exotic bit-rates or CAN
  68           source clock frequencies. Disabling saves some space, but then the
  69           bit-timing parameters must be specified directly using the Netlink
  70           arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
  71           If unsure, say Y.
  72
  73 config CAN_LEDS
  74         bool "Enable LED triggers for Netlink based drivers"
  75         depends on LEDS_CLASS
  76         select LEDS_TRIGGERS
  77         ---help---
  78           This option adds two LED triggers for packet receive and transmit
  79           events on each supported CAN device.
  80
  81           Say Y here if you are working on a system with led-class supported
  82           LEDs and you want to use them as canbus activity indicators.
  83
  84 config CAN_AT91
  85         tristate "Atmel AT91 onchip CAN controller"
  86         depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM
  87         ---help---
  88           This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
  89           and AT91SAM9X5 processors.
  90
  91 config CAN_BFIN
  92         depends on BF534 || BF536 || BF537 || BF538 || BF539 || BF54x
  93         tristate "Analog Devices Blackfin on-chip CAN"
  94         ---help---
  95           Driver for the Analog Devices Blackfin on-chip CAN controllers
  96
  97           To compile this driver as a module, choose M here: the
  98           module will be called bfin_can.
  99
 100 config CAN_FLEXCAN
 101         tristate "Support for Freescale FLEXCAN based chips"
 102         depends on ARM || PPC
 103         ---help---
 104           Say Y here if you want to support for Freescale FlexCAN.
 105
 106 config CAN_GRCAN
 107         tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
 108         depends on OF && HAS_DMA
 109         ---help---
 110           Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
 111           Note that the driver supports little endian, even though little
 112           endian syntheses of the cores would need some modifications on
 113           the hardware level to work.
 114
 115 config CAN_JANZ_ICAN3
 116         tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
 117         depends on MFD_JANZ_CMODIO
 118         ---help---
 119           Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
 120           connects to a MODULbus carrier board.
 121
 122           This driver can also be built as a module. If so, the module will be
 123           called janz-ican3.ko.
 124
 125 config CAN_SUN4I
 126         tristate "Allwinner A10 CAN controller"
 127         depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
 128         ---help---
 129           Say Y here if you want to use CAN controller found on Allwinner
 130           A10/A20 SoCs.
 131
 132           To compile this driver as a module, choose M here: the module will
 133           be called sun4i_can.
 134
 135 config CAN_TI_HECC
 136         depends on ARM
 137         tristate "TI High End CAN Controller"
 138         ---help---
 139           Driver for TI HECC (High End CAN Controller) module found on many
 140           TI devices. The device specifications are available from www.ti.com
 141
 142 config CAN_XILINXCAN
 143         tristate "Xilinx CAN"
 144         depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST
 145         depends on COMMON_CLK && HAS_IOMEM
 146         ---help---
 147           Xilinx CAN driver. This driver supports both soft AXI CAN IP and
 148           Zynq CANPS IP.
 149
 150 config PCH_CAN
 151         tristate "Intel EG20T PCH CAN controller"
 152         depends on PCI && (X86_32 || COMPILE_TEST)
 153         ---help---
 154           This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
 155           is an IOH for x86 embedded processor (Intel Atom E6xx series).
 156           This driver can access CAN bus.
 157
 158 source "drivers/net/can/c_can/Kconfig"
 159 source "drivers/net/can/cc770/Kconfig"
 160 source "drivers/net/can/ifi_canfd/Kconfig"
 161 source "drivers/net/can/m_can/Kconfig"
 162 source "drivers/net/can/mscan/Kconfig"
 163 source "drivers/net/can/peak_canfd/Kconfig"
 164 source "drivers/net/can/rcar/Kconfig"
 165 source "drivers/net/can/sja1000/Kconfig"
 166 source "drivers/net/can/softing/Kconfig"
 167 source "drivers/net/can/spi/Kconfig"
 168 source "drivers/net/can/usb/Kconfig"
 169
 170 endif
 171
 172 config CAN_DEBUG_DEVICES
 173         bool "CAN devices debugging messages"
 174         ---help---
 175           Say Y here if you want the CAN device drivers to produce a bunch of
 176           debug messages to the system log.  Select this if you are having
 177           a problem with CAN support and want to see more of what is going
 178           on.
 179
 180 endmenu