1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "CAN Device Drivers"
5 tristate "Virtual Local CAN Interface (vcan)"
7 Similar to the network loopback devices, vcan offers a
8 virtual local CAN interface.
10 This driver can also be built as a module. If so, the module
14 tristate "Virtual CAN Tunnel (vxcan)"
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.
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.
28 This driver can also be built as a module. If so, the module
32 tristate "Serial / USB serial CAN Adaptors (slcan)"
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.
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
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.
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.
52 tristate "Platform CAN drivers with Netlink support"
55 Enables the common framework for platform CAN drivers with Netlink
56 support. This is the standard library for CAN drivers.
61 config CAN_CALC_BITTIMING
62 bool "CAN bit-timing calculation"
65 If enabled, CAN bit-timing parameters will be calculated for the
66 bit-rate specified via Netlink argument "bitrate" when the device
67 get started. This works fine for the most common CAN controllers
68 with standard bit-rates but may fail for exotic bit-rates or CAN
69 source clock frequencies. Disabling saves some space, but then the
70 bit-timing parameters must be specified directly using the Netlink
71 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
75 tristate "Atmel AT91 onchip CAN controller"
76 depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM
78 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
79 and AT91SAM9X5 processors.
82 tristate "Support for Freescale FLEXCAN based chips"
83 depends on OF || COLDFIRE || COMPILE_TEST
86 Say Y here if you want to support for Freescale FlexCAN.
89 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
90 depends on OF && HAS_DMA && HAS_IOMEM
92 Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
93 Note that the driver supports little endian, even though little
94 endian syntheses of the cores would need some modifications on
95 the hardware level to work.
98 tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
99 depends on MFD_JANZ_CMODIO
101 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
102 connects to a MODULbus carrier board.
104 This driver can also be built as a module. If so, the module will be
105 called janz-ican3.ko.
107 config CAN_KVASER_PCIEFD
109 tristate "Kvaser PCIe FD cards"
112 This is a driver for the Kvaser PCI Express CAN FD family.
116 Kvaser PCIEcan 2xHS v2
118 Kvaser Mini PCI Express HS v2
119 Kvaser Mini PCI Express 2xHS v2
122 tristate "Allwinner A10 CAN controller"
123 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
125 Say Y here if you want to use CAN controller found on Allwinner
128 To compile this driver as a module, choose M here: the module will
133 tristate "TI High End CAN Controller"
135 Driver for TI HECC (High End CAN Controller) module found on many
136 TI devices. The device specifications are available from www.ti.com
139 tristate "Xilinx CAN"
140 depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST
141 depends on COMMON_CLK && HAS_IOMEM
143 Xilinx CAN driver. This driver supports both soft AXI CAN IP and
147 tristate "Intel EG20T PCH CAN controller"
148 depends on PCI && (X86_32 || COMPILE_TEST)
150 This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
151 is an IOH for x86 embedded processor (Intel Atom E6xx series).
152 This driver can access CAN bus.
154 source "drivers/net/can/c_can/Kconfig"
155 source "drivers/net/can/cc770/Kconfig"
156 source "drivers/net/can/ctucanfd/Kconfig"
157 source "drivers/net/can/ifi_canfd/Kconfig"
158 source "drivers/net/can/m_can/Kconfig"
159 source "drivers/net/can/mscan/Kconfig"
160 source "drivers/net/can/peak_canfd/Kconfig"
161 source "drivers/net/can/rcar/Kconfig"
162 source "drivers/net/can/sja1000/Kconfig"
163 source "drivers/net/can/softing/Kconfig"
164 source "drivers/net/can/spi/Kconfig"
165 source "drivers/net/can/usb/Kconfig"
169 config CAN_DEBUG_DEVICES
170 bool "CAN devices debugging messages"
172 Say Y here if you want the CAN device drivers to produce a bunch of
173 debug messages to the system log. Select this if you are having
174 a problem with CAN support and want to see more of what is going