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>
This commit is contained in:
		
					parent
					
						
							
								9b1087aa5e
							
						
					
				
			
			
				commit
				
					
						6cfda7fbeb
					
				
			
		
					 2 changed files with 6 additions and 0 deletions
				
			
		|  | @ -98,6 +98,7 @@ struct can_ctrlmode { | |||
| #define CAN_CTRLMODE_BERR_REPORTING	0x10	/* Bus-error reporting */ | ||||
| #define CAN_CTRLMODE_FD			0x20	/* CAN FD mode */ | ||||
| #define CAN_CTRLMODE_PRESUME_ACK	0x40	/* Ignore missing CAN ACKs */ | ||||
| #define CAN_CTRLMODE_FD_NON_ISO		0x80	/* CAN FD in non-ISO mode */ | ||||
| 
 | ||||
| /*
 | ||||
|  * CAN device statistics | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue
	
	 Oliver Hartkopp
				Oliver Hartkopp