Kconfig revision 702171adeed3607ee9603ec30ce081411e36ae42
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_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
38config CAN_SJA1000
39	depends on CAN_DEV && HAS_IOMEM
40	tristate "Philips SJA1000"
41	---help---
42	  Driver for the SJA1000 CAN controllers from Philips or NXP
43
44config CAN_SJA1000_ISA
45	depends on CAN_SJA1000 && ISA
46	tristate "ISA Bus based legacy SJA1000 driver"
47	---help---
48	  This driver adds legacy support for SJA1000 chips connected to
49	  the ISA bus using I/O port, memory mapped or indirect access.
50
51config CAN_SJA1000_PLATFORM
52	depends on CAN_SJA1000
53	tristate "Generic Platform Bus based SJA1000 driver"
54	---help---
55	  This driver adds support for the SJA1000 chips connected to
56	  the "platform bus" (Linux abstraction for directly to the
57	  processor attached devices).  Which can be found on various
58	  boards from Phytec (http://www.phytec.de) like the PCM027,
59	  PCM038.
60
61config CAN_SJA1000_OF_PLATFORM
62	depends on CAN_SJA1000 && PPC_OF
63	tristate "Generic OF Platform Bus based SJA1000 driver"
64	---help---
65	  This driver adds support for the SJA1000 chips connected to
66	  the OpenFirmware "platform bus" found on embedded systems with
67	  OpenFirmware bindings, e.g. if you have a PowerPC based system
68	  you may want to enable this option.
69
70config CAN_EMS_PCI
71	tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card"
72	depends on PCI && CAN_SJA1000
73	---help---
74	  This driver is for the one, two or four channel CPC-PCI,
75	  CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche
76	  (http://www.ems-wuensche.de).
77
78config CAN_EMS_USB
79	tristate "EMS CPC-USB/ARM7 CAN/USB interface"
80	depends on USB && CAN_DEV
81	---help---
82	  This driver is for the one channel CPC-USB/ARM7 CAN/USB interface
83	  from from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
84
85config CAN_KVASER_PCI
86	tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards"
87	depends on PCI && CAN_SJA1000
88	---help---
89	  This driver is for the the PCIcanx and PCIcan cards (1, 2 or
90	  4 channel) from Kvaser (http://www.kvaser.com).
91
92config CAN_DEBUG_DEVICES
93	bool "CAN devices debugging messages"
94	depends on CAN
95	default N
96	---help---
97	  Say Y here if you want the CAN device drivers to produce a bunch of
98	  debug messages to the system log.  Select this if you are having
99	  a problem with CAN support and want to see more of what is going
100	  on.
101
102endmenu
103