xref: /openbmc/linux/drivers/net/can/Kconfig (revision 1f223208)
1# SPDX-License-Identifier: GPL-2.0-only
2
3menuconfig CAN_DEV
4	tristate "CAN Device Drivers"
5	default y
6	depends on CAN
7	help
8	  Controller Area Network (CAN) is serial communications protocol up to
9	  1Mbit/s for its original release (now known as Classical CAN) and up
10	  to 8Mbit/s for the more recent CAN with Flexible Data-Rate
11	  (CAN-FD). The CAN bus was originally mainly for automotive, but is now
12	  widely used in marine (NMEA2000), industrial, and medical
13	  applications. More information on the CAN network protocol family
14	  PF_CAN is contained in <Documentation/networking/can.rst>.
15
16	  This section contains all the CAN(-FD) device drivers including the
17	  virtual ones. If you own such devices or plan to use the virtual CAN
18	  interfaces to develop applications, say Y here.
19
20	  To compile as a module, choose M here: the module will be called
21	  can-dev.
22
23if CAN_DEV
24
25config CAN_VCAN
26	tristate "Virtual Local CAN Interface (vcan)"
27	help
28	  Similar to the network loopback devices, vcan offers a
29	  virtual local CAN interface.
30
31	  This driver can also be built as a module.  If so, the module
32	  will be called vcan.
33
34config CAN_VXCAN
35	tristate "Virtual CAN Tunnel (vxcan)"
36	help
37	  Similar to the virtual ethernet driver veth, vxcan implements a
38	  local CAN traffic tunnel between two virtual CAN network devices.
39	  When creating a vxcan, two vxcan devices are created as pair.
40	  When one end receives the packet it appears on its pair and vice
41	  versa. The vxcan can be used for cross namespace communication.
42
43	  In opposite to vcan loopback devices the vxcan only forwards CAN
44	  frames to its pair and does *not* provide a local echo of sent
45	  CAN frames. To disable a potential echo in af_can.c the vxcan driver
46	  announces IFF_ECHO in the interface flags. To have a clean start
47	  in each namespace the CAN GW hop counter is set to zero.
48
49	  This driver can also be built as a module.  If so, the module
50	  will be called vxcan.
51
52config CAN_NETLINK
53	bool "CAN device drivers with Netlink support"
54	default y
55	help
56	  Enables the common framework for CAN device drivers. This is the
57	  standard library and provides features for the Netlink interface such
58	  as bittiming validation, support of CAN error states, device restart
59	  and others.
60
61	  The additional features selected by this option will be added to the
62	  can-dev module.
63
64	  This is required by all platform and hardware CAN drivers. If you
65	  plan to use such devices or if unsure, say Y.
66
67if CAN_NETLINK
68
69config CAN_CALC_BITTIMING
70	bool "CAN bit-timing calculation"
71	default y
72	help
73	  If enabled, CAN bit-timing parameters will be calculated for the
74	  bit-rate specified via Netlink argument "bitrate" when the device
75	  get started. This works fine for the most common CAN controllers
76	  with standard bit-rates but may fail for exotic bit-rates or CAN
77	  source clock frequencies. Disabling saves some space, but then the
78	  bit-timing parameters must be specified directly using the Netlink
79	  arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
80
81	  The additional features selected by this option will be added to the
82	  can-dev module.
83
84	  If unsure, say Y.
85
86config CAN_RX_OFFLOAD
87	bool
88
89config CAN_AT91
90	tristate "Atmel AT91 onchip CAN controller"
91	depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM
92	help
93	  This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
94	  and AT91SAM9X5 processors.
95
96config CAN_BXCAN
97	tristate "STM32 Basic Extended CAN (bxCAN) devices"
98	depends on ARCH_STM32 || COMPILE_TEST
99	depends on HAS_IOMEM
100	select CAN_RX_OFFLOAD
101	help
102	  Say yes here to build support for the STMicroelectronics STM32 basic
103	  extended CAN Controller (bxCAN).
104
105	  This driver can also be built as a module. If so, the module
106	  will be called bxcan.
107
108config CAN_CAN327
109	tristate "Serial / USB serial ELM327 based OBD-II Interfaces (can327)"
110	depends on TTY
111	select CAN_RX_OFFLOAD
112	help
113	  CAN driver for several 'low cost' OBD-II interfaces based on the
114	  ELM327 OBD-II interpreter chip.
115
116	  This is a best effort driver - the ELM327 interface was never
117	  designed to be used as a standalone CAN interface. However, it can
118	  still be used for simple request-response protocols (such as OBD II),
119	  and to monitor broadcast messages on a bus (such as in a vehicle).
120
121	  Please refer to the documentation for information on how to use it:
122	  Documentation/networking/device_drivers/can/can327.rst
123
124	  If this driver is built as a module, it will be called can327.
125
126config CAN_FLEXCAN
127	tristate "Support for Freescale FLEXCAN based chips"
128	depends on OF || COLDFIRE || COMPILE_TEST
129	depends on HAS_IOMEM
130	select CAN_RX_OFFLOAD
131	help
132	  Say Y here if you want to support for Freescale FlexCAN.
133
134config CAN_GRCAN
135	tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
136	depends on OF && HAS_DMA && HAS_IOMEM
137	help
138	  Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
139	  Note that the driver supports little endian, even though little
140	  endian syntheses of the cores would need some modifications on
141	  the hardware level to work.
142
143config CAN_JANZ_ICAN3
144	tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
145	depends on MFD_JANZ_CMODIO
146	help
147	  Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
148	  connects to a MODULbus carrier board.
149
150	  This driver can also be built as a module. If so, the module will be
151	  called janz-ican3.ko.
152
153config CAN_KVASER_PCIEFD
154	depends on PCI
155	tristate "Kvaser PCIe FD cards"
156	help
157	  This is a driver for the Kvaser PCI Express CAN FD family.
158
159	  Supported devices:
160	    Kvaser PCIEcan 4xHS
161	    Kvaser PCIEcan 2xHS v2
162	    Kvaser PCIEcan HS v2
163	    Kvaser PCIEcan 1xCAN v3
164	    Kvaser PCIEcan 2xCAN v3
165	    Kvaser PCIEcan 4xCAN v2
166	    Kvaser Mini PCI Express HS v2
167	    Kvaser Mini PCI Express 2xHS v2
168	    Kvaser Mini PCI Express 1xCAN v3
169	    Kvaser Mini PCI Express 2xCAN v3
170
171config CAN_SLCAN
172	tristate "Serial / USB serial CAN Adaptors (slcan)"
173	depends on TTY
174	help
175	  CAN driver for several 'low cost' CAN interfaces that are attached
176	  via serial lines or via USB-to-serial adapters using the LAWICEL
177	  ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
178
179	  As only the sending and receiving of CAN frames is implemented, this
180	  driver should work with the (serial/USB) CAN hardware from:
181	  www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
182
183	  Userspace tools to attach the SLCAN line discipline (slcan_attach,
184	  slcand) can be found in the can-utils at the linux-can project, see
185	  https://github.com/linux-can/can-utils for details.
186
187	  The slcan driver supports up to 10 CAN netdevices by default which
188	  can be changed by the 'maxdev=xx' module option. This driver can
189	  also be built as a module. If so, the module will be called slcan.
190
191config CAN_SUN4I
192	tristate "Allwinner A10 CAN controller"
193	depends on MACH_SUN4I || MACH_SUN7I || (RISCV && ARCH_SUNXI) || COMPILE_TEST
194	help
195	  Say Y here if you want to use CAN controller found on Allwinner
196	  A10/A20/D1 SoCs.
197
198	  To compile this driver as a module, choose M here: the module will
199	  be called sun4i_can.
200
201config CAN_TI_HECC
202	depends on ARM
203	tristate "TI High End CAN Controller"
204	select CAN_RX_OFFLOAD
205	help
206	  Driver for TI HECC (High End CAN Controller) module found on many
207	  TI devices. The device specifications are available from www.ti.com
208
209config CAN_XILINXCAN
210	tristate "Xilinx CAN"
211	depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST
212	depends on COMMON_CLK && HAS_IOMEM
213	help
214	  Xilinx CAN driver. This driver supports both soft AXI CAN IP and
215	  Zynq CANPS IP.
216
217source "drivers/net/can/c_can/Kconfig"
218source "drivers/net/can/cc770/Kconfig"
219source "drivers/net/can/ctucanfd/Kconfig"
220source "drivers/net/can/ifi_canfd/Kconfig"
221source "drivers/net/can/m_can/Kconfig"
222source "drivers/net/can/mscan/Kconfig"
223source "drivers/net/can/peak_canfd/Kconfig"
224source "drivers/net/can/rcar/Kconfig"
225source "drivers/net/can/sja1000/Kconfig"
226source "drivers/net/can/softing/Kconfig"
227source "drivers/net/can/spi/Kconfig"
228source "drivers/net/can/usb/Kconfig"
229
230endif #CAN_NETLINK
231
232config CAN_DEBUG_DEVICES
233	bool "CAN devices debugging messages"
234	help
235	  Say Y here if you want the CAN device drivers to produce a bunch of
236	  debug messages to the system log.  Select this if you are having
237	  a problem with CAN support and want to see more of what is going
238	  on.
239
240endif #CAN_DEV
241