forked from ~ljy/RK356X_SDK_RELEASE
blame | history | patch | commit | commitdiff
hc
2024-05-11 297b60346df8beafee954a0fd7c2d64f33f3b9bc 
 kernel/drivers/net/can/Kconfig
....@@ -1,8 +1,9 @@
1
+# SPDX-License-Identifier: GPL-2.0-only
12 menu "CAN Device Drivers"
23 
34 config CAN_VCAN
45 	tristate "Virtual Local CAN Interface (vcan)"
5
-	---help---
6
+	help
67 	  Similar to the network loopback devices, vcan offers a
78 	  virtual local CAN interface.
89 
....@@ -11,7 +12,7 @@
1112 
1213 config CAN_VXCAN
1314 	tristate "Virtual CAN Tunnel (vxcan)"
14
-	---help---
15
+	help
1516 	  Similar to the virtual ethernet driver veth, vxcan implements a
1617 	  local CAN traffic tunnel between two virtual CAN network devices.
1718 	  When creating a vxcan, two vxcan devices are created as pair.
....@@ -30,7 +31,7 @@
3031 config CAN_SLCAN
3132 	tristate "Serial / USB serial CAN Adaptors (slcan)"
3233 	depends on TTY
33
-	---help---
34
+	help
3435 	  CAN driver for several 'low cost' CAN interfaces that are attached
3536 	  via serial lines or via USB-to-serial adapters using the LAWICEL
3637 	  ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
....@@ -40,8 +41,8 @@
4041 	  www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
4142 
4243 	  Userspace tools to attach the SLCAN line discipline (slcan_attach,
43
-	  slcand) can be found in the can-utils at the SocketCAN SVN, see
44
-	  http://developer.berlios.de/projects/socketcan for details.
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.
4546 
4647 	  The slcan driver supports up to 10 CAN netdevices by default which
4748 	  can be changed by the 'maxdev=xx' module option. This driver can
....@@ -50,7 +51,7 @@
5051 config CAN_DEV
5152 	tristate "Platform CAN drivers with Netlink support"
5253 	default y
53
-	---help---
54
+	help
5455 	  Enables the common framework for platform CAN drivers with Netlink
5556 	  support. This is the standard library for CAN drivers.
5657 	  If unsure, say Y.
....@@ -60,7 +61,7 @@
6061 config CAN_CALC_BITTIMING
6162 	bool "CAN bit-timing calculation"
6263 	default y
63
-	---help---
64
+	help
6465 	  If enabled, CAN bit-timing parameters will be calculated for the
6566 	  bit-rate specified via Netlink argument "bitrate" when the device
6667 	  get started. This works fine for the most common CAN controllers
....@@ -80,7 +81,7 @@
8081 	# fulfills your needs instead of fixing this driver.
8182 	depends on BROKEN
8283 	select LEDS_TRIGGERS
83
-	---help---
84
+	help
8485 	  This option adds two LED triggers for packet receive and transmit
8586 	  events on each supported CAN device.
8687 
....@@ -90,20 +91,20 @@
9091 config CAN_AT91
9192 	tristate "Atmel AT91 onchip CAN controller"
9293 	depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM
93
-	---help---
94
+	help
9495 	  This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
9596 	  and AT91SAM9X5 processors.
9697 
9798 config CAN_FLEXCAN
9899 	tristate "Support for Freescale FLEXCAN based chips"
99
-	depends on ARM || PPC
100
-	---help---
100
+	depends on OF && HAS_IOMEM
101
+	help
101102 	  Say Y here if you want to support for Freescale FlexCAN.
102103 
103104 config CAN_GRCAN
104105 	tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
105106 	depends on OF && HAS_DMA
106
-	---help---
107
+	help
107108 	  Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
108109 	  Note that the driver supports little endian, even though little
109110 	  endian syntheses of the cores would need some modifications on
....@@ -112,17 +113,31 @@
112113 config CAN_JANZ_ICAN3
113114 	tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
114115 	depends on MFD_JANZ_CMODIO
115
-	---help---
116
+	help
116117 	  Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
117118 	  connects to a MODULbus carrier board.
118119 
119120 	  This driver can also be built as a module. If so, the module will be
120121 	  called janz-ican3.ko.
121122 
123
+config CAN_KVASER_PCIEFD
124
+	depends on PCI
125
+	tristate "Kvaser PCIe FD cards"
126
+	select CRC32
127
+	  help
128
+	  This is a driver for the Kvaser PCI Express CAN FD family.
129
+
130
+	  Supported devices:
131
+	    Kvaser PCIEcan 4xHS
132
+	    Kvaser PCIEcan 2xHS v2
133
+	    Kvaser PCIEcan HS v2
134
+	    Kvaser Mini PCI Express HS v2
135
+	    Kvaser Mini PCI Express 2xHS v2
136
+
122137 config CAN_SUN4I
123138 	tristate "Allwinner A10 CAN controller"
124139 	depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
125
-	---help---
140
+	help
126141 	  Say Y here if you want to use CAN controller found on Allwinner
127142 	  A10/A20 SoCs.
128143 
....@@ -132,7 +147,7 @@
132147 config CAN_TI_HECC
133148 	depends on ARM
134149 	tristate "TI High End CAN Controller"
135
-	---help---
150
+	help
136151 	  Driver for TI HECC (High End CAN Controller) module found on many
137152 	  TI devices. The device specifications are available from www.ti.com
138153 
....@@ -140,14 +155,14 @@
140155 	tristate "Xilinx CAN"
141156 	depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST
142157 	depends on COMMON_CLK && HAS_IOMEM
143
-	---help---
158
+	help
144159 	  Xilinx CAN driver. This driver supports both soft AXI CAN IP and
145160 	  Zynq CANPS IP.
146161 
147162 config PCH_CAN
148163 	tristate "Intel EG20T PCH CAN controller"
149164 	depends on PCI && (X86_32 || COMPILE_TEST)
150
-	---help---
165
+	help
151166 	  This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
152167 	  is an IOH for x86 embedded processor (Intel Atom E6xx series).
153168 	  This driver can access CAN bus.
....@@ -169,7 +184,7 @@
169184 
170185 config CAN_DEBUG_DEVICES
171186 	bool "CAN devices debugging messages"
172
-	---help---
187
+	help
173188 	  Say Y here if you want the CAN device drivers to produce a bunch of
174189 	  debug messages to the system log.  Select this if you are having
175190 	  a problem with CAN support and want to see more of what is going