Kconfig revision b9e379bccda6913f7baece42cd249824c0758b97 
1menu "CAN Device Drivers"
2	depends on CAN
3
4config CAN_VCAN
5	tristate "Virtual Local CAN Interface (vcan)"
6	depends on CAN
7	default N
8	---help---
9	  Similar to the network loopback devices, vcan offers a
10	  virtual local CAN interface.
11
12	  This driver can also be built as a module.  If so, the module
13	  will be called vcan.
14
15config CAN_SLCAN
16	tristate "Serial / USB serial CAN Adaptors (slcan)"
17	depends on CAN
18	default N
19	---help---
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.
23
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
27
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.
31
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.
35
36config CAN_DEV
37	tristate "Platform CAN drivers with Netlink support"
38	depends on CAN
39	default Y
40	---help---
41	  Enables the common framework for platform CAN drivers with Netlink
42	  support. This is the standard library for CAN drivers.
43	  If unsure, say Y.
44
45config CAN_CALC_BITTIMING
46	bool "CAN bit-timing calculation"
47	depends on CAN_DEV
48	default Y
49	---help---
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".
57	  If unsure, say Y.
58
59config CAN_AT91
60	tristate "Atmel AT91 onchip CAN controller"
61	depends on CAN_DEV && (ARCH_AT91SAM9263 || ARCH_AT91SAM9X5)
62	---help---
63	  This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
64	  and AT91SAM9X5 processors.
65
66config CAN_TI_HECC
67	depends on CAN_DEV && ARCH_OMAP3
68	tristate "TI High End CAN Controller"
69	---help---
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
72
73config CAN_MCP251X
74	tristate "Microchip MCP251x SPI CAN controllers"
75	depends on CAN_DEV && SPI && HAS_DMA
76	---help---
77	  Driver for the Microchip MCP251x SPI CAN controllers.
78
79config CAN_BFIN
80	depends on CAN_DEV && (BF534 || BF536 || BF537 || BF538 || BF539 || BF54x)
81	tristate "Analog Devices Blackfin on-chip CAN"
82	---help---
83	  Driver for the Analog Devices Blackfin on-chip CAN controllers
84
85	  To compile this driver as a module, choose M here: the
86	  module will be called bfin_can.
87
88config CAN_JANZ_ICAN3
89	tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
90	depends on CAN_DEV && MFD_JANZ_CMODIO
91	---help---
92	  Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
93	  connects to a MODULbus carrier board.
94
95	  This driver can also be built as a module. If so, the module will be
96	  called janz-ican3.ko.
97
98config HAVE_CAN_FLEXCAN
99	bool
100
101config CAN_FLEXCAN
102	tristate "Support for Freescale FLEXCAN based chips"
103	depends on CAN_DEV && HAVE_CAN_FLEXCAN
104	---help---
105	  Say Y here if you want to support for Freescale FlexCAN.
106
107config PCH_CAN
108	tristate "PCH CAN"
109	depends on CAN_DEV && PCI
110	---help---
111	  This driver is for PCH CAN of Topcliff which is an IOH for x86
112	  embedded processor.
113	  This driver can access CAN bus.
114
115source "drivers/net/can/mscan/Kconfig"
116
117source "drivers/net/can/sja1000/Kconfig"
118
119source "drivers/net/can/c_can/Kconfig"
120
121source "drivers/net/can/usb/Kconfig"
122
123source "drivers/net/can/softing/Kconfig"
124
125config CAN_DEBUG_DEVICES
126	bool "CAN devices debugging messages"
127	depends on CAN
128	default N
129	---help---
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
133	  on.
134
135endmenu
136