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_SLCAN 13 tristate "Serial / USB serial CAN Adaptors (slcan)" 14 ---help--- 15 CAN driver for several 'low cost' CAN interfaces that are attached 16 via serial lines or via USB-to-serial adapters using the LAWICEL 17 ASCII protocol. The driver implements the tty linediscipline N_SLCAN. 18 19 As only the sending and receiving of CAN frames is implemented, this 20 driver should work with the (serial/USB) CAN hardware from: 21 www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de 22 23 Userspace tools to attach the SLCAN line discipline (slcan_attach, 24 slcand) can be found in the can-utils at the SocketCAN SVN, see 25 http://developer.berlios.de/projects/socketcan for details. 26 27 The slcan driver supports up to 10 CAN netdevices by default which 28 can be changed by the 'maxdev=xx' module option. This driver can 29 also be built as a module. If so, the module will be called slcan. 30 31config CAN_DEV 32 tristate "Platform CAN drivers with Netlink support" 33 default y 34 ---help--- 35 Enables the common framework for platform CAN drivers with Netlink 36 support. This is the standard library for CAN drivers. 37 If unsure, say Y. 38 39if CAN_DEV 40 41config CAN_CALC_BITTIMING 42 bool "CAN bit-timing calculation" 43 default y 44 ---help--- 45 If enabled, CAN bit-timing parameters will be calculated for the 46 bit-rate specified via Netlink argument "bitrate" when the device 47 get started. This works fine for the most common CAN controllers 48 with standard bit-rates but may fail for exotic bit-rates or CAN 49 source clock frequencies. Disabling saves some space, but then the 50 bit-timing parameters must be specified directly using the Netlink 51 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw". 52 If unsure, say Y. 53 54config CAN_LEDS 55 bool "Enable LED triggers for Netlink based drivers" 56 depends on LEDS_CLASS 57 select LEDS_TRIGGERS 58 ---help--- 59 This option adds two LED triggers for packet receive and transmit 60 events on each supported CAN device. 61 62 Say Y here if you are working on a system with led-class supported 63 LEDs and you want to use them as canbus activity indicators. 64 65config CAN_AT91 66 tristate "Atmel AT91 onchip CAN controller" 67 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9X5 68 ---help--- 69 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263 70 and AT91SAM9X5 processors. 71 72config CAN_TI_HECC 73 depends on ARCH_OMAP3 74 tristate "TI High End CAN Controller" 75 ---help--- 76 Driver for TI HECC (High End CAN Controller) module found on many 77 TI devices. The device specifications are available from www.ti.com 78 79config CAN_MCP251X 80 tristate "Microchip MCP251x SPI CAN controllers" 81 depends on SPI && HAS_DMA 82 ---help--- 83 Driver for the Microchip MCP251x SPI CAN controllers. 84 85config CAN_BFIN 86 depends on BF534 || BF536 || BF537 || BF538 || BF539 || BF54x 87 tristate "Analog Devices Blackfin on-chip CAN" 88 ---help--- 89 Driver for the Analog Devices Blackfin on-chip CAN controllers 90 91 To compile this driver as a module, choose M here: the 92 module will be called bfin_can. 93 94config CAN_JANZ_ICAN3 95 tristate "Janz VMOD-ICAN3 Intelligent CAN controller" 96 depends on MFD_JANZ_CMODIO 97 ---help--- 98 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which 99 connects to a MODULbus carrier board. 100 101 This driver can also be built as a module. If so, the module will be 102 called janz-ican3.ko. 103 104config HAVE_CAN_FLEXCAN 105 bool 106 107config CAN_FLEXCAN 108 tristate "Support for Freescale FLEXCAN based chips" 109 depends on HAVE_CAN_FLEXCAN 110 ---help--- 111 Say Y here if you want to support for Freescale FlexCAN. 112 113config PCH_CAN 114 tristate "Intel EG20T PCH CAN controller" 115 depends on PCI 116 ---help--- 117 This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which 118 is an IOH for x86 embedded processor (Intel Atom E6xx series). 119 This driver can access CAN bus. 120 121config CAN_GRCAN 122 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices" 123 depends on OF 124 ---help--- 125 Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN. 126 Note that the driver supports little endian, even though little 127 endian syntheses of the cores would need some modifications on 128 the hardware level to work. 129 130source "drivers/net/can/mscan/Kconfig" 131 132source "drivers/net/can/sja1000/Kconfig" 133 134source "drivers/net/can/c_can/Kconfig" 135 136source "drivers/net/can/cc770/Kconfig" 137 138source "drivers/net/can/usb/Kconfig" 139 140source "drivers/net/can/softing/Kconfig" 141 142endif 143 144config CAN_DEBUG_DEVICES 145 bool "CAN devices debugging messages" 146 ---help--- 147 Say Y here if you want the CAN device drivers to produce a bunch of 148 debug messages to the system log. Select this if you are having 149 a problem with CAN support and want to see more of what is going 150 on. 151 152endmenu 153