Hi Paul, I noticed that this bug occurs with the old dwc_otg driver (from the Ralink SDK) as well, so it is not dwc2-specific. However, I also ound out this bug does not occur on another (identical) unit I have (using the old driver), so it seems likely that this is somehow a one-off (hardware) fault in my debug board. There is still a chance that running the dwc2 driver on a board makes it "faulty" forever afterwards (I have only ran the dwc2 driver on the "faulty" board so far, since that's the only one with a serial port soldered on). However, this doesn't seem so likely to me. I'll probably do a few more tests in the future, but for now I don't think this is a bug that should receive much more attention. Gr. Matthijs -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
