On Tue, 31 Jan 2012, Sarah Sharp wrote: > > In fact, all HCDs need to address this sort of problem. It looks like > > the best answer is to disable IRQ generation at the start of > > bus_suspend and call synchronize_irq(). As a bonus, the remainder of > > bus_suspend can run without holding the private lock, since no other > > threads will enter the driver until the suspend finishes and IRQ > > generation is re-enabled. > > What you described (disabling IRQs, etc) needs to be done in > xhci_bus_suspend() as well, correct? Or were you thinking it could be > done in the USB core, since other HCDs also have this problem? It can't be done in the core, because the core doesn't know how to tell the hardware to stop generating IRQs. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
