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	select CAN_RX_OFFLOAD
 93	help
 94	  This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
 95	  and AT91SAM9X5 processors.
 96
 97config CAN_BXCAN
 98	tristate "STM32 Basic Extended CAN (bxCAN) devices"
 99	depends on ARCH_STM32 || COMPILE_TEST
100	depends on HAS_IOMEM
101	select CAN_RX_OFFLOAD
102	help
103	  Say yes here to build support for the STMicroelectronics STM32 basic
104	  extended CAN Controller (bxCAN).
105
106	  This driver can also be built as a module. If so, the module
107	  will be called bxcan.
108
109config CAN_CAN327
110	tristate "Serial / USB serial ELM327 based OBD-II Interfaces (can327)"
111	depends on TTY
112	select CAN_RX_OFFLOAD
113	help
114	  CAN driver for several 'low cost' OBD-II interfaces based on the
115	  ELM327 OBD-II interpreter chip.
116
117	  This is a best effort driver - the ELM327 interface was never
118	  designed to be used as a standalone CAN interface. However, it can
119	  still be used for simple request-response protocols (such as OBD II),
120	  and to monitor broadcast messages on a bus (such as in a vehicle).
121
122	  Please refer to the documentation for information on how to use it:
123	  Documentation/networking/device_drivers/can/can327.rst
124
125	  If this driver is built as a module, it will be called can327.
126
127config CAN_FLEXCAN
128	tristate "Support for Freescale FLEXCAN based chips"
129	depends on OF || COLDFIRE || COMPILE_TEST
130	depends on HAS_IOMEM
131	select CAN_RX_OFFLOAD
132	help
133	  Say Y here if you want to support for Freescale FlexCAN.
134
135config CAN_GRCAN
136	tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
137	depends on OF && HAS_DMA && HAS_IOMEM
138	help
139	  Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
140	  Note that the driver supports little endian, even though little
141	  endian syntheses of the cores would need some modifications on
142	  the hardware level to work.
143
144config CAN_JANZ_ICAN3
145	tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
146	depends on MFD_JANZ_CMODIO
147	help
148	  Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
149	  connects to a MODULbus carrier board.
150
151	  This driver can also be built as a module. If so, the module will be
152	  called janz-ican3.ko.
153
154config CAN_KVASER_PCIEFD
155	depends on PCI
156	tristate "Kvaser PCIe FD cards"
157	help
158	  This is a driver for the Kvaser PCI Express CAN FD family.
159
160	  Supported devices:
161	    Kvaser PCIEcan 4xHS
162	    Kvaser PCIEcan 2xHS v2
163	    Kvaser PCIEcan HS v2
164	    Kvaser PCIEcan 1xCAN v3
165	    Kvaser PCIEcan 2xCAN v3
166	    Kvaser PCIEcan 4xCAN v2
167	    Kvaser Mini PCI Express HS v2
168	    Kvaser Mini PCI Express 2xHS v2
169	    Kvaser Mini PCI Express 1xCAN v3
170	    Kvaser Mini PCI Express 2xCAN v3
171
172config CAN_SLCAN
173	tristate "Serial / USB serial CAN Adaptors (slcan)"
174	depends on TTY
175	help
176	  CAN driver for several 'low cost' CAN interfaces that are attached
177	  via serial lines or via USB-to-serial adapters using the LAWICEL
178	  ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
179
180	  As only the sending and receiving of CAN frames is implemented, this
181	  driver should work with the (serial/USB) CAN hardware from:
182	  www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
183
184	  Userspace tools to attach the SLCAN line discipline (slcan_attach,
185	  slcand) can be found in the can-utils at the linux-can project, see
186	  https://github.com/linux-can/can-utils for details.
187
188	  The slcan driver supports up to 10 CAN netdevices by default which
189	  can be changed by the 'maxdev=xx' module option. This driver can
190	  also be built as a module. If so, the module will be called slcan.
191
192config CAN_SUN4I
193	tristate "Allwinner A10 CAN controller"
194	depends on MACH_SUN4I || MACH_SUN7I || (RISCV && ARCH_SUNXI) || COMPILE_TEST
195	help
196	  Say Y here if you want to use CAN controller found on Allwinner
197	  A10/A20/D1 SoCs.
198
199	  To compile this driver as a module, choose M here: the module will
200	  be called sun4i_can.
201
202config CAN_TI_HECC
203	depends on ARM
204	tristate "TI High End CAN Controller"
205	select CAN_RX_OFFLOAD
206	help
207	  Driver for TI HECC (High End CAN Controller) module found on many
208	  TI devices. The device specifications are available from www.ti.com
209
210config CAN_XILINXCAN
211	tristate "Xilinx CAN"
212	depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST
213	depends on COMMON_CLK && HAS_IOMEM
214	help
215	  Xilinx CAN driver. This driver supports both soft AXI CAN IP and
216	  Zynq CANPS IP.
217
 
 
 
 
 
 
 
 
218source "drivers/net/can/c_can/Kconfig"
219source "drivers/net/can/cc770/Kconfig"
220source "drivers/net/can/ctucanfd/Kconfig"
221source "drivers/net/can/ifi_canfd/Kconfig"
222source "drivers/net/can/m_can/Kconfig"
223source "drivers/net/can/mscan/Kconfig"
224source "drivers/net/can/peak_canfd/Kconfig"
225source "drivers/net/can/rcar/Kconfig"
226source "drivers/net/can/sja1000/Kconfig"
227source "drivers/net/can/softing/Kconfig"
228source "drivers/net/can/spi/Kconfig"
229source "drivers/net/can/usb/Kconfig"
230
231endif #CAN_NETLINK
232
233config CAN_DEBUG_DEVICES
234	bool "CAN devices debugging messages"
235	help
236	  Say Y here if you want the CAN device drivers to produce a bunch of
237	  debug messages to the system log.  Select this if you are having
238	  a problem with CAN support and want to see more of what is going
239	  on.
240
241endif #CAN_DEV

  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 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
 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 && HAS_IOMEM
 
 
