> Thank You, I went through the errata document. Probably that > explains the usb suspend-resumes failures. > Now that we use this part on your board. Cant we support > suspend-resume for other interfaces at all without getting "usb resume > failures" > My understanding is - If suspend-resume has to work then we need to > put all the interfaces to suspend. > Is there a workaround/hack? > I'm afraid not. We've tried our best to find one and looks like the only option is to use a different part, if you need selective suspend/resume. > I guess evm uses SMSC3223. suspend-resume works on that part > according to the patch > > http://e2e.ti.com/support/arm174_microprocessors/omap_applications_processors/f/42/p/29363/102101.aspx#102101 I'm fairly certain it doesn't. What this patch enables seems to be to allow the OMAP3 to enter low-power modes (by disabling clocks in the suspend path). This is on the TODO list for the driver, and upcoming patches will address that. However, this patch will not allow you to resume a selectively suspended device with the SMSC332X parts. Note: If you are using a hub, then you should be able to selectively suspend the devices connected through that hub. You may need to disable autosuspend for the hub, but you should be able to suspend and resume all connected devices. Maybe this will help? - Anand -- 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
