usb: dwc2: host: reset frame number after suspend
authorGregory Herrero <gregory.herrero@intel.com>
Tue, 22 Sep 2015 13:16:45 +0000 (15:16 +0200)
committerFelipe Balbi <balbi@ti.com>
Thu, 1 Oct 2015 17:40:16 +0000 (12:40 -0500)
commit08c4ffc24087d1949948002abdbac0d1e71ade5d
tree3298f2b031f9d40c51b3c0fb68748af49c73edd5
parentbea78555f71e01196d0a4613ffefd4c8920ba439
usb: dwc2: host: reset frame number after suspend

Frame number is reset in hardware after exiting hibernation.
Thus, reset frame_number and ensure qh are queued with correct
sched_frame.

Otherwise, qh->sched_frame may be too high compared to
current frame number (which is 0). This can delay addition of qh in
the list of transfers until frame number reaches qh->sched_frame.

Signed-off-by: Gregory Herrero <gregory.herrero@intel.com>
Signed-off-by: Mian Yousaf Kaukab <yousaf.kaukab@intel.com>
Tested-by: Robert Baldyga <r.baldyga@samsung.com>
Tested-by: Dinh Nguyen <dinguyen@opensource.altera.com>
Tested-by: John Youn <johnyoun@synopsys.com>
Acked-by: John Youn <johnyoun@synopsys.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
drivers/usb/dwc2/core.c
drivers/usb/dwc2/hcd_queue.c
This page took 0.024578 seconds and 5 git commands to generate.