8729856c19
Per https://docs.xilinx.com/r/en-US/ug1085-zynq-ultrascale-trm/Message-Format
Message Format
The same message format is used for RXFIFO, TXFIFO, and TXHPB.
Each message includes four words (16 bytes). Software must read
and write all four words regardless of the actual number of data
bytes and valid fields in the message.
There is no mention in this reference manual about what the
hardware does when not all four words are read. To fix the
reported underflow behavior, I choose to fill the 4 frame data
registers when the first register (ID) is accessed, which is how
I expect hardware would do.
Reported-by: Qiang Liu <cyruscyliu@gmail.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Francisco Iglesias <francisco.iglesias@amd.com>
Reviewed-by: Vikram Garhwal <vikram.garhwal@amd.com>
Message-id: 20231124183325.95392-3-philmd@linaro.org
Fixes:
|
||
|---|---|---|
| .. | ||
| can_kvaser_pci.c | ||
| can_mioe3680_pci.c | ||
| can_pcm3680_pci.c | ||
| can_sja1000.c | ||
| can_sja1000.h | ||
| ctu_can_fd_frame.h | ||
| ctu_can_fd_regs.h | ||
| ctucan_core.c | ||
| ctucan_core.h | ||
| ctucan_pci.c | ||
| meson.build | ||
| trace-events | ||
| trace.h | ||
| xlnx-versal-canfd.c | ||
| xlnx-zynqmp-can.c | ||