1# SPDX-License-Identifier: GPL-2.0-only 2 3menuconfig CAN_DEV 4 tristate "CAN Device Drivers" 5 default y 6 depends on CAN 7 help 8 Controller Area Network (CAN) is serial communications protocol up to 9 1Mbit/s for its original release (now known as Classical CAN) and up 10 to 8Mbit/s for the more recent CAN with Flexible Data-Rate 11 (CAN-FD). The CAN bus was originally mainly for automotive, but is now 12 widely used in marine (NMEA2000), industrial, and medical 13 applications. More information on the CAN network protocol family 14 PF_CAN is contained in <Documentation/networking/can.rst>. 15 16 This section contains all the CAN(-FD) device drivers including the 17 virtual ones. If you own such devices or plan to use the virtual CAN 18 interfaces to develop applications, say Y here. 19 20 To compile as a module, choose M here: the module will be called 21 can-dev. 22 23if CAN_DEV 24 25config CAN_VCAN 26 tristate "Virtual Local CAN Interface (vcan)" 27 help 28 Similar to the network loopback devices, vcan offers a 29 virtual local CAN interface. 30 31 This driver can also be built as a module. If so, the module 32 will be called vcan. 33 34config CAN_VXCAN 35 tristate "Virtual CAN Tunnel (vxcan)" 36 help 37 Similar to the virtual ethernet driver veth, vxcan implements a 38 local CAN traffic tunnel between two virtual CAN network devices. 39 When creating a vxcan, two vxcan devices are created as pair. 40 When one end receives the packet it appears on its pair and vice 41 versa. The vxcan can be used for cross namespace communication. 42 43 In opposite to vcan loopback devices the vxcan only forwards CAN 44 frames to its pair and does *not* provide a local echo of sent 45 CAN frames. To disable a potential echo in af_can.c the vxcan driver 46 announces IFF_ECHO in the interface flags. To have a clean start 47 in each namespace the CAN GW hop counter is set to zero. 48 49 This driver can also be built as a module. If so, the module 50 will be called vxcan. 51 52config CAN_NETLINK 53 bool "CAN device drivers with Netlink support" 54 default y 55 help 56 Enables the common framework for CAN device drivers. This is the 57 standard library and provides features for the Netlink interface such 58 as bittiming validation, support of CAN error states, device restart 59 and others. 60 61 The additional features selected by this option will be added to the 62 can-dev module. 63 64 This is required by all platform and hardware CAN drivers. If you 65 plan to use such devices or if unsure, say Y. 66 67if CAN_NETLINK 68 69config CAN_CALC_BITTIMING 70 bool "CAN bit-timing calculation" 71 default y 72 help 73 If enabled, CAN bit-timing parameters will be calculated for the 74 bit-rate specified via Netlink argument "bitrate" when the device 75 get started. This works fine for the most common CAN controllers 76 with standard bit-rates but may fail for exotic bit-rates or CAN 77 source clock frequencies. Disabling saves some space, but then the 78 bit-timing parameters must be specified directly using the Netlink 79 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw". 80 81 The additional features selected by this option will be added to the 82 can-dev module. 83 84 If unsure, say Y. 85 86config CAN_RX_OFFLOAD 87 bool 88 89config CAN_AT91 90 tristate "Atmel AT91 onchip CAN controller" 91 depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM 92 select CAN_RX_OFFLOAD 93 help 94 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263 95 and AT91SAM9X5 processors. 96 97config CAN_BXCAN 98 tristate "STM32 Basic Extended CAN (bxCAN) devices" 99 depends on ARCH_STM32 || COMPILE_TEST 100 depends on HAS_IOMEM 101 select CAN_RX_OFFLOAD 102 help 103 Say yes here to build support for the STMicroelectronics STM32 basic 104 extended CAN Controller (bxCAN). 105 106 This driver can also be built as a module. If so, the module 107 will be called bxcan. 108 109config CAN_CAN327 110 tristate "Serial / USB serial ELM327 based OBD-II Interfaces (can327)" 111 depends on TTY 112 select CAN_RX_OFFLOAD 113 help 114 CAN driver for several 'low cost' OBD-II interfaces based on the 115 ELM327 OBD-II interpreter chip. 116 117 This is a best effort driver - the ELM327 interface was never 118 designed to be used as a standalone CAN interface. However, it can 119 still be used for simple request-response protocols (such as OBD II), 120 and to monitor broadcast messages on a bus (such as in a vehicle). 121 122 Please refer to the documentation for information on how to use it: 123 Documentation/networking/device_drivers/can/can327.rst 124 125 If this driver is built as a module, it will be called can327. 126 127config CAN_DUMMY 128 tristate "Dummy CAN" 129 help 130 A dummy CAN module supporting Classical CAN, CAN FD and CAN XL. It 131 exposes bittiming values which can be configured through the netlink 132 interface. 133 134 The module will simply echo any frame sent to it. If debug messages 135 are activated, it prints all the CAN bittiming information in the 136 kernel log. Aside from that it does nothing. 137 138 This is convenient for testing the CAN netlink interface. Most of the 139 users will never need this. If unsure, say NO. 140 141 To compile this driver as a module, choose M here: the module will be 142 called dummy-can. 143 144config CAN_FLEXCAN 145 tristate "Support for Freescale FLEXCAN based chips" 146 depends on OF || COLDFIRE || COMPILE_TEST 147 depends on HAS_IOMEM 148 select CAN_RX_OFFLOAD 149 help 150 Say Y here if you want to support for Freescale FlexCAN. 151 152config CAN_GRCAN 153 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices" 154 depends on OF && HAS_DMA && HAS_IOMEM 155 help 156 Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN. 157 Note that the driver supports little endian, even though little 158 endian syntheses of the cores would need some modifications on 159 the hardware level to work. 160 161config CAN_JANZ_ICAN3 162 tristate "Janz VMOD-ICAN3 Intelligent CAN controller" 163 depends on MFD_JANZ_CMODIO 164 help 165 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which 166 connects to a MODULbus carrier board. 167 168 This driver can also be built as a module. If so, the module will be 169 called janz-ican3.ko. 170 171config CAN_KVASER_PCIEFD 172 depends on PCI 173 tristate "Kvaser PCIe FD cards" 174 select NET_DEVLINK 175 help 176 This is a driver for the Kvaser PCI Express CAN FD family. 177 178 Supported devices: 179 Kvaser PCIEcan 4xHS 180 Kvaser PCIEcan 2xHS v2 181 Kvaser PCIEcan HS v2 182 Kvaser PCIEcan 1xCAN v3 183 Kvaser PCIEcan 2xCAN v3 184 Kvaser PCIEcan 4xCAN v2 185 Kvaser Mini PCI Express HS v2 186 Kvaser Mini PCI Express 2xHS v2 187 Kvaser Mini PCI Express 1xCAN v3 188 Kvaser Mini PCI Express 2xCAN v3 189 Kvaser M.2 PCIe 4xCAN 190 Kvaser PCIe 8xCAN 191 192config CAN_SLCAN 193 tristate "Serial / USB serial CAN Adaptors (slcan)" 194 depends on TTY 195 help 196 CAN driver for several 'low cost' CAN interfaces that are attached 197 via serial lines or via USB-to-serial adapters using the LAWICEL 198 ASCII protocol. The driver implements the tty linediscipline N_SLCAN. 199 200 As only the sending and receiving of CAN frames is implemented, this 201 driver should work with the (serial/USB) CAN hardware from: 202 www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de 203 204 Userspace tools to attach the SLCAN line discipline (slcan_attach, 205 slcand) can be found in the can-utils at the linux-can project, see 206 https://github.com/linux-can/can-utils for details. 207 208 This driver can also be built as a module. If so, the module 209 will be called slcan. 210 211config CAN_SUN4I 212 tristate "Allwinner A10 CAN controller" 213 depends on MACH_SUN4I || MACH_SUN7I || (RISCV && ARCH_SUNXI) || COMPILE_TEST 214 help 215 Say Y here if you want to use CAN controller found on Allwinner 216 A10/A20/D1 SoCs. 217 218 To compile this driver as a module, choose M here: the module will 219 be called sun4i_can. 220 221config CAN_TI_HECC 222 depends on ARM || COMPILE_TEST 223 tristate "TI High End CAN Controller" 224 select CAN_RX_OFFLOAD 225 help 226 Driver for TI HECC (High End CAN Controller) module found on many 227 TI devices. The device specifications are available from www.ti.com 228 229config CAN_XILINXCAN 230 tristate "Xilinx CAN" 231 depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST 232 depends on COMMON_CLK && HAS_IOMEM 233 help 234 Xilinx CAN driver. This driver supports both soft AXI CAN IP and 235 Zynq CANPS IP. 236 237source "drivers/net/can/c_can/Kconfig" 238source "drivers/net/can/cc770/Kconfig" 239source "drivers/net/can/ctucanfd/Kconfig" 240source "drivers/net/can/esd/Kconfig" 241source "drivers/net/can/ifi_canfd/Kconfig" 242source "drivers/net/can/m_can/Kconfig" 243source "drivers/net/can/mscan/Kconfig" 244source "drivers/net/can/peak_canfd/Kconfig" 245source "drivers/net/can/rcar/Kconfig" 246source "drivers/net/can/rockchip/Kconfig" 247source "drivers/net/can/sja1000/Kconfig" 248source "drivers/net/can/softing/Kconfig" 249source "drivers/net/can/spi/Kconfig" 250source "drivers/net/can/usb/Kconfig" 251 252endif #CAN_NETLINK 253 254config CAN_DEBUG_DEVICES 255 bool "CAN devices debugging messages" 256 help 257 Say Y here if you want the CAN device drivers to produce a bunch of 258 debug messages to the system log. Select this if you are having 259 a problem with CAN support and want to see more of what is going 260 on. 261 262endif #CAN_DEV 263