On Fri, 7 Dec 2012, Sarah Sharp wrote:
> > > 2. It doesn't consider a connect status change to be a failed reset. If
> > > multiple warm resets needed to be issued, the connect status may have
> > > changed, so we need to ignore that and look at the port link state
> > > instead. hub_port_reset
On Wed, Dec 05, 2012 at 02:41:11PM -0500, Alan Stern wrote:
> On Tue, 4 Dec 2012, Sarah Sharp wrote:
>
> > When a hot reset fails on a USB 3.0 port, the current port reset code
> > recursively calls hub_port_reset inside hub_port_wait_reset. This isn't
> > ideal, since we should avoid recursive c
On Tue, 4 Dec 2012, Sarah Sharp wrote:
> When a hot reset fails on a USB 3.0 port, the current port reset code
> recursively calls hub_port_reset inside hub_port_wait_reset. This isn't
> ideal, since we should avoid recursive calls in the kernel, and it also
> doesn't allow us to issue multiple w
When a hot reset fails on a USB 3.0 port, the current port reset code
recursively calls hub_port_reset inside hub_port_wait_reset. This isn't
ideal, since we should avoid recursive calls in the kernel, and it also
doesn't allow us to issue multiple warm resets on reset failures.
Rip out the recur
