Martin Gagnon wrote: > By using a Linux OS and reproducing the same problem, we were able to > get a lead further towards the IN control endpoint from our USB audio > device. Again, for some reason, the bus driver is resetting the device, > and it seems that there is a timeout on the in transactions that is > happening (the IN transactions are at every millisecond, which we > believe is way too often for a control endpoint sending HID input value > from the volume up/down buttons on the chip). > > So we went ahead and disabled the HID control device from our USB audio > device, and the problem goes away. We still want to understand why this > situation happens. In Linux, you can enable "USB verbose debug messages" (CONFIG_USB_DEBUG) in the kernel configuration. This might tell you why the reset happens, and who initiates it. > Does anybody know if an IN transaction for reporting button control > value makes any sense to happen every millisecond? I'd guess the drivers just use the interval from the descriptor. Best regards, Clemens ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/