[mirror_ubuntu-bionic-kernel.git] / net / can / Kconfig

#
# Controller Area Network (CAN) network layer core configuration
#

menuconfig CAN
	depends on NET
	tristate "CAN bus subsystem support"
	---help---
	  Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
	  communications protocol which was developed by Bosch in
	  1991, mainly for automotive, but now widely used in marine
	  (NMEA2000), industrial, and medical applications.
	  More information on the CAN network protocol family PF_CAN
	  is contained in <Documentation/networking/can.txt>.

	  If you want CAN support you should say Y here and also to the
	  specific driver for your controller(s) below.

if CAN

config CAN_RAW
	tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
	default y
	---help---
	  The raw CAN protocol option offers access to the CAN bus via
	  the BSD socket API. You probably want to use the raw socket in
	  most cases where no higher level protocol is being used. The raw
	  socket has several filter options e.g. ID masking / error frames.
	  To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.

config CAN_BCM
	tristate "Broadcast Manager CAN Protocol (with content filtering)"
	default y
	---help---
	  The Broadcast Manager offers content filtering, timeout monitoring,
	  sending of RTR frames, and cyclic CAN messages without permanent user
	  interaction. The BCM can be 'programmed' via the BSD socket API and
	  informs you on demand e.g. only on content updates / timeouts.
	  You probably want to use the bcm socket in most cases where cyclic
	  CAN messages are used on the bus (e.g. in automotive environments).
	  To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM.

config CAN_GW
	tristate "CAN Gateway/Router (with netlink configuration)"
	default y
	---help---
	  The CAN Gateway/Router is used to route (and modify) CAN frames.
	  It is based on the PF_CAN core infrastructure for msg filtering and
	  msg sending and can optionally modify routed CAN frames on the fly.
	  CAN frames can be routed between CAN network interfaces (one hop).
	  They can be modified with AND/OR/XOR/SET operations as configured
	  by the netlink configuration interface known e.g. from iptables.

source "drivers/net/can/Kconfig"

endif
Commit	Line	Data
0d66548a OH	1	#
	2	# Controller Area Network (CAN) network layer core configuration
	3	#
	4
	5	menuconfig CAN
	6	depends on NET
	7	tristate "CAN bus subsystem support"
	8	---help---
	9	Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
	10	communications protocol which was developed by Bosch in
	11	1991, mainly for automotive, but now widely used in marine
	12	(NMEA2000), industrial, and medical applications.
	13	More information on the CAN network protocol family PF_CAN
	14	is contained in <Documentation/networking/can.txt>.
	15
	16	If you want CAN support you should say Y here and also to the
	17	specific driver for your controller(s) below.
c18ce101	18
77136836 MKB	19	if CAN
77136836 MKB	20
c18ce101 OH	21	config CAN_RAW
c18ce101 OH	22	tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
f66b0301	23	default y
c18ce101 OH	24	---help---
	25	The raw CAN protocol option offers access to the CAN bus via
	26	the BSD socket API. You probably want to use the raw socket in
	27	most cases where no higher level protocol is being used. The raw
	28	socket has several filter options e.g. ID masking / error frames.
	29	To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
ffd980f9 OH	30
	31	config CAN_BCM
	32	tristate "Broadcast Manager CAN Protocol (with content filtering)"
f66b0301	33	default y
ffd980f9 OH	34	---help---
	35	The Broadcast Manager offers content filtering, timeout monitoring,
	36	sending of RTR frames, and cyclic CAN messages without permanent user
	37	interaction. The BCM can be 'programmed' via the BSD socket API and
	38	informs you on demand e.g. only on content updates / timeouts.
	39	You probably want to use the bcm socket in most cases where cyclic
	40	CAN messages are used on the bus (e.g. in automotive environments).
	41	To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM.
ccb29637	42
c1aabdf3 OH	43	config CAN_GW
c1aabdf3 OH	44	tristate "CAN Gateway/Router (with netlink configuration)"
f66b0301	45	default y
c1aabdf3 OH	46	---help---
	47	The CAN Gateway/Router is used to route (and modify) CAN frames.
	48	It is based on the PF_CAN core infrastructure for msg filtering and
	49	msg sending and can optionally modify routed CAN frames on the fly.
	50	CAN frames can be routed between CAN network interfaces (one hop).
	51	They can be modified with AND/OR/XOR/SET operations as configured
	52	by the netlink configuration interface known e.g. from iptables.
ccb29637 OH	53
ccb29637 OH	54	source "drivers/net/can/Kconfig"
77136836 MKB	55
77136836 MKB	56	endif