Kconfig 8.0 KB

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