On Wed, 4 Jul 2012, shaiju shaiju wrote: > > Hi Shaiju, > > > > The host controller sends two BUS_RESET during the enumeration, the first > > one > > is when the host controller detects there is a port change, the second > > one is after > > first GET_DESCRIPTOR. > > From your "dmesg-usb_debug-broke.out", -- see below > > It tells us the first BUS_RESET is successful, the line state goes to SE0, > > and > > PORT_ENABLE is 1. But there is a problem at the second BUS_RESET. > > > > Try to read your hub spec, and there is reset pin usually. Try to > > reset it at your > > platform code (before usb driver loads). There is no reset pin. The hub is integrated into the chipset, not external. > > Where should I do this ? In which function ? > > > > Is a port reset (once) in hub_port_init() will be enough ? > > > Usually, there is a Reset pin at HUB, you can use a GPIO to control it. > > Here I am attaching the spec I am using . I could n't find a pin > Reset the hub . I can reset the controller though. There's no way to do it. As far as I can see, this isn't something you can fix. It's bad hardware. You should talk to your vendor (Intel?). 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
