4d107feca9
...when attempting to start a receiving USB transfer. Previously, we would check on the IN endpoint which is the transmitting part of the USB endpoint. This is wrong and lead to two USB transfers being started immediately after each other in case of e.g. RAW HID endpoints: 1. When finishing an OUT transfer the low level USB driver calls the out_cb callback, which in turn initiates another OUT transfer by calling qmkusbDataReceived. 2. When the raw hid receive channel runs empty inside the raw_hid task, another OUT transfer is started to potentially fill the channel again. This happens by calling ibnotify. Both events occur directly after each other, thus triggering the bug. |
||
|---|---|---|
| .. | ||
| arm_atsam | ||
| chibios | ||
| lufa | ||
| midi | ||
| usb_hid | ||
| vusb | ||
| arm_atsam.mk | ||
| chibios.mk | ||
| host_driver.h | ||
| host.c | ||
| host.h | ||
| lufa.mk | ||
| midi.mk | ||
| report.c | ||
| report.h | ||
| serial_soft.c | ||
| serial_uart.c | ||
| serial.h | ||
| usb_descriptor_common.h | ||
| usb_descriptor.c | ||
| usb_descriptor.h | ||
| usb_device_state.c | ||
| usb_device_state.h | ||
| usb_hid.mk | ||
| usb_util.c | ||
| usb_util.h | ||
| vusb.mk | ||