1menu "CAN Device Drivers" 2 3config 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 12config 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 30config 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 50config 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 58if CAN_DEV 59 60config 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 73config 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 84config 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 91config CAN_FLEXCAN 92 tristate "Support for Freescale FLEXCAN based chips" 93 depends on ARM || PPC 94 ---help--- 95 Say Y here if you want to support for Freescale FlexCAN. 96 97config CAN_GRCAN 98 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices" 99 depends on OF && HAS_DMA 100 ---help--- 101 Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN. 102 Note that the driver supports little endian, even though little 103 endian syntheses of the cores would need some modifications on 104 the hardware level to work. 105 106config CAN_JANZ_ICAN3 107 tristate "Janz VMOD-ICAN3 Intelligent CAN controller" 108 depends on MFD_JANZ_CMODIO 109 ---help--- 110 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which 111 connects to a MODULbus carrier board. 112 113 This driver can also be built as a module. If so, the module will be 114 called janz-ican3.ko. 115 116config CAN_SUN4I 117 tristate "Allwinner A10 CAN controller" 118 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST 119 ---help--- 120 Say Y here if you want to use CAN controller found on Allwinner 121 A10/A20 SoCs. 122 123 To compile this driver as a module, choose M here: the module will 124 be called sun4i_can. 125 126config CAN_TI_HECC 127 depends on ARM 128 tristate "TI High End CAN Controller" 129 ---help--- 130 Driver for TI HECC (High End CAN Controller) module found on many 131 TI devices. The device specifications are available from www.ti.com 132 133config CAN_XILINXCAN 134 tristate "Xilinx CAN" 135 depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST 136 depends on COMMON_CLK && HAS_IOMEM 137 ---help--- 138 Xilinx CAN driver. This driver supports both soft AXI CAN IP and 139 Zynq CANPS IP. 140 141config PCH_CAN 142 tristate "Intel EG20T PCH CAN controller" 143 depends on PCI && (X86_32 || COMPILE_TEST) 144 ---help--- 145 This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which 146 is an IOH for x86 embedded processor (Intel Atom E6xx series). 147 This driver can access CAN bus. 148 149source "drivers/net/can/c_can/Kconfig" 150source "drivers/net/can/cc770/Kconfig" 151source "drivers/net/can/ifi_canfd/Kconfig" 152source "drivers/net/can/m_can/Kconfig" 153source "drivers/net/can/mscan/Kconfig" 154source "drivers/net/can/peak_canfd/Kconfig" 155source "drivers/net/can/rcar/Kconfig" 156source "drivers/net/can/sja1000/Kconfig" 157source "drivers/net/can/softing/Kconfig" 158source "drivers/net/can/spi/Kconfig" 159source "drivers/net/can/usb/Kconfig" 160 161endif 162 163config CAN_DEBUG_DEVICES 164 bool "CAN devices debugging messages" 165 ---help--- 166 Say Y here if you want the CAN device drivers to produce a bunch of 167 debug messages to the system log. Select this if you are having 168 a problem with CAN support and want to see more of what is going 169 on. 170 171endmenu 172