linux/net/can
Oliver Hartkopp 6f3b911d5f can: bcm: add support for CAN FD frames
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.

Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
2016-06-17 15:39:46 +02:00
..
af_can.c can: replace timestamp as unique skb attribute 2015-07-12 21:13:22 +02:00
af_can.h can: build proc support only if CONFIG_PROC_FS is activated 2016-06-17 15:39:41 +02:00
bcm.c can: bcm: add support for CAN FD frames 2016-06-17 15:39:46 +02:00
gw.c can: cangw: introduce optional uid to reference created routing jobs 2015-06-09 09:39:49 +02:00
Kconfig can: Kconfig: switch on all CAN protocolls by default 2013-01-26 16:58:58 +01:00
Makefile can: build proc support only if CONFIG_PROC_FS is activated 2016-06-17 15:39:41 +02:00
proc.c can: build proc support only if CONFIG_PROC_FS is activated 2016-06-17 15:39:41 +02:00
raw.c sock: enable timestamping using control messages 2016-04-04 15:50:30 -04:00