On Wed, Dec 11, 2013 at 11:00:13AM -0800, Julius Werner wrote: > > I don't know what you mean by "fails". The system goes to sleep and > > then later on wakes up, doesn't it? > > > > Do you mean that the Jetflash device gets disconnected when the system > > wakes up? That's _supposed_ to happen under those circumstances. > > When hub_activate() sees HUB_RESET_RESUME, all child devices get > > disconnected except those where udev->persist_enabled is set. > > This patch was written in response to the same bug as my "usb: hub: > Use correct reset for wedged USB3 devices that are NOTATTACHED" > submission. My patch only helps when the port gets stuck in Compliance > Mode, but Vikas reports that he can sometimes see it stuck in Polling > or Recovery states as well. > > The underlying issue is a deadlock in the USB 3.0 link training state > machine when the host controller is unilaterally reset on resume > (without driving a reset on the bus). The xHCI spec requires that when the xHCI host is reset, a USB reset is driven down the USB 3.0 ports. If hot reset fails, the port may migrate to warm reset. See table 32 in the xHCI spec, in the definition of HCRST. It sounds like this host doesn't drive a USB reset down USB 3.0 ports at all on host controller reset? > The host port starts out back in > Rx.Detect without remembering anything about its previous state, but > the device is still in U3. The host detects Rx terminations, moves to > Polling and starts sending LFPS link training packets, but the device > doesn't expect those and interprets them as link problems (moving to > Recovery). What happens next seems to be device specific, but > apparently the device can end up in SS.Inactive while the host port > gets stuck in Polling or Recovery (or some kind of livelock between > those). > > This patch tries to warm reset all USB 3.0 ports on reset-resume > (after xhci_reset() was called) that had devices connected to them > before suspend. This seems to be the only way to ensure the devices' > state machines get back to a well-defined state that the host can work > with. I don't think this is a specific hardware bug, it's just an > unfortunate design flaw that the USB 3.0 spec doesn't account for a > root hub port being reset independently of its connected device. I > think Sarah is correct that it could be limited to root hubs, though. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |