1# SPDX-License-Identifier: GPL-2.0-only 2menu "CAN Device Drivers" 3 4config CAN_VCAN 5 tristate "Virtual Local CAN Interface (vcan)" 6 help 7 Similar to the network loopback devices, vcan offers a 8 virtual local CAN interface. 9 10 This driver can also be built as a module. If so, the module 11 will be called vcan. 12 13config CAN_VXCAN 14 tristate "Virtual CAN Tunnel (vxcan)" 15 help 16 Similar to the virtual ethernet driver veth, vxcan implements a 17 local CAN traffic tunnel between two virtual CAN network devices. 18 When creating a vxcan, two vxcan devices are created as pair. 19 When one end receives the packet it appears on its pair and vice 20 versa. The vxcan can be used for cross namespace communication. 21 22 In opposite to vcan loopback devices the vxcan only forwards CAN 23 frames to its pair and does *not* provide a local echo of sent 24 CAN frames. To disable a potential echo in af_can.c the vxcan driver 25 announces IFF_ECHO in the interface flags. To have a clean start 26 in each namespace the CAN GW hop counter is set to zero. 27 28 This driver can also be built as a module. If so, the module 29 will be called vxcan. 30 31config CAN_SLCAN 32 tristate "Serial / USB serial CAN Adaptors (slcan)" 33 depends on TTY 34 help 35 CAN driver for several 'low cost' CAN interfaces that are attached 36 via serial lines or via USB-to-serial adapters using the LAWICEL 37 ASCII protocol. The driver implements the tty linediscipline N_SLCAN. 38 39 As only the sending and receiving of CAN frames is implemented, this 40 driver should work with the (serial/USB) CAN hardware from: 41 www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de 42 43 Userspace tools to attach the SLCAN line discipline (slcan_attach, 44 slcand) can be found in the can-utils at the linux-can project, see 45 https://github.com/linux-can/can-utils for details. 46 47 The slcan driver supports up to 10 CAN netdevices by default which 48 can be changed by the 'maxdev=xx' module option. This driver can 49 also be built as a module. If so, the module will be called slcan. 50 51config CAN_NETLINK 52 tristate "CAN device drivers with Netlink support" 53 default y 54 help 55 Enables the common framework for CAN device drivers. This is the 56 standard library and provides features for the Netlink interface such 57 as bittiming validation, support of CAN error states, device restart 58 and others. 59 60 This is required by all platform and hardware CAN drivers. If you 61 plan to use such devices or if unsure, say Y. 62 63if CAN_NETLINK 64 65config CAN_CALC_BITTIMING 66 bool "CAN bit-timing calculation" 67 default y 68 help 69 If enabled, CAN bit-timing parameters will be calculated for the 70 bit-rate specified via Netlink argument "bitrate" when the device 71 get started. This works fine for the most common CAN controllers 72 with standard bit-rates but may fail for exotic bit-rates or CAN 73 source clock frequencies. Disabling saves some space, but then the 74 bit-timing parameters must be specified directly using the Netlink 75 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw". 76 If unsure, say Y. 77 78config CAN_AT91 79 tristate "Atmel AT91 onchip CAN controller" 80 depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM 81 help 82 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263 83 and AT91SAM9X5 processors. 84 85config CAN_FLEXCAN 86 tristate "Support for Freescale FLEXCAN based chips" 87 depends on OF || COLDFIRE || COMPILE_TEST 88 depends on HAS_IOMEM 89 help 90 Say Y here if you want to support for Freescale FlexCAN. 91 92config CAN_GRCAN 93 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices" 94 depends on OF && HAS_DMA && HAS_IOMEM 95 help 96 Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN. 97 Note that the driver supports little endian, even though little 98 endian syntheses of the cores would need some modifications on 99 the hardware level to work. 100 101config CAN_JANZ_ICAN3 102 tristate "Janz VMOD-ICAN3 Intelligent CAN controller" 103 depends on MFD_JANZ_CMODIO 104 help 105 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which 106 connects to a MODULbus carrier board. 107 108 This driver can also be built as a module. If so, the module will be 109 called janz-ican3.ko. 110 111config CAN_KVASER_PCIEFD 112 depends on PCI 113 tristate "Kvaser PCIe FD cards" 114 select CRC32 115 help 116 This is a driver for the Kvaser PCI Express CAN FD family. 117 118 Supported devices: 119 Kvaser PCIEcan 4xHS 120 Kvaser PCIEcan 2xHS v2 121 Kvaser PCIEcan HS v2 122 Kvaser Mini PCI Express HS v2 123 Kvaser Mini PCI Express 2xHS v2 124 125config 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 135config 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 142config 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 150config 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 158source "drivers/net/can/c_can/Kconfig" 159source "drivers/net/can/cc770/Kconfig" 160source "drivers/net/can/ctucanfd/Kconfig" 161source "drivers/net/can/ifi_canfd/Kconfig" 162source "drivers/net/can/m_can/Kconfig" 163source "drivers/net/can/mscan/Kconfig" 164source "drivers/net/can/peak_canfd/Kconfig" 165source "drivers/net/can/rcar/Kconfig" 166source "drivers/net/can/sja1000/Kconfig" 167source "drivers/net/can/softing/Kconfig" 168source "drivers/net/can/spi/Kconfig" 169source "drivers/net/can/usb/Kconfig" 170 171endif #CAN_NETLINK 172 173config CAN_DEBUG_DEVICES 174 bool "CAN devices debugging messages" 175 help 176 Say Y here if you want the CAN device drivers to produce a bunch of 177 debug messages to the system log. Select this if you are having 178 a problem with CAN support and want to see more of what is going 179 on. 180 181endmenu 182