tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1# SPDX-License-Identifier: GPL-2.0-only
2menu "CAN Device Drivers"
3
4config CAN_VCAN
5 tristate "Virtual Local CAN Interface (vcan)"
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
13config 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
31config CAN_SLCAN
32 tristate "Serial / USB serial CAN Adaptors (slcan)"
33 depends on TTY
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:
41 www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
42
43 Userspace tools to attach the SLCAN line discipline (slcan_attach,
44 slcand) can be found in the can-utils at the linux-can project, see
45 https://github.com/linux-can/can-utils 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
51config CAN_DEV
52 tristate "Platform CAN drivers with Netlink support"
53 default y
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
59if CAN_DEV
60
61config CAN_CALC_BITTIMING
62 bool "CAN bit-timing calculation"
63 default y
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
74config CAN_LEDS
75 bool "Enable LED triggers for Netlink based drivers"
76 depends on LEDS_CLASS
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
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
91config CAN_AT91
92 tristate "Atmel AT91 onchip CAN controller"
93 depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM
94 help
95 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
96 and AT91SAM9X5 processors.
97
98config CAN_FLEXCAN
99 tristate "Support for Freescale FLEXCAN based chips"
100 depends on OF || COLDFIRE || COMPILE_TEST
101 depends on HAS_IOMEM
102 help
103 Say Y here if you want to support for Freescale FlexCAN.
104
105config CAN_GRCAN
106 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
107 depends on OF && HAS_DMA && HAS_IOMEM
108 help
109 Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
110 Note that the driver supports little endian, even though little
111 endian syntheses of the cores would need some modifications on
112 the hardware level to work.
113
114config CAN_JANZ_ICAN3
115 tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
116 depends on MFD_JANZ_CMODIO
117 help
118 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
119 connects to a MODULbus carrier board.
120
121 This driver can also be built as a module. If so, the module will be
122 called janz-ican3.ko.
123
124config CAN_KVASER_PCIEFD
125 depends on PCI
126 tristate "Kvaser PCIe FD cards"
127 select CRC32
128 help
129 This is a driver for the Kvaser PCI Express CAN FD family.
130
131 Supported devices:
132 Kvaser PCIEcan 4xHS
133 Kvaser PCIEcan 2xHS v2
134 Kvaser PCIEcan HS v2
135 Kvaser Mini PCI Express HS v2
136 Kvaser Mini PCI Express 2xHS v2
137
138config CAN_SUN4I
139 tristate "Allwinner A10 CAN controller"
140 depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
141 help
142 Say Y here if you want to use CAN controller found on Allwinner
143 A10/A20 SoCs.
144
145 To compile this driver as a module, choose M here: the module will
146 be called sun4i_can.
147
148config CAN_TI_HECC
149 depends on ARM
150 tristate "TI High End CAN Controller"
151 help
152 Driver for TI HECC (High End CAN Controller) module found on many
153 TI devices. The device specifications are available from www.ti.com
154
155config CAN_XILINXCAN
156 tristate "Xilinx CAN"
157 depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST
158 depends on COMMON_CLK && HAS_IOMEM
159 help
160 Xilinx CAN driver. This driver supports both soft AXI CAN IP and
161 Zynq CANPS IP.
162
163config PCH_CAN
164 tristate "Intel EG20T PCH CAN controller"
165 depends on PCI && (X86_32 || COMPILE_TEST)
166 help
167 This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
168 is an IOH for x86 embedded processor (Intel Atom E6xx series).
169 This driver can access CAN bus.
170
171source "drivers/net/can/c_can/Kconfig"
172source "drivers/net/can/cc770/Kconfig"
173source "drivers/net/can/ifi_canfd/Kconfig"
174source "drivers/net/can/m_can/Kconfig"
175source "drivers/net/can/mscan/Kconfig"
176source "drivers/net/can/peak_canfd/Kconfig"
177source "drivers/net/can/rcar/Kconfig"
178source "drivers/net/can/sja1000/Kconfig"
179source "drivers/net/can/softing/Kconfig"
180source "drivers/net/can/spi/Kconfig"
181source "drivers/net/can/usb/Kconfig"
182
183endif
184
185config CAN_DEBUG_DEVICES
186 bool "CAN devices debugging messages"
187 help
188 Say Y here if you want the CAN device drivers to produce a bunch of
189 debug messages to the system log. Select this if you are having
190 a problem with CAN support and want to see more of what is going
191 on.
192
193endmenu