1 menu "CAN Device Drivers"
5 tristate "Virtual Local CAN Interface (vcan)"
9 Similar to the network loopback devices, vcan offers a
10 virtual local CAN interface.
12 This driver can also be built as a module. If so, the module
16 tristate "Serial / USB serial CAN Adaptors (slcan)"
20 CAN driver for several 'low cost' CAN interfaces that are attached
21 via serial lines or via USB-to-serial adapters using the LAWICEL
22 ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
24 As only the sending and receiving of CAN frames is implemented, this
25 driver should work with the (serial/USB) CAN hardware from:
26 www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
28 Userspace tools to attach the SLCAN line discipline (slcan_attach,
29 slcand) can be found in the can-utils at the SocketCAN SVN, see
30 http://developer.berlios.de/projects/socketcan for details.
32 The slcan driver supports up to 10 CAN netdevices by default which
33 can be changed by the 'maxdev=xx' module option. This driver can
34 also be built as a module. If so, the module will be called slcan.
37 tristate "Platform CAN drivers with Netlink support"
41 Enables the common framework for platform CAN drivers with Netlink
42 support. This is the standard library for CAN drivers.
45 config CAN_CALC_BITTIMING
46 bool "CAN bit-timing calculation"
50 If enabled, CAN bit-timing parameters will be calculated for the
51 bit-rate specified via Netlink argument "bitrate" when the device
52 get started. This works fine for the most common CAN controllers
53 with standard bit-rates but may fail for exotic bit-rates or CAN
54 source clock frequencies. Disabling saves some space, but then the
55 bit-timing parameters must be specified directly using the Netlink
56 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
60 tristate "Atmel AT91 onchip CAN controller"
61 depends on CAN_DEV && (ARCH_AT91SAM9263 || ARCH_AT91SAM9X5)
63 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
64 and AT91SAM9X5 processors.
67 depends on CAN_DEV && ARCH_OMAP3
68 tristate "TI High End CAN Controller"
70 Driver for TI HECC (High End CAN Controller) module found on many
71 TI devices. The device specifications are available from www.ti.com
74 tristate "Microchip MCP251x SPI CAN controllers"
75 depends on CAN_DEV && SPI && HAS_DMA
77 Driver for the Microchip MCP251x SPI CAN controllers.
80 depends on CAN_DEV && (BF534 || BF536 || BF537 || BF538 || BF539 || BF54x)
81 tristate "Analog Devices Blackfin on-chip CAN"
83 Driver for the Analog Devices Blackfin on-chip CAN controllers
85 To compile this driver as a module, choose M here: the
86 module will be called bfin_can.
89 tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
90 depends on CAN_DEV && MFD_JANZ_CMODIO
92 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
93 connects to a MODULbus carrier board.
95 This driver can also be built as a module. If so, the module will be
98 config HAVE_CAN_FLEXCAN
102 tristate "Support for Freescale FLEXCAN based chips"
103 depends on CAN_DEV && HAVE_CAN_FLEXCAN
105 Say Y here if you want to support for Freescale FlexCAN.
109 depends on CAN_DEV && PCI
111 This driver is for PCH CAN of Topcliff which is an IOH for x86
113 This driver can access CAN bus.
115 source "drivers/net/can/mscan/Kconfig"
117 source "drivers/net/can/sja1000/Kconfig"
119 source "drivers/net/can/c_can/Kconfig"
121 source "drivers/net/can/usb/Kconfig"
123 source "drivers/net/can/softing/Kconfig"
125 config CAN_DEBUG_DEVICES
126 bool "CAN devices debugging messages"
130 Say Y here if you want the CAN device drivers to produce a bunch of
131 debug messages to the system log. Select this if you are having
132 a problem with CAN support and want to see more of what is going