can: dev: Consolidate and unify state change handling
The handling of can error states is different between platforms. This is an attempt to correct that problem. I've moved this handling into a generic function for changing the error state. This ensures that error state changes are handled the same way everywhere (where this function is used). This new mechanism also adds reverse state transitioning in error frames, i.e. the user will be notified through the socket interface when the state goes down. Signed-off-by: Andri Yngvason <andri.yngvason@marel.com> Acked-by: Wolfgang Grandegger <wg@grandegger.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
This commit is contained in:
		
					parent
					
						
							
								04ee0865d1
							
						
					
				
			
			
				commit
				
					
						bac78aabcf
					
				
			
		
					 3 changed files with 82 additions and 0 deletions
				
			
		|  | @ -71,6 +71,7 @@ | |||
| #define CAN_ERR_CRTL_TX_PASSIVE  0x20 /* reached error passive status TX */ | ||||
| 				      /* (at least one error counter exceeds */ | ||||
| 				      /* the protocol-defined level of 127)  */ | ||||
| #define CAN_ERR_CRTL_ACTIVE      0x40 /* recovered to error active state */ | ||||
| 
 | ||||
| /* error in CAN protocol (type) / data[2] */ | ||||
| #define CAN_ERR_PROT_UNSPEC      0x00 /* unspecified */ | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue
	
	 Andri Yngvason
				Andri Yngvason