can: CAN Network device driver and Netlink interface

The CAN network device driver interface provides a generic interface to
setup, configure and monitor CAN network devices. It exports a set of
common data structures and functions, which all real CAN network device
drivers should use. Please have a look to the SJA1000 or MSCAN driver
to understand how to use them. The name of the module is can-dev.ko.

Furthermore, it adds a Netlink interface allowing to configure the CAN
device using the program "ip" from the iproute2 utility suite.

For further information please check "Documentation/networking/can.txt"

Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
Signed-off-by: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
Signed-off-by: David S. Miller <davem@davemloft.net>

1 files changed, 23 insertions, 0 deletions

diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig
index 57def0d57371..77adb8ef6e4f 100644
--- a/drivers/net/can/Kconfig
+++ b/drivers/net/can/Kconfig
@@ -12,6 +12,29 @@ config CAN_VCAN
           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_DEBUG_DEVICES
         bool "CAN devices debugging messages"
         depends on CAN