summaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorAhmed S. Darwish <ahmed.darwish@valeo.com>2015-02-26 18:22:02 +0300
committerMarc Kleine-Budde <mkl@pengutronix.de>2015-03-09 12:22:24 +0300
commit2fec5104f9c61de4cf2205aa355101e19a81f490 (patch)
tree7c3fa357f160f9bf6dc44d6d4a87bc73ac4117a5 /MAINTAINERS
parentdeb2701cf704a2fd03a8b598bf73df3edb08818d (diff)
downloadlinux-2fec5104f9c61de4cf2205aa355101e19a81f490.tar.xz
can: kvaser_usb: Read all messages in a bulk-in URB buffer
The Kvaser firmware can only read and write messages that are not crossing the USB endpoint's wMaxPacketSize boundary. While receiving commands from the CAN device, if the next command in the same URB buffer crossed that max packet size boundary, the firmware puts a zero-length placeholder command in its place then moves the real command to the next boundary mark. The driver did not recognize such behavior, leading to missing a good number of rx events during a heavy rx load session. Moreover, a tx URB context only gets freed upon receiving its respective tx ACK event. Over time, the free tx URB contexts pool gets depleted due to the missing ACK events. Consequently, the netif transmission queue gets __permanently__ stopped; no frames could be sent again except after restarting the CAN newtwork interface. Signed-off-by: Ahmed S. Darwish <ahmed.darwish@valeo.com> Cc: linux-stable <stable@vger.kernel.org> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions