2007-11-17 07:56:08 +08:00
|
|
|
menu "CAN Device Drivers"
|
|
|
|
|
depends on CAN
|
|
|
|
|
|
|
|
|
|
config CAN_VCAN
|
|
|
|
|
tristate "Virtual Local CAN Interface (vcan)"
|
|
|
|
|
depends on CAN
|
|
|
|
|
default N
|
|
|
|
|
---help---
|
|
|
|
|
Similar to the network loopback devices, vcan offers a
|
|
|
|
|
virtual local CAN interface.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called vcan.
|
|
|
|
|
|
2009-05-16 07:39:29 +08:00
|
|
|
config CAN_DEV
|
|
|
|
|
tristate "Platform CAN drivers with Netlink support"
|
|
|
|
|
depends on CAN
|
|
|
|
|
default Y
|
|
|
|
|
---help---
|
|
|
|
|
Enables the common framework for platform CAN drivers with Netlink
|
|
|
|
|
support. This is the standard library for CAN drivers.
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config CAN_CALC_BITTIMING
|
|
|
|
|
bool "CAN bit-timing calculation"
|
|
|
|
|
depends on CAN_DEV
|
|
|
|
|
default Y
|
|
|
|
|
---help---
|
|
|
|
|
If enabled, CAN 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 CAN controllers
|
|
|
|
|
with standard bit-rates but may fail for exotic bit-rates or CAN
|
|
|
|
|
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.
|
|
|
|
|
|
2009-09-23 05:46:57 +08:00
|
|
|
config CAN_AT91
|
|
|
|
|
tristate "Atmel AT91 onchip CAN controller"
|
2009-11-12 09:35:01 +08:00
|
|
|
depends on CAN_DEV && ARCH_AT91SAM9263
|
2009-09-23 05:46:57 +08:00
|
|
|
---help---
|
|
|
|
|
This is a driver for the SoC CAN controller in Atmel's AT91SAM9263.
|
|
|
|
|
|
2009-10-07 10:59:47 +08:00
|
|
|
config CAN_TI_HECC
|
|
|
|
|
depends on CAN_DEV && ARCH_OMAP3
|
|
|
|
|
tristate "TI High End CAN Controller"
|
|
|
|
|
---help---
|
|
|
|
|
Driver for TI HECC (High End CAN Controller) module found on many
|
|
|
|
|
TI devices. The device specifications are available from www.ti.com
|
|
|
|
|
|
2009-11-03 07:07:00 +08:00
|
|
|
config CAN_MCP251X
|
|
|
|
|
tristate "Microchip MCP251x SPI CAN controllers"
|
2009-12-13 17:11:06 +08:00
|
|
|
depends on CAN_DEV && SPI && HAS_DMA
|
2009-11-03 07:07:00 +08:00
|
|
|
---help---
|
|
|
|
|
Driver for the Microchip MCP251x SPI CAN controllers.
|
|
|
|
|
|
2009-12-11 07:46:28 +08:00
|
|
|
config CAN_BFIN
|
|
|
|
|
depends on CAN_DEV && (BF534 || BF536 || BF537 || BF538 || BF539 || BF54x)
|
|
|
|
|
tristate "Analog Devices Blackfin on-chip CAN"
|
|
|
|
|
---help---
|
|
|
|
|
Driver for the Analog Devices Blackfin on-chip CAN controllers
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called bfin_can.
|
|
|
|
|
|
2010-03-30 00:58:51 +08:00
|
|
|
config CAN_JANZ_ICAN3
|
|
|
|
|
tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
|
|
|
|
|
depends on CAN_DEV && MFD_JANZ_CMODIO
|
|
|
|
|
---help---
|
|
|
|
|
Driver for Janz VMOD-ICAN3 Intelligent CAN 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.
|
|
|
|
|
|
2009-11-17 19:57:12 +08:00
|
|
|
source "drivers/net/can/mscan/Kconfig"
|
2009-11-13 14:14:52 +08:00
|
|
|
|
2009-11-12 09:35:01 +08:00
|
|
|
source "drivers/net/can/sja1000/Kconfig"
|
|
|
|
|
|
|
|
|
|
source "drivers/net/can/usb/Kconfig"
|
|
|
|
|
|
2007-11-17 07:56:08 +08:00
|
|
|
config CAN_DEBUG_DEVICES
|
|
|
|
|
bool "CAN devices debugging messages"
|
|
|
|
|
depends on CAN
|
|
|
|
|
default N
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want the CAN device drivers to produce a bunch of
|
|
|
|
|
debug messages to the system log. Select this if you are having
|
|
|
|
|
a problem with CAN support and want to see more of what is going
|
|
|
|
|
on.
|
|
|
|
|
|
|
|
|
|
endmenu
|
