Kconfig revision 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c 
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.mictronic.com / 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
62	---help---
63	  This is a driver for the SoC CAN controller in Atmel's AT91SAM9263.
64
65config CAN_TI_HECC
66	depends on CAN_DEV && ARCH_OMAP3
67	tristate "TI High End CAN Controller"
68	---help---
69	  Driver for TI HECC (High End CAN Controller) module found on many
70	  TI devices. The device specifications are available from www.ti.com
71
72config CAN_MCP251X
73	tristate "Microchip MCP251x SPI CAN controllers"
74	depends on CAN_DEV && SPI && HAS_DMA
75	---help---
76	  Driver for the Microchip MCP251x SPI CAN controllers.
77
78config CAN_BFIN
79	depends on CAN_DEV && (BF534 || BF536 || BF537 || BF538 || BF539 || BF54x)
80	tristate "Analog Devices Blackfin on-chip CAN"
81	---help---
82	  Driver for the Analog Devices Blackfin on-chip CAN controllers
83
84	  To compile this driver as a module, choose M here: the
85	  module will be called bfin_can.
86
87config CAN_JANZ_ICAN3
88	tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
89	depends on CAN_DEV && MFD_JANZ_CMODIO
90	---help---
91	  Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
92	  connects to a MODULbus carrier board.
93
94	  This driver can also be built as a module. If so, the module will be
95	  called janz-ican3.ko.
96
97config HAVE_CAN_FLEXCAN
98	bool
99
100config CAN_FLEXCAN
101	tristate "Support for Freescale FLEXCAN based chips"
102	depends on CAN_DEV && HAVE_CAN_FLEXCAN
103	---help---
104	  Say Y here if you want to support for Freescale FlexCAN.
105
106config PCH_CAN
107	tristate "PCH CAN"
108	depends on CAN_DEV && PCI
109	---help---
110	  This driver is for PCH CAN of Topcliff which is an IOH for x86
111	  embedded processor.
112	  This driver can access CAN bus.
113
114source "drivers/net/can/mscan/Kconfig"
115
116source "drivers/net/can/sja1000/Kconfig"
117
118source "drivers/net/can/usb/Kconfig"
119
120source "drivers/net/can/softing/Kconfig"
121
122config CAN_DEBUG_DEVICES
123	bool "CAN devices debugging messages"
124	depends on CAN
125	default N
126	---help---
127	  Say Y here if you want the CAN device drivers to produce a bunch of
128	  debug messages to the system log.  Select this if you are having
129	  a problem with CAN support and want to see more of what is going
130	  on.
131
132endmenu
133