Hi, 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 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 Thank you, Regards, sriram On Wed, Mar 24, 2010 at 10:56 PM, Gadiyar, Anand <gadiyar@xxxxxx> wrote: > Sriram V wrote: > >> 1) I use 2.6.29 Kernel. >> 2) I use a SMSC 3320 PHY to which a hub is connected. I have 2 devices >> on the hub. My host is omap ehci. >> 3) When i suspend-resume the usb device i get the error "I get an >> error "PM: Device 1-2.2 failed to resume: error -19" > > Hi, > > There's an interoperability issue between this PHY and the OMAP3. > You won't be able to do USB suspend-resume with this PHY, if you're > using the EHCI controller. > > (See the OMAP3 errata docs for details). > > This is what folks using the beagleboard have been facing for a > while now. I'd recommend switching to another PHY. > > - 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
