LXR linux/drivers/net/can/Kconfig

   1menu "CAN Device Drivers"
   2        depends on CAN
   3
   4config CAN_VCAN
   5        tristate "Virtual Local CAN Interface (vcan)"
   6        depends on CAN
   7        ---help---
   8          Similar to the network loopback devices, vcan offers a
   9          virtual local CAN interface.
  10
  11          This driver can also be built as a module.  If so, the module
  12          will be called vcan.
  13
  14config CAN_SLCAN
  15        tristate "Serial / USB serial CAN Adaptors (slcan)"
  16        depends on CAN
  17        ---help---
  18          CAN driver for several 'low cost' CAN interfaces that are attached
  19          via serial lines or via USB-to-serial adapters using the LAWICEL
  20          ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
  21
  22          As only the sending and receiving of CAN frames is implemented, this
  23          driver should work with the (serial/USB) CAN hardware from:
  24          www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
  25
  26          Userspace tools to attach the SLCAN line discipline (slcan_attach,
  27          slcand) can be found in the can-utils at the SocketCAN SVN, see
  28          http://developer.berlios.de/projects/socketcan for details.
  29
  30          The slcan driver supports up to 10 CAN netdevices by default which
  31          can be changed by the 'maxdev=xx' module option. This driver can
  32          also be built as a module. If so, the module will be called slcan.
  33
  34config CAN_DEV
  35        tristate "Platform CAN drivers with Netlink support"
  36        depends on CAN
  37        default y
  38        ---help---
  39          Enables the common framework for platform CAN drivers with Netlink
  40          support. This is the standard library for CAN drivers.
  41          If unsure, say Y.
  42
  43config CAN_CALC_BITTIMING
  44        bool "CAN bit-timing calculation"
  45        depends on CAN_DEV
  46        default y
  47        ---help---
  48          If enabled, CAN bit-timing parameters will be calculated for the
  49          bit-rate specified via Netlink argument "bitrate" when the device
  50          get started. This works fine for the most common CAN controllers
  51          with standard bit-rates but may fail for exotic bit-rates or CAN
  52          source clock frequencies. Disabling saves some space, but then the
  53          bit-timing parameters must be specified directly using the Netlink
  54          arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
  55          If unsure, say Y.
  56
  57config CAN_AT91
  58        tristate "Atmel AT91 onchip CAN controller"
  59        depends on CAN_DEV && (ARCH_AT91SAM9263 || ARCH_AT91SAM9X5)
  60        ---help---
  61          This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
  62          and AT91SAM9X5 processors.
  63
  64config CAN_TI_HECC
  65        depends on CAN_DEV && ARCH_OMAP3
  66        tristate "TI High End CAN Controller"
  67        ---help---
  68          Driver for TI HECC (High End CAN Controller) module found on many
  69          TI devices. The device specifications are available from www.ti.com
  70
  71config CAN_MCP251X
  72        tristate "Microchip MCP251x SPI CAN controllers"
  73        depends on CAN_DEV && SPI && HAS_DMA
  74        ---help---
  75          Driver for the Microchip MCP251x SPI CAN controllers.
  76
  77config CAN_BFIN
  78        depends on CAN_DEV && (BF534 || BF536 || BF537 || BF538 || BF539 || BF54x)
  79        tristate "Analog Devices Blackfin on-chip CAN"
  80        ---help---
  81          Driver for the Analog Devices Blackfin on-chip CAN controllers
  82
  83          To compile this driver as a module, choose M here: the
  84          module will be called bfin_can.
  85
  86config CAN_JANZ_ICAN3
  87        tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
  88        depends on CAN_DEV && MFD_JANZ_CMODIO
  89        ---help---
  90          Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
  91          connects to a MODULbus carrier board.
  92
  93          This driver can also be built as a module. If so, the module will be
  94          called janz-ican3.ko.
  95
  96config HAVE_CAN_FLEXCAN
  97        bool
  98
  99config CAN_FLEXCAN
 100        tristate "Support for Freescale FLEXCAN based chips"
 101        depends on CAN_DEV && HAVE_CAN_FLEXCAN
 102        ---help---
 103          Say Y here if you want to support for Freescale FlexCAN.
 104
 105config PCH_CAN
 106        tristate "PCH CAN"
 107        depends on CAN_DEV && PCI
 108        ---help---
 109          This driver is for PCH CAN of Topcliff which is an IOH for x86
 110          embedded processor.
 111          This driver can access CAN bus.
 112
 113source "drivers/net/can/mscan/Kconfig"
 114
 115source "drivers/net/can/sja1000/Kconfig"
 116
 117source "drivers/net/can/c_can/Kconfig"
 118
 119source "drivers/net/can/usb/Kconfig"
 120
 121source "drivers/net/can/softing/Kconfig"
 122
 123config CAN_DEBUG_DEVICES
 124        bool "CAN devices debugging messages"
 125        depends on CAN
 126        ---help---
 127          Say Y here if you want the CAN device drivers to produce a bunch of
 128          debug messages to the system log.  Select this if you are having
 129          a problem with CAN support and want to see more of what is going
 130          on.
 131
 132endmenu
 133