blob: 77adb8ef6e4f022db7b2765817e45078a6f5bc04 [file] [log] [blame]
Oliver Hartkoppccb29632007-11-16 15:56:08 -08001menu "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
Wolfgang Grandegger39549ee2009-05-15 23:39:29 +000015config CAN_DEV
16 tristate "Platform CAN drivers with Netlink support"
17 depends on CAN
18 default Y
19 ---help---
20 Enables the common framework for platform CAN drivers with Netlink
21 support. This is the standard library for CAN drivers.
22 If unsure, say Y.
23
24config CAN_CALC_BITTIMING
25 bool "CAN bit-timing calculation"
26 depends on CAN_DEV
27 default Y
28 ---help---
29 If enabled, CAN bit-timing parameters will be calculated for the
30 bit-rate specified via Netlink argument "bitrate" when the device
31 get started. This works fine for the most common CAN controllers
32 with standard bit-rates but may fail for exotic bit-rates or CAN
33 source clock frequencies. Disabling saves some space, but then the
34 bit-timing parameters must be specified directly using the Netlink
35 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
36 If unsure, say Y.
37
Oliver Hartkoppccb29632007-11-16 15:56:08 -080038config CAN_DEBUG_DEVICES
39 bool "CAN devices debugging messages"
40 depends on CAN
41 default N
42 ---help---
43 Say Y here if you want the CAN device drivers to produce a bunch of
44 debug messages to the system log. Select this if you are having
45 a problem with CAN support and want to see more of what is going
46 on.
47
48endmenu