Lines Matching refs:FD
231 The Classical CAN frame structure (aka CAN 2.0B), the CAN FD frame structure
397 Remark about CAN FD (flexible data rate) support:
399 Generally the handling of CAN FD is very similar to the formerly described
400 examples. The new CAN FD capable CAN controllers support two different
401 bitrates for the arbitration phase and the payload phase of the CAN FD frame
406 switches the socket into a mode that allows the handling of CAN FD frames
416 __u8 flags; /* additional flags for CAN FD */
434 For details about the distinction of CAN and CAN FD capable devices and
437 The length of the two CAN(FD) frame structures define the maximum transfer
438 unit (MTU) of the CAN(FD) network interface and skbuff data length. Two
444 #define CANFD_MTU (sizeof(struct canfd_frame)) == 72 => CAN FD frame
619 CAN FD support in CAN_RAW sockets can be enabled with a new socket option
625 and CAN FD frames. OTOH the application has to handle CAN and CAN FD frames
644 printf("got CAN FD frame with length %d\n", cfd.len);
650 fprintf(stderr, "read: invalid CAN(FD) frame\n");
662 provided CAN FD structure. Note that the canfd_frame.flags data field is
664 CANFD_MTU sized CAN FD frames.
668 To build a CAN FD aware application use struct canfd_frame as basic CAN
672 or CAN FD frames and can process them the same way.
675 CAN FD frames by checking if the device maximum transfer unit is CANFD_MTU.
972 Broadcast Manager CAN FD Support
977 schema for the CAN FD frames a new flag 'CAN_FD_FRAME' in the bcm_msg_head
994 When using CAN FD frames for multiplex filtering the MUX mask is still
1113 dev->mtu = CANFD_MTU; /* sizeof(struct canfd_frame) -> CAN FD interface */
1392 CAN FD (Flexible Data Rate) Driver Support
1395 CAN FD capable CAN controllers support two different bitrates for the
1396 arbitration phase and the payload phase of the CAN FD frame. Therefore a
1397 second bit timing has to be specified in order to enable the CAN FD bitrate.
1399 Additionally CAN FD capable CAN controllers support up to 64 bytes of
1412 MTU = 72 (CANFD_MTU) => sizeof(struct canfd_frame) => CAN FD capable device
1415 N.B. CAN FD capable devices can also handle and send Classical CAN frames.
1417 When configuring CAN FD capable CAN controllers an additional 'data' bitrate
1418 has to be set. This bitrate for the data phase of the CAN FD frame has to be
1424 specified to enable the CAN FD mode in the CAN controller. This controller
1427 The first CAN FD specification presented as whitepaper at the International
1429 Therefore two CAN FD implementations have to be distinguished today:
1431 - ISO compliant: The ISO 11898-1:2015 CAN FD implementation (default)
1432 - non-ISO compliant: The CAN FD implementation following the 2012 whitepaper
1434 Finally there are three types of CAN FD controllers:
1438 3. ISO/non-ISO CAN FD controllers (switchable, like the PEAK PCAN-USB FD)
1441 netlink and displayed by the 'ip' tool (controller option FD-NON-ISO).
1443 switchable CAN FD controllers only.
1453 can <FD> state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
1464 Example when 'fd-non-iso on' is added on this switchable CAN FD adapter::
1466 can <FD,FD-NON-ISO> state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0