Hi xilinx_can maintainers,
Hartley Sweeten reported a bug when sending RTR frames with the
xilinx_can driver here:
https://github.com/linux-can/can-utils/issues/405#
The problem: When sending a single RTR frame (e.g. with 'cansend can0
001#R') nothing happens.
Only after sending a *second* RTR frame with 'cansend can0 001#R' the
two (pending) RTR-frames are sent directly after each other.
This faulty behavior of RTR frame sending is independent of the time gap
between the two cansend attempts.
Best regards,
Oliver
