Hello. On 11/08/2012 07:05 PM, Alan Stern wrote: >> USB specs says that if an over-current is detected then a hub must switch off >> all affected port, wait to cool down and then switch on. >> There are few controllers, which does not follow it, and expects software >> to switch off the port power. > Can you give any examples? The example that springs to my mind is EHCI -- but the EHCI driver takes care for switching the port off. >> This patch will add workaround for such controllers. Pratyush, I don't see where it waits for port to cool down and switch the power back on and I assume it's already done by the current code. Why claim that it's *you* who's doing it now? >> I think it will not affect others, even if HW switch off the port power. >> Signed-off-by: Pratyush Anand <pratyush.anand@xxxxxx> WBR, Sergei -- 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