On Wed, Dec 05, 2012 at 11:55:59AM -0500, Alan Stern wrote:
> On Tue, 4 Dec 2012, Sarah Sharp wrote:
> > +static int hub_set_port_link_state(struct usb_hub *hub, int port1,
> > + unsigned int link_status)
> > +{
> > + return set_port_feature(hub->hdev,
> > + po
On Tue, 4 Dec 2012, Sarah Sharp wrote:
> If hot and warm reset fails, or a port remains in the Compliance Mode,
> the USB core needs to be able to disable a USB 3.0 port. Unlike USB 2.0
> ports, once the port is placed into the Disabled link state, it will not
> report any new device connects. T
If hot and warm reset fails, or a port remains in the Compliance Mode,
the USB core needs to be able to disable a USB 3.0 port. Unlike USB 2.0
ports, once the port is placed into the Disabled link state, it will not
report any new device connects. To get device connect notifications, we
need to p
