Hi, On 27/01/17 17:47, Felipe Balbi wrote: > > Hi, > > (hmm, I didn't receive your reply in my intel inbox, only > gmail. Odd. Replying to myself here, but it should be on your reply, > rater). > > Felipe Balbi <balbi@xxxxxxxxxx> writes: >>> The previous commit c499ff71ff2a281366c6ec7a904c547d806cbcd1 is fine. >> >> okay. Then let's try to figure out what's going on. A diff of regdump >> before and after suspend/resume might start to give some clue about >> what's going on. DWC3 tracepoints should help too. Care to get those? >> BTW, is this dwc3 as host or peripheral? > > You don't have any endpoints enabled: > > -DALEPENA = 0x0000000f > +DALEPENA = 0x00000000 Thanks for the hints. This problem is because reason dwc3_gadget_run_stop() is timing out during the suspend sequence and so dwc3_disconnect_gadget() and __dwc3_gadget_stop() are not being called. dwc3_suspend() does not consider dwc3_gadget_suspend()'s return value and happily continues suspending the machine. If I force dwc3_gadget_run_stop() to return 0 then everything works fine. Any ideas why DWC3_DSTS_DEVCTRLHLT is not getting set? I checked that DWC3_GEVNTCOUNT(0) is zero. cheers, -roger -- 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
