The programming API of the CAN_BCM depends on struct can_frame which is given as array directly behind the bcm_msg_head structure. To follow this schema for the CAN FD frames a new flag 'CAN_FD_FRAME' in the bcm_msg_head flags indicates that the concatenated CAN frame structures behind the bcm_msg_head are defined as struct canfd_frame. This patch adds the support to handle CAN and CAN FD frames on a per BCM-op base. Main changes: - generally use struct canfd_frames instead if struct can_frames - use canfd_frame.flags instead of can_frame.can_dlc for private BCM flags - make all CAN frame sizes depending on the new CAN_FD_FRAME flags - separate between CAN and CAN FD when sending/receiving frames Due to the dependence of the CAN_FD_FRAME flag the former binary interface for classic CAN frames remains stable.
Showing the changes to include/uapi/linux (1 of 2 files). Show all
Unified · Split
| @@ -99,5 +99,6 @@ enum { · 98 unmodified lines | ||
| 99 | 99 | #define RX_ANNOUNCE_RESUME 0x0100 |
| 100 | 100 | #define TX_RESET_MULTI_IDX 0x0200 |
| 101 | 101 | #define RX_RTR_FRAME 0x0400 |
| 102 | +#define CAN_FD_FRAME 0x0800 | |
| 102 | 103 | |
| 103 | 104 | #endif /* !_UAPI_CAN_BCM_H */ |