Kconfig revision 77136836aef2c7ce9745e765c1e51a14e3933931 
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
39config CAN_CALC_BITTIMING
40	bool "CAN bit-timing calculation"
41	depends on CAN_DEV
42	default y
43	---help---
44	  If enabled, CAN bit-timing parameters will be calculated for the
45	  bit-rate specified via Netlink argument "bitrate" when the device
46	  get started. This works fine for the most common CAN controllers
47	  with standard bit-rates but may fail for exotic bit-rates or CAN
48	  source clock frequencies. Disabling saves some space, but then the
49	  bit-timing parameters must be specified directly using the Netlink
50	  arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
51	  If unsure, say Y.
52
53config CAN_AT91
54	tristate "Atmel AT91 onchip CAN controller"
55	depends on CAN_DEV && (ARCH_AT91SAM9263 || ARCH_AT91SAM9X5)
56	---help---
57	  This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
58	  and AT91SAM9X5 processors.
59
60config CAN_TI_HECC
61	depends on CAN_DEV && ARCH_OMAP3
62	tristate "TI High End CAN Controller"
63	---help---
64	  Driver for TI HECC (High End CAN Controller) module found on many
65	  TI devices. The device specifications are available from www.ti.com
66
67config CAN_MCP251X
68	tristate "Microchip MCP251x SPI CAN controllers"
69	depends on CAN_DEV && SPI && HAS_DMA
70	---help---
71	  Driver for the Microchip MCP251x SPI CAN controllers.
72
73config CAN_BFIN
74	depends on CAN_DEV && (BF534 || BF536 || BF537 || BF538 || BF539 || BF54x)
75	tristate "Analog Devices Blackfin on-chip CAN"
76	---help---
77	  Driver for the Analog Devices Blackfin on-chip CAN controllers
78
79	  To compile this driver as a module, choose M here: the
80	  module will be called bfin_can.
81
82config CAN_JANZ_ICAN3
83	tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
84	depends on CAN_DEV && MFD_JANZ_CMODIO
85	---help---
86	  Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
87	  connects to a MODULbus carrier board.
88
89	  This driver can also be built as a module. If so, the module will be
90	  called janz-ican3.ko.
91
92config HAVE_CAN_FLEXCAN
93	bool
94
95config CAN_FLEXCAN
96	tristate "Support for Freescale FLEXCAN based chips"
97	depends on CAN_DEV && HAVE_CAN_FLEXCAN
98	---help---
99	  Say Y here if you want to support for Freescale FlexCAN.
100
101config PCH_CAN
102	tristate "Intel EG20T PCH CAN controller"
103	depends on CAN_DEV && PCI
104	---help---
105	  This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
106	  is an IOH for x86 embedded processor (Intel Atom E6xx series).
107	  This driver can access CAN bus.
108
109config CAN_GRCAN
110	tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
111	depends on CAN_DEV && OF
112	---help---
113	  Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
114	  Note that the driver supports little endian, even though little
115	  endian syntheses of the cores would need some modifications on
116	  the hardware level to work.
117
118source "drivers/net/can/mscan/Kconfig"
119
120source "drivers/net/can/sja1000/Kconfig"
121
122source "drivers/net/can/c_can/Kconfig"
123
124source "drivers/net/can/cc770/Kconfig"
125
126source "drivers/net/can/usb/Kconfig"
127
128source "drivers/net/can/softing/Kconfig"
129
130config CAN_DEBUG_DEVICES
131	bool "CAN devices debugging messages"
132	---help---
133	  Say Y here if you want the CAN device drivers to produce a bunch of
134	  debug messages to the system log.  Select this if you are having
135	  a problem with CAN support and want to see more of what is going
136	  on.
137
138endmenu
139