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        default N
   8        ---help---
   9          Similar to the network loopback devices, vcan offers a
  10          virtual local CAN interface.
  11
  12          This driver can also be built as a module.  If so, the module
  13          will be called vcan.
  14
  15config CAN_DEV
  16        tristate "Platform CAN drivers with Netlink support"
  17        depends on CAN
  18        default Y
  19        ---help---
  20          Enables the common framework for platform CAN drivers with Netlink
  21          support. This is the standard library for CAN drivers.
  22          If unsure, say Y.
  23
  24config CAN_CALC_BITTIMING
  25        bool "CAN bit-timing calculation"
  26        depends on CAN_DEV
  27        default Y
  28        ---help---
  29          If enabled, CAN bit-timing parameters will be calculated for the
  30          bit-rate specified via Netlink argument "bitrate" when the device
  31          get started. This works fine for the most common CAN controllers
  32          with standard bit-rates but may fail for exotic bit-rates or CAN
  33          source clock frequencies. Disabling saves some space, but then the
  34          bit-timing parameters must be specified directly using the Netlink
  35          arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
  36          If unsure, say Y.
  37
  38config CAN_AT91
  39        tristate "Atmel AT91 onchip CAN controller"
  40        depends on CAN_DEV && ARCH_AT91SAM9263
  41        ---help---
  42          This is a driver for the SoC CAN controller in Atmel's AT91SAM9263.
  43
  44config CAN_TI_HECC
  45        depends on CAN_DEV && ARCH_OMAP3
  46        tristate "TI High End CAN Controller"
  47        ---help---
  48          Driver for TI HECC (High End CAN Controller) module found on many
  49          TI devices. The device specifications are available from www.ti.com
  50
  51config CAN_MCP251X
  52        tristate "Microchip MCP251x SPI CAN controllers"
  53        depends on CAN_DEV && SPI && HAS_DMA
  54        ---help---
  55          Driver for the Microchip MCP251x SPI CAN controllers.
  56
  57config CAN_BFIN
  58        depends on CAN_DEV && (BF534 || BF536 || BF537 || BF538 || BF539 || BF54x)
  59        tristate "Analog Devices Blackfin on-chip CAN"
  60        ---help---
  61          Driver for the Analog Devices Blackfin on-chip CAN controllers
  62
  63          To compile this driver as a module, choose M here: the
  64          module will be called bfin_can.
  65
  66config CAN_JANZ_ICAN3
  67        tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
  68        depends on CAN_DEV && MFD_JANZ_CMODIO
  69        ---help---
  70          Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
  71          connects to a MODULbus carrier board.
  72
  73          This driver can also be built as a module. If so, the module will be
  74          called janz-ican3.ko.
  75
  76source "drivers/net/can/mscan/Kconfig"
  77
  78source "drivers/net/can/sja1000/Kconfig"
  79
  80source "drivers/net/can/usb/Kconfig"
  81
  82config CAN_DEBUG_DEVICES
  83        bool "CAN devices debugging messages"
  84        depends on CAN
  85        default N
  86        ---help---
  87          Say Y here if you want the CAN device drivers to produce a bunch of
  88          debug messages to the system log.  Select this if you are having
  89          a problem with CAN support and want to see more of what is going
  90          on.
  91
  92endmenu
  93