# SPDX-License-Identifier: GPL-2.0-only
menu "CAN Device Drivers"
config [31mCONFIG_CAN_VCAN[0m
tristate "Virtual Local CAN Interface (vcan)"
---help---
Similar to the network loopback devices, vcan offers a
virtual local [31mCONFIG_CAN[0m interface.
This driver can also be built as a module. If so, the module
will be called vcan.
config [31mCONFIG_CAN_VXCAN[0m
tristate "Virtual CAN Tunnel (vxcan)"
---help---
Similar to the virtual ethernet driver veth, vxcan implements a
local [31mCONFIG_CAN[0m traffic tunnel between two virtual [31mCONFIG_CAN[0m network devices.
When creating a vxcan, two vxcan devices are created as pair.
When one end receives the packet it appears on its pair and vice
versa. The vxcan can be used for cross namespace communication.
In opposite to vcan loopback devices the vxcan only forwards [31mCONFIG_CAN[0m
frames to its pair and does *not* provide a local echo of sent
[31mCONFIG_CAN[0m frames. To disable a potential echo in af_can.c the vxcan driver
announces IFF_ECHO in the interface flags. To have a clean start
in each namespace the [31mCONFIG_CAN[0m GW hop counter is set to zero.
This driver can also be built as a module. If so, the module
will be called vxcan.
config [31mCONFIG_CAN_SLCAN[0m
tristate "Serial / USB serial CAN Adaptors (slcan)"
depends on [31mCONFIG_TTY[0m
---help---
[31mCONFIG_CAN[0m driver for several 'low cost' [31mCONFIG_CAN[0m interfaces that are attached
via serial lines or via [31mCONFIG_USB[0m-to-serial adapters using the LAWICEL
ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
As only the sending and receiving of [31mCONFIG_CAN[0m frames is implemented, this
driver should work with the (serial/[31mCONFIG_USB[0m) [31mCONFIG_CAN[0m hardware from:
www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
Userspace tools to attach the SLCAN line discipline (slcan_attach,
slcand) can be found in the can-utils at the SocketCAN SVN, see
http://developer.berlios.de/projects/socketcan for details.
The slcan driver supports up to 10 [31mCONFIG_CAN[0m netdevices by default which
can be changed by the 'maxdev=xx' module option. This driver can
also be built as a module. If so, the module will be called slcan.
config [31mCONFIG_CAN_DEV[0m
tristate "Platform CAN drivers with Netlink support"
default y
---help---
Enables the common framework for platform [31mCONFIG_CAN[0m drivers with Netlink
support. This is the standard library for [31mCONFIG_CAN[0m drivers.
If unsure, say Y.
if [31mCONFIG_CAN_DEV[0m
config [31mCONFIG_CAN_CALC_BITTIMING[0m
bool "CAN bit-timing calculation"
default y
---help---
If enabled, [31mCONFIG_CAN[0m bit-timing parameters will be calculated for the
bit-rate specified via Netlink argument "bitrate" when the device
get started. This works fine for the most common [31mCONFIG_CAN[0m controllers
with standard bit-rates but may fail for exotic bit-rates or [31mCONFIG_CAN[0m
source clock frequencies. Disabling saves some space, but then the
bit-timing parameters must be specified directly using the Netlink
arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
If unsure, say Y.
config [31mCONFIG_CAN_LEDS[0m
bool "Enable LED triggers for Netlink based drivers"
depends on [31mCONFIG_LEDS_CLASS[0m
# The netdev trigger ([31mCONFIG_LEDS_TRIGGER_NETDEV[0m) should be able to do
# everything that this driver is doing. This is marked as broken
# because it uses stuff that is intended to be changed or removed.
# Please consider switching to the netdev trigger and confirm it
# fulfills your needs instead of fixing this driver.
depends on [31mCONFIG_BROKEN[0m
select [31mCONFIG_LEDS_TRIGGERS[0m
---help---
This option adds two LED triggers for packet receive and transmit
events on each supported [31mCONFIG_CAN[0m device.
Say Y here if you are working on a system with led-class supported
LEDs and you want to use them as canbus activity indicators.
config [31mCONFIG_CAN_AT91[0m
tristate "Atmel AT91 onchip CAN controller"
depends on ([31mCONFIG_ARCH_AT91[0m || [31mCONFIG_COMPILE_TEST[0m) && [31mCONFIG_HAS_IOMEM[0m
---help---
This is a driver for the SoC [31mCONFIG_CAN[0m controller in Atmel's AT91SAM9263
and AT91SAM9X5 processors.
config [31mCONFIG_CAN_FLEXCAN[0m
tristate "Support for Freescale FLEXCAN based chips"
depends on [31mCONFIG_OF[0m && [31mCONFIG_HAS_IOMEM[0m
---help---
Say Y here if you want to support for Freescale FlexCAN.
config [31mCONFIG_CAN_GRCAN[0m
tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
depends on [31mCONFIG_OF[0m && [31mCONFIG_HAS_DMA[0m
---help---
Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
Note that the driver supports little endian, even though little
endian syntheses of the cores would need some modifications on
the hardware level to work.
config [31mCONFIG_CAN_JANZ_ICAN3[0m
tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
depends on [31mCONFIG_MFD_JANZ_CMODIO[0m
---help---
Driver for Janz VMOD-ICAN3 Intelligent [31mCONFIG_CAN[0m controller module, which
connects to a MODULbus carrier board.
This driver can also be built as a module. If so, the module will be
called janz-ican3.ko.
config [31mCONFIG_CAN_KVASER_PCIEFD[0m
depends on [31mCONFIG_PCI[0m
tristate "Kvaser PCIe FD cards"
help
This is a driver for the Kvaser [31mCONFIG_PCI[0m Express [31mCONFIG_CAN[0m FD family.
Supported devices:
Kvaser PCIEcan 4xHS
Kvaser PCIEcan 2xHS v2
Kvaser PCIEcan HS v2
Kvaser Mini [31mCONFIG_PCI[0m Express HS v2
Kvaser Mini [31mCONFIG_PCI[0m Express 2xHS v2
config [31mCONFIG_CAN_SUN4I[0m
tristate "Allwinner A10 CAN controller"
depends on [31mCONFIG_MACH_SUN4I[0m || [31mCONFIG_MACH_SUN7I[0m || [31mCONFIG_COMPILE_TEST[0m
---help---
Say Y here if you want to use [31mCONFIG_CAN[0m controller found on Allwinner
A10/A20 SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called sun4i_can.
config [31mCONFIG_CAN_TI_HECC[0m
depends on [31mCONFIG_ARM[0m
tristate "TI High End CAN Controller"
---help---
Driver for TI HECC (High End [31mCONFIG_CAN[0m Controller) module found on many
TI devices. The device specifications are available from www.ti.com
config [31mCONFIG_CAN_XILINXCAN[0m
tristate "Xilinx CAN"
depends on [31mCONFIG_ARCH_ZYNQ[0m || [31mCONFIG_ARM64[0m || [31mCONFIG_MICROBLAZE[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_COMMON_CLK[0m && [31mCONFIG_HAS_IOMEM[0m
---help---
Xilinx [31mCONFIG_CAN[0m driver. This driver supports both soft AXI [31mCONFIG_CAN[0m IP and
Zynq CANPS IP.
config [31mCONFIG_PCH_CAN[0m
tristate "Intel EG20T PCH CAN controller"
depends on [31mCONFIG_PCI[0m && ([31mCONFIG_X86_32[0m || [31mCONFIG_COMPILE_TEST[0m)
---help---
This driver is for PCH [31mCONFIG_CAN[0m of Topcliff (Intel EG20T PCH) which
is an IOH for x86 embedded processor (Intel Atom E6xx series).
This driver can access [31mCONFIG_CAN[0m bus.
source "drivers/net/can/c_can/Kconfig"
source "drivers/net/can/cc770/Kconfig"
source "drivers/net/can/ifi_canfd/Kconfig"
source "drivers/net/can/m_can/Kconfig"
source "drivers/net/can/mscan/Kconfig"
source "drivers/net/can/peak_canfd/Kconfig"
source "drivers/net/can/rcar/Kconfig"
source "drivers/net/can/sja1000/Kconfig"
source "drivers/net/can/softing/Kconfig"
source "drivers/net/can/spi/Kconfig"
source "drivers/net/can/usb/Kconfig"
endif
config [31mCONFIG_CAN_DEBUG_DEVICES[0m
bool "CAN devices debugging messages"
---help---
Say Y here if you want the [31mCONFIG_CAN[0m device drivers to produce a bunch of
debug messages to the system log. Select this if you are having
a problem with [31mCONFIG_CAN[0m support and want to see more of what is going
on.
endmenu