Lines Matching refs:FD
364 Remark about CAN FD (flexible data rate) support:
366 Generally the handling of CAN FD is very similar to the formerly described
367 examples. The new CAN FD capable CAN controllers support two different
368 bitrates for the arbitration phase and the payload phase of the CAN FD frame
373 switches the socket into a mode that allows the handling of CAN FD frames
383 __u8 flags; /* additional flags for CAN FD */
401 For details about the distinction of CAN and CAN FD capable devices and
404 The length of the two CAN(FD) frame structures define the maximum transfer
405 unit (MTU) of the CAN(FD) network interface and skbuff data length. Two
411 #define CANFD_MTU (sizeof(struct canfd_frame)) == 72 => CAN FD frame
584 CAN FD support in CAN_RAW sockets can be enabled with a new socket option
590 and CAN FD frames. OTOH the application has to handle CAN and CAN FD frames
609 printf("got CAN FD frame with length %d\n", cfd.len);
615 fprintf(stderr, "read: invalid CAN(FD) frame\n");
627 provided CAN FD structure. Note that the canfd_frame.flags data field is
629 CANFD_MTU sized CAN FD frames.
633 To build a CAN FD aware application use struct canfd_frame as basic CAN
637 or CAN FD frames and can process them the same way.
640 CAN FD frames by checking if the device maximum transfer unit is CANFD_MTU.
935 Broadcast Manager CAN FD Support
940 schema for the CAN FD frames a new flag 'CAN_FD_FRAME' in the bcm_msg_head
957 When using CAN FD frames for multiplex filtering the MUX mask is still
1076 dev->mtu = CANFD_MTU; /* sizeof(struct canfd_frame) -> CAN FD interface */
1321 CAN FD (Flexible Data Rate) Driver Support
1324 CAN FD capable CAN controllers support two different bitrates for the
1325 arbitration phase and the payload phase of the CAN FD frame. Therefore a
1326 second bit timing has to be specified in order to enable the CAN FD bitrate.
1328 Additionally CAN FD capable CAN controllers support up to 64 bytes of
1341 MTU = 72 (CANFD_MTU) => sizeof(struct canfd_frame) => CAN FD capable device
1344 N.B. CAN FD capable devices can also handle and send legacy CAN frames.
1346 When configuring CAN FD capable CAN controllers an additional 'data' bitrate
1347 has to be set. This bitrate for the data phase of the CAN FD frame has to be
1353 specified to enable the CAN FD mode in the CAN controller. This controller
1356 The first CAN FD specification presented as whitepaper at the International
1358 Therefore two CAN FD implementations have to be distinguished today:
1360 - ISO compliant: The ISO 11898-1:2015 CAN FD implementation (default)
1361 - non-ISO compliant: The CAN FD implementation following the 2012 whitepaper
1363 Finally there are three types of CAN FD controllers:
1367 3. ISO/non-ISO CAN FD controllers (switchable, like the PEAK PCAN-USB FD)
1370 netlink and displayed by the 'ip' tool (controller option FD-NON-ISO).
1372 switchable CAN FD controllers only.
1382 can <FD> state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
1393 Example when 'fd-non-iso on' is added on this switchable CAN FD adapter::
1395 can <FD,FD-NON-ISO> state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0