Oliver Hartkopp 6cfda7fbeb can: m_can: tag current CAN FD controllers as non-ISO ... During the CAN FD standardization process within the ISO it turned out that the failure detection capability has to be improved. The CAN in Automation organization (CiA) defined the already implemented CAN FD controllers as 'non-ISO' and the upcoming improved CAN FD controllers as 'ISO' compliant. See at http://www.can-cia.com/index.php?id=1937 Finally there will be three types of CAN FD controllers in the future: 1. ISO compliant (fixed) 2. non-ISO compliant (fixed, like the M_CAN IP v3.0.1 in m_can.c) 3. ISO/non-ISO CAN FD controllers (switchable, like the PEAK USB FD) So the current M_CAN driver for the M_CAN IP v3.0.1 has to expose its non-ISO implementation by setting the CAN_CTRLMODE_FD_NON_ISO ctrlmode at startup. As this bit cannot be switched at configuration time CAN_CTRLMODE_FD_NON_ISO must not be set in ctrlmode_supported of the current M_CAN driver. Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Cc: linux-stable <stable@vger.kernel.org> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>		2015-01-15 16:57:59 +01:00
..
bcm.h	can: unify identifiers to ensure unique include processing	2014-05-19 09:38:24 +02:00
error.h	can: dev: Consolidate and unify state change handling	2014-12-07 21:22:09 +01:00
gw.h	can: unify identifiers to ensure unique include processing	2014-05-19 09:38:24 +02:00
Kbuild	UAPI: (Scripted) Disintegrate include/linux/can	2012-10-10 22:24:21 +02:00
netlink.h	can: m_can: tag current CAN FD controllers as non-ISO	2015-01-15 16:57:59 +01:00
raw.h	can: unify identifiers to ensure unique include processing	2014-05-19 09:38:24 +02:00