xhci: Workaround to get Intel xHCI reset working more reliably
authorRajmohan Mani <rajmohan.mani@intel.com>
Wed, 18 Nov 2015 08:48:20 +0000 (10:48 +0200)
committerBen Hutchings <ben@decadent.org.uk>
Wed, 30 Dec 2015 02:25:56 +0000 (02:25 +0000)
commit18fb47eeecd9103959e70700fdf0b2b392d8ab0e
tree1463206066499a019088f260b4deab71a724f217
parente40e3262d98d47dd8e7231e68124202e7a532d3d
xhci: Workaround to get Intel xHCI reset working more reliably

commit a5964396190d0c40dd549c23848c282fffa5d1f2 upstream.

Existing Intel xHCI controllers require a delay of 1 mS,
after setting the CMD_RESET bit in command register, before
accessing any HC registers. This allows the HC to complete
the reset operation and be ready for HC register access.
Without this delay, the subsequent HC register access,
may result in a system hang, very rarely.

Verified CherryView / Braswell platforms go through over
5000 warm reboot cycles (which was not possible without
this patch), without any xHCI reset hang.

Signed-off-by: Rajmohan Mani <rajmohan.mani@intel.com>
Tested-by: Joe Lawrence <joe.lawrence@stratus.com>
Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/usb/host/xhci.c