| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354 |
- 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.
- 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.
- config CAN_SJA1000
- depends on CAN_DEV
- tristate "Philips SJA1000"
- ---help---
- Driver for the SJA1000 CAN controllers from Philips or NXP
- 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
|
