Kconfig 3.0 KB

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