10d66548aSOliver Hartkopp# 20d66548aSOliver Hartkopp# Controller Area Network (CAN) network layer core configuration 30d66548aSOliver Hartkopp# 40d66548aSOliver Hartkopp 50d66548aSOliver Hartkoppmenuconfig CAN 60d66548aSOliver Hartkopp depends on NET 70d66548aSOliver Hartkopp tristate "CAN bus subsystem support" 80d66548aSOliver Hartkopp ---help--- 90d66548aSOliver Hartkopp Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial 100d66548aSOliver Hartkopp communications protocol which was developed by Bosch in 110d66548aSOliver Hartkopp 1991, mainly for automotive, but now widely used in marine 120d66548aSOliver Hartkopp (NMEA2000), industrial, and medical applications. 130d66548aSOliver Hartkopp More information on the CAN network protocol family PF_CAN 140d66548aSOliver Hartkopp is contained in <Documentation/networking/can.txt>. 150d66548aSOliver Hartkopp 160d66548aSOliver Hartkopp If you want CAN support you should say Y here and also to the 170d66548aSOliver Hartkopp specific driver for your controller(s) below. 18c18ce101SOliver Hartkopp 19c18ce101SOliver Hartkoppconfig CAN_RAW 20c18ce101SOliver Hartkopp tristate "Raw CAN Protocol (raw access with CAN-ID filtering)" 21c18ce101SOliver Hartkopp depends on CAN 22c18ce101SOliver Hartkopp default N 23c18ce101SOliver Hartkopp ---help--- 24c18ce101SOliver Hartkopp The raw CAN protocol option offers access to the CAN bus via 25c18ce101SOliver Hartkopp the BSD socket API. You probably want to use the raw socket in 26c18ce101SOliver Hartkopp most cases where no higher level protocol is being used. The raw 27c18ce101SOliver Hartkopp socket has several filter options e.g. ID masking / error frames. 28c18ce101SOliver Hartkopp To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW. 29ffd980f9SOliver Hartkopp 30ffd980f9SOliver Hartkoppconfig CAN_BCM 31ffd980f9SOliver Hartkopp tristate "Broadcast Manager CAN Protocol (with content filtering)" 32ffd980f9SOliver Hartkopp depends on CAN 33ffd980f9SOliver Hartkopp default N 34ffd980f9SOliver Hartkopp ---help--- 35ffd980f9SOliver Hartkopp The Broadcast Manager offers content filtering, timeout monitoring, 36ffd980f9SOliver Hartkopp sending of RTR frames, and cyclic CAN messages without permanent user 37ffd980f9SOliver Hartkopp interaction. The BCM can be 'programmed' via the BSD socket API and 38ffd980f9SOliver Hartkopp informs you on demand e.g. only on content updates / timeouts. 39ffd980f9SOliver Hartkopp You probably want to use the bcm socket in most cases where cyclic 40ffd980f9SOliver Hartkopp CAN messages are used on the bus (e.g. in automotive environments). 41ffd980f9SOliver Hartkopp To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM. 42*ccb29637SOliver Hartkopp 43*ccb29637SOliver Hartkopp 44*ccb29637SOliver Hartkoppsource "drivers/net/can/Kconfig" 45