101	help
102	  Say Y here if you want to support for Freescale FlexCAN.
103
104config CAN_GRCAN
105	tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
106	depends on OF && HAS_DMA
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
113config 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
123config CAN_KVASER_PCIEFD
124	depends on PCI
125	tristate "Kvaser PCIe FD cards"
126	  help
127	  This is a driver for the Kvaser PCI Express CAN FD family.
128
129	  Supported devices:
130	    Kvaser PCIEcan 4xHS
131	    Kvaser PCIEcan 2xHS v2
132	    Kvaser PCIEcan HS v2
 
 
 
133	    Kvaser Mini PCI Express HS v2
134	    Kvaser Mini PCI Express 2xHS v2
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
135
136config CAN_SUN4I
137	tristate "Allwinner A10 CAN controller"
138	depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
139	help
140	  Say Y here if you want to use CAN controller found on Allwinner
141	  A10/A20 SoCs.
142
143	  To compile this driver as a module, choose M here: the module will
144	  be called sun4i_can.
145
146config CAN_TI_HECC
147	depends on ARM
148	tristate "TI High End CAN Controller"
 
149	help
150	  Driver for TI HECC (High End CAN Controller) module found on many
151	  TI devices. The device specifications are available from www.ti.com
152
153config CAN_XILINXCAN
154	tristate "Xilinx CAN"
155	depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST
156	depends on COMMON_CLK && HAS_IOMEM
157	help
158	  Xilinx CAN driver. This driver supports both soft AXI CAN IP and
159	  Zynq CANPS IP.
160
161config PCH_CAN
162	tristate "Intel EG20T PCH CAN controller"
163	depends on PCI && (X86_32 || COMPILE_TEST)
164	help
165	  This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
166	  is an IOH for x86 embedded processor (Intel Atom E6xx series).
167	  This driver can access CAN bus.
168
169source "drivers/net/can/c_can/Kconfig"
170source "drivers/net/can/cc770/Kconfig"
 
171source "drivers/net/can/ifi_canfd/Kconfig"
172source "drivers/net/can/m_can/Kconfig"
173source "drivers/net/can/mscan/Kconfig"
174source "drivers/net/can/peak_canfd/Kconfig"
175source "drivers/net/can/rcar/Kconfig"
176source "drivers/net/can/sja1000/Kconfig"
177source "drivers/net/can/softing/Kconfig"
178source "drivers/net/can/spi/Kconfig"
179source "drivers/net/can/usb/Kconfig"
180
181endif
182
183config CAN_DEBUG_DEVICES
184	bool "CAN devices debugging messages"
185	help
186	  Say Y here if you want the CAN device drivers to produce a bunch of
187	  debug messages to the system log.  Select this if you are having
188	  a problem with CAN support and want to see more of what is going
189	  on.
190
191endmenu