Lines Matching +full:zynq +full:- +full:can +full:- +full:1
1 # SPDX-License-Identifier: GPL-2.0-only
4 tristate "CAN Device Drivers"
6 depends on CAN
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
13 applications. More information on the CAN network protocol family
14 PF_CAN is contained in <Documentation/networking/can.rst>.
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
21 can-dev.
26 tristate "Virtual Local CAN Interface (vcan)"
29 virtual local CAN interface.
31 This driver can also be built as a module. If so, the module
35 tristate "Virtual CAN Tunnel (vxcan)"
38 local CAN traffic tunnel between two virtual CAN network devices.
41 versa. The vxcan can be used for cross namespace communication.
43 In opposite to vcan loopback devices the vxcan only forwards CAN
45 CAN frames. To disable a potential echo in af_can.c the vxcan driver
47 in each namespace the CAN GW hop counter is set to zero.
49 This driver can also be built as a module. If so, the module
53 bool "CAN device drivers with Netlink support"
56 Enables the common framework for CAN device drivers. This is the
58 as bittiming validation, support of CAN error states, device restart
62 can-dev module.
64 This is required by all platform and hardware CAN drivers. If you
70 bool "CAN bit-timing calculation"
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
78 bit-timing parameters must be specified directly using the Netlink
82 can-dev module.
90 tristate "Atmel AT91 onchip CAN controller"
94 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
98 tristate "STM32 Basic Extended CAN (bxCAN) devices"
104 extended CAN Controller (bxCAN).
106 This driver can also be built as a module. If so, the module
110 tristate "Serial / USB serial ELM327 based OBD-II Interfaces (can327)"
114 CAN driver for several 'low cost' OBD-II interfaces based on the
115 ELM327 OBD-II interpreter chip.
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),
123 Documentation/networking/device_drivers/can/can327.rst
128 tristate "Dummy CAN"
130 A dummy CAN module supporting Classical CAN, CAN FD and CAN XL. It
131 exposes bittiming values which can be configured through the netlink
135 are activated, it prints all the CAN bittiming information in the
138 This is convenient for testing the CAN netlink interface. Most of the
142 called dummy-can.
153 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
162 tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
165 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
168 This driver can also be built as a module. If so, the module will be
169 called janz-ican3.ko.
176 This is a driver for the Kvaser PCI Express CAN FD family.
182 Kvaser PCIEcan 1xCAN v3
187 Kvaser Mini PCI Express 1xCAN v3
193 tristate "Serial / USB serial CAN Adaptors (slcan)"
196 CAN driver for several 'low cost' CAN interfaces that are attached
197 via serial lines or via USB-to-serial adapters using the LAWICEL
200 As only the sending and receiving of CAN frames is implemented, this
201 driver should work with the (serial/USB) CAN hardware from:
205 slcand) can be found in the can-utils at the linux-can project, see
206 https://github.com/linux-can/can-utils for details.
208 This driver can also be built as a module. If so, the module
212 tristate "Allwinner A10 CAN controller"
215 Say Y here if you want to use CAN controller found on Allwinner
223 tristate "TI High End CAN Controller"
226 Driver for TI HECC (High End CAN Controller) module found on many
230 tristate "Xilinx CAN"
234 Xilinx CAN driver. This driver supports both soft AXI CAN IP and
235 Zynq CANPS IP.
237 source "drivers/net/can/c_can/Kconfig"
238 source "drivers/net/can/cc770/Kconfig"
239 source "drivers/net/can/ctucanfd/Kconfig"
240 source "drivers/net/can/esd/Kconfig"
241 source "drivers/net/can/ifi_canfd/Kconfig"
242 source "drivers/net/can/m_can/Kconfig"
243 source "drivers/net/can/mscan/Kconfig"
244 source "drivers/net/can/peak_canfd/Kconfig"
245 source "drivers/net/can/rcar/Kconfig"
246 source "drivers/net/can/rockchip/Kconfig"
247 source "drivers/net/can/sja1000/Kconfig"
248 source "drivers/net/can/softing/Kconfig"
249 source "drivers/net/can/spi/Kconfig"
250 source "drivers/net/can/usb/Kconfig"
255 bool "CAN devices debugging messages"
257 Say Y here if you want the CAN device drivers to produce a bunch of
259 a problem with CAN support and want to see more of what is going