1ccb29637SOliver Hartkoppmenu "CAN Device Drivers" 2ccb29637SOliver Hartkopp depends on CAN 3ccb29637SOliver Hartkopp 4ccb29637SOliver Hartkoppconfig CAN_VCAN 5ccb29637SOliver Hartkopp tristate "Virtual Local CAN Interface (vcan)" 6ccb29637SOliver Hartkopp depends on CAN 7ccb29637SOliver Hartkopp default N 8ccb29637SOliver Hartkopp ---help--- 9ccb29637SOliver Hartkopp Similar to the network loopback devices, vcan offers a 10ccb29637SOliver Hartkopp virtual local CAN interface. 11ccb29637SOliver Hartkopp 12ccb29637SOliver Hartkopp This driver can also be built as a module. If so, the module 13ccb29637SOliver Hartkopp will be called vcan. 14ccb29637SOliver Hartkopp 1539549eefSWolfgang Grandeggerconfig CAN_DEV 1639549eefSWolfgang Grandegger tristate "Platform CAN drivers with Netlink support" 1739549eefSWolfgang Grandegger depends on CAN 1839549eefSWolfgang Grandegger default Y 1939549eefSWolfgang Grandegger ---help--- 2039549eefSWolfgang Grandegger Enables the common framework for platform CAN drivers with Netlink 2139549eefSWolfgang Grandegger support. This is the standard library for CAN drivers. 2239549eefSWolfgang Grandegger If unsure, say Y. 2339549eefSWolfgang Grandegger 2439549eefSWolfgang Grandeggerconfig CAN_CALC_BITTIMING 2539549eefSWolfgang Grandegger bool "CAN bit-timing calculation" 2639549eefSWolfgang Grandegger depends on CAN_DEV 2739549eefSWolfgang Grandegger default Y 2839549eefSWolfgang Grandegger ---help--- 2939549eefSWolfgang Grandegger If enabled, CAN bit-timing parameters will be calculated for the 3039549eefSWolfgang Grandegger bit-rate specified via Netlink argument "bitrate" when the device 3139549eefSWolfgang Grandegger get started. This works fine for the most common CAN controllers 3239549eefSWolfgang Grandegger with standard bit-rates but may fail for exotic bit-rates or CAN 3339549eefSWolfgang Grandegger source clock frequencies. Disabling saves some space, but then the 3439549eefSWolfgang Grandegger bit-timing parameters must be specified directly using the Netlink 3539549eefSWolfgang Grandegger arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw". 3639549eefSWolfgang Grandegger If unsure, say Y. 3739549eefSWolfgang Grandegger 38429da1ccSWolfgang Grandeggerconfig CAN_SJA1000 39fec37ab5SHeiko Carstens depends on CAN_DEV && HAS_IOMEM 40429da1ccSWolfgang Grandegger tristate "Philips SJA1000" 41429da1ccSWolfgang Grandegger ---help--- 42429da1ccSWolfgang Grandegger Driver for the SJA1000 CAN controllers from Philips or NXP 43429da1ccSWolfgang Grandegger 442a6ba39aSWolfgang Grandeggerconfig CAN_SJA1000_ISA 452a6ba39aSWolfgang Grandegger depends on CAN_SJA1000 && ISA 462a6ba39aSWolfgang Grandegger tristate "ISA Bus based legacy SJA1000 driver" 472a6ba39aSWolfgang Grandegger ---help--- 482a6ba39aSWolfgang Grandegger This driver adds legacy support for SJA1000 chips connected to 492a6ba39aSWolfgang Grandegger the ISA bus using I/O port, memory mapped or indirect access. 502a6ba39aSWolfgang Grandegger 51f534e52fSWolfgang Grandeggerconfig CAN_SJA1000_PLATFORM 52f534e52fSWolfgang Grandegger depends on CAN_SJA1000 53f534e52fSWolfgang Grandegger tristate "Generic Platform Bus based SJA1000 driver" 54f534e52fSWolfgang Grandegger ---help--- 55f534e52fSWolfgang Grandegger This driver adds support for the SJA1000 chips connected to 56f534e52fSWolfgang Grandegger the "platform bus" (Linux abstraction for directly to the 57f534e52fSWolfgang Grandegger processor attached devices). Which can be found on various 58f534e52fSWolfgang Grandegger boards from Phytec (http://www.phytec.de) like the PCM027, 59f534e52fSWolfgang Grandegger PCM038. 60f534e52fSWolfgang Grandegger 61d1a277c5SWolfgang Grandeggerconfig CAN_SJA1000_OF_PLATFORM 62d1a277c5SWolfgang Grandegger depends on CAN_SJA1000 && PPC_OF 63d1a277c5SWolfgang Grandegger tristate "Generic OF Platform Bus based SJA1000 driver" 64d1a277c5SWolfgang Grandegger ---help--- 65d1a277c5SWolfgang Grandegger This driver adds support for the SJA1000 chips connected to 66d1a277c5SWolfgang Grandegger the OpenFirmware "platform bus" found on embedded systems with 67d1a277c5SWolfgang Grandegger OpenFirmware bindings, e.g. if you have a PowerPC based system 68d1a277c5SWolfgang Grandegger you may want to enable this option. 69d1a277c5SWolfgang Grandegger 70a61a8423SWolfgang Grandeggerconfig CAN_EMS_PCI 71dd52856bSSebastian Haas tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card" 72a61a8423SWolfgang Grandegger depends on PCI && CAN_SJA1000 73a61a8423SWolfgang Grandegger ---help--- 74dd52856bSSebastian Haas This driver is for the one, two or four channel CPC-PCI, 75dd52856bSSebastian Haas CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche 76dd52856bSSebastian Haas (http://www.ems-wuensche.de). 77a61a8423SWolfgang Grandegger 783878fb6fSWolfgang Grandeggerconfig CAN_KVASER_PCI 793878fb6fSWolfgang Grandegger tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards" 803878fb6fSWolfgang Grandegger depends on PCI && CAN_SJA1000 813878fb6fSWolfgang Grandegger ---help--- 823878fb6fSWolfgang Grandegger This driver is for the the PCIcanx and PCIcan cards (1, 2 or 833878fb6fSWolfgang Grandegger 4 channel) from Kvaser (http://www.kvaser.com). 843878fb6fSWolfgang Grandegger 85ccb29637SOliver Hartkoppconfig CAN_DEBUG_DEVICES 86ccb29637SOliver Hartkopp bool "CAN devices debugging messages" 87ccb29637SOliver Hartkopp depends on CAN 88ccb29637SOliver Hartkopp default N 89ccb29637SOliver Hartkopp ---help--- 90ccb29637SOliver Hartkopp Say Y here if you want the CAN device drivers to produce a bunch of 91ccb29637SOliver Hartkopp debug messages to the system log. Select this if you are having 92ccb29637SOliver Hartkopp a problem with CAN support and want to see more of what is going 93ccb29637SOliver Hartkopp on. 94ccb29637SOliver Hartkopp 95ccb29637SOliver Hartkoppendmenu 96