Commit | Line | Data |
---|---|---|
ec8f24b7 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
ccb29637 | 2 | menu "CAN Device Drivers" |
ccb29637 OH |
3 | |
4 | config CAN_VCAN | |
5 | tristate "Virtual Local CAN Interface (vcan)" | |
ccb29637 OH |
6 | ---help--- |
7 | Similar to the network loopback devices, vcan offers a | |
8 | virtual local CAN interface. | |
9 | ||
10 | This driver can also be built as a module. If so, the module | |
11 | will be called vcan. | |
12 | ||
a8f820a3 OH |
13 | config CAN_VXCAN |
14 | tristate "Virtual CAN Tunnel (vxcan)" | |
15 | ---help--- | |
16 | Similar to the virtual ethernet driver veth, vxcan implements a | |
17 | local CAN traffic tunnel between two virtual CAN network devices. | |
18 | When creating a vxcan, two vxcan devices are created as pair. | |
19 | When one end receives the packet it appears on its pair and vice | |
20 | versa. The vxcan can be used for cross namespace communication. | |
21 | ||
22 | In opposite to vcan loopback devices the vxcan only forwards CAN | |
23 | frames to its pair and does *not* provide a local echo of sent | |
24 | CAN frames. To disable a potential echo in af_can.c the vxcan driver | |
25 | announces IFF_ECHO in the interface flags. To have a clean start | |
26 | in each namespace the CAN GW hop counter is set to zero. | |
27 | ||
28 | This driver can also be built as a module. If so, the module | |
29 | will be called vxcan. | |
30 | ||
a1044e36 OH |
31 | config CAN_SLCAN |
32 | tristate "Serial / USB serial CAN Adaptors (slcan)" | |
21eaab6d | 33 | depends on TTY |
a1044e36 OH |
34 | ---help--- |
35 | CAN driver for several 'low cost' CAN interfaces that are attached | |
36 | via serial lines or via USB-to-serial adapters using the LAWICEL | |
37 | ASCII protocol. The driver implements the tty linediscipline N_SLCAN. | |
38 | ||
39 | As only the sending and receiving of CAN frames is implemented, this | |
40 | driver should work with the (serial/USB) CAN hardware from: | |
c128df73 | 41 | www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de |
a1044e36 OH |
42 | |
43 | Userspace tools to attach the SLCAN line discipline (slcan_attach, | |
44 | slcand) can be found in the can-utils at the SocketCAN SVN, see | |
45 | http://developer.berlios.de/projects/socketcan for details. | |
46 | ||
47 | The slcan driver supports up to 10 CAN netdevices by default which | |
48 | can be changed by the 'maxdev=xx' module option. This driver can | |
49 | also be built as a module. If so, the module will be called slcan. | |
50 | ||
39549eef WG |
51 | config CAN_DEV |
52 | tristate "Platform CAN drivers with Netlink support" | |
a30d5155 | 53 | default y |
39549eef WG |
54 | ---help--- |
55 | Enables the common framework for platform CAN drivers with Netlink | |
56 | support. This is the standard library for CAN drivers. | |
57 | If unsure, say Y. | |
58 | ||
6586c5d7 MKB |
59 | if CAN_DEV |
60 | ||
39549eef WG |
61 | config CAN_CALC_BITTIMING |
62 | bool "CAN bit-timing calculation" | |
a30d5155 | 63 | default y |
39549eef WG |
64 | ---help--- |
65 | If enabled, CAN bit-timing parameters will be calculated for the | |
66 | bit-rate specified via Netlink argument "bitrate" when the device | |
67 | get started. This works fine for the most common CAN controllers | |
68 | with standard bit-rates but may fail for exotic bit-rates or CAN | |
69 | source clock frequencies. Disabling saves some space, but then the | |
70 | bit-timing parameters must be specified directly using the Netlink | |
71 | arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw". | |
72 | If unsure, say Y. | |
73 | ||
996a953d FB |
74 | config CAN_LEDS |
75 | bool "Enable LED triggers for Netlink based drivers" | |
76 | depends on LEDS_CLASS | |
30f3b421 UKK |
77 | # The netdev trigger (LEDS_TRIGGER_NETDEV) should be able to do |
78 | # everything that this driver is doing. This is marked as broken | |
79 | # because it uses stuff that is intended to be changed or removed. | |
80 | # Please consider switching to the netdev trigger and confirm it | |
81 | # fulfills your needs instead of fixing this driver. | |
82 | depends on BROKEN | |
996a953d FB |
83 | select LEDS_TRIGGERS |
84 | ---help--- | |
85 | This option adds two LED triggers for packet receive and transmit | |
86 | events on each supported CAN device. | |
87 | ||
88 | Say Y here if you are working on a system with led-class supported | |
89 | LEDs and you want to use them as canbus activity indicators. | |
90 | ||
68f40152 MKB |
91 | config CAN_AT91 |
92 | tristate "Atmel AT91 onchip CAN controller" | |
9dc8be28 | 93 | depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM |
68f40152 | 94 | ---help--- |
b9e379bc UKK |
95 | This is a driver for the SoC CAN controller in Atmel's AT91SAM9263 |
96 | and AT91SAM9X5 processors. | |
68f40152 | 97 | |
e955cead MKB |
98 | config CAN_FLEXCAN |
99 | tristate "Support for Freescale FLEXCAN based chips" | |
0f8af56f | 100 | depends on OF && HAS_IOMEM |
e955cead MKB |
101 | ---help--- |
102 | Say Y here if you want to support for Freescale FlexCAN. | |
103 | ||
6cec9b07 AL |
104 | config CAN_GRCAN |
105 | tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices" | |
2fb42aab | 106 | depends on OF && HAS_DMA |
6cec9b07 AL |
107 | ---help--- |
108 | Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN. | |
109 | Note that the driver supports little endian, even though little | |
110 | endian syntheses of the cores would need some modifications on | |
111 | the hardware level to work. | |
112 | ||
26821162 MKB |
113 | config CAN_JANZ_ICAN3 |
114 | tristate "Janz VMOD-ICAN3 Intelligent CAN controller" | |
115 | depends on MFD_JANZ_CMODIO | |
116 | ---help--- | |
117 | Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which | |
118 | connects to a MODULbus carrier board. | |
119 | ||
120 | This driver can also be built as a module. If so, the module will be | |
121 | called janz-ican3.ko. | |
122 | ||
0738eff1 GB |
123 | config CAN_SUN4I |
124 | tristate "Allwinner A10 CAN controller" | |
125 | depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST | |
126 | ---help--- | |
127 | Say Y here if you want to use CAN controller found on Allwinner | |
128 | A10/A20 SoCs. | |
129 | ||
130 | To compile this driver as a module, choose M here: the module will | |
131 | be called sun4i_can. | |
132 | ||
26821162 MKB |
133 | config CAN_TI_HECC |
134 | depends on ARM | |
135 | tristate "TI High End CAN Controller" | |
136 | ---help--- | |
137 | Driver for TI HECC (High End CAN Controller) module found on many | |
138 | TI devices. The device specifications are available from www.ti.com | |
139 | ||
b1201e44 KA |
140 | config CAN_XILINXCAN |
141 | tristate "Xilinx CAN" | |
963a822b | 142 | depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST |
b1201e44 KA |
143 | depends on COMMON_CLK && HAS_IOMEM |
144 | ---help--- | |
145 | Xilinx CAN driver. This driver supports both soft AXI CAN IP and | |
146 | Zynq CANPS IP. | |
147 | ||
26821162 MKB |
148 | config PCH_CAN |
149 | tristate "Intel EG20T PCH CAN controller" | |
150 | depends on PCI && (X86_32 || COMPILE_TEST) | |
151 | ---help--- | |
152 | This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which | |
153 | is an IOH for x86 embedded processor (Intel Atom E6xx series). | |
154 | This driver can access CAN bus. | |
b93cf3f0 | 155 | |
881ff67a | 156 | source "drivers/net/can/c_can/Kconfig" |
2a367c3a | 157 | source "drivers/net/can/cc770/Kconfig" |
0c4d9c94 | 158 | source "drivers/net/can/ifi_canfd/Kconfig" |
83407c7f MV |
159 | source "drivers/net/can/m_can/Kconfig" |
160 | source "drivers/net/can/mscan/Kconfig" | |
8ac8321e | 161 | source "drivers/net/can/peak_canfd/Kconfig" |
dd3bd23e | 162 | source "drivers/net/can/rcar/Kconfig" |
83407c7f MV |
163 | source "drivers/net/can/sja1000/Kconfig" |
164 | source "drivers/net/can/softing/Kconfig" | |
869ba1e6 | 165 | source "drivers/net/can/spi/Kconfig" |
b93cf3f0 OH |
166 | source "drivers/net/can/usb/Kconfig" |
167 | ||
6586c5d7 MKB |
168 | endif |
169 | ||
ccb29637 OH |
170 | config CAN_DEBUG_DEVICES |
171 | bool "CAN devices debugging messages" | |
ccb29637 OH |
172 | ---help--- |
173 | Say Y here if you want the CAN device drivers to produce a bunch of | |
174 | debug messages to the system log. Select this if you are having | |
175 | a problem with CAN support and want to see more of what is going | |
176 | on. | |
177 | ||
178 | endmenu |