On Wed, Sep 08, 2010 at 09:07:42PM +0530, Pavan Kondeti wrote: > > > > I have started manipulating HW_ACCESSIBLE flag initially and faced some > > > problems. This was on 2.6.29 kernel. So I have decided to use usb_add_hcd and > > > usb_remove_hcd upon Id state change. But this is causing problems in meeting > > > HNP timings. When HNP is started, host is suspended by clearing HW_ACCESSIBLE > > > flag, disabling autosuspend, and changing it usb state to NOT_ATTACHED. > > > > You should change the state to NOT_ATTACHED first. I hope you do this > > by calling usb_set_device_state(). > > > > udev->state is directly changed to NOT_ATTACHED. The reason, I have not used > this API is that it blocks till the children device is disconnected (i.e class > driver's unbind is called). Is this API have an async version? > Sorry. I was confused with usb_disconnect API. I have not tried using usb_set_device_state() API. I will use this API to change root hub state during HNP. -- Sent by a consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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
