Hi, I apologize for my late response. I failed to flag this email for reply. On Fri, Jan 27, 2017 at 08:50:24PM +0100, Tasslehoff Kjappfot wrote: > Hi. > > I'm struggling with an issue on an old omap 3530 running linux 2.6.39, and > since you seem to be the maintainer for musb I'll chance asking you a > question. I don't have experience on omap3530 musb, I believe it uses an external PHY, isn't it? > > We're stuck on 2.6.39, and it mostly serves us well. Lately an old issue > has resurfaced. We have musb connected to an smsc95xx. We run reboot tests smsc95xx is permanently on the board? or attached to an usb port? > on this hardware, and occasionally the systems come up without an IP > address. When that happens, it seems that the kernel does not discover the > smsc95xx at all. A soft reboot does not fix it, so we have to turn the > systems completely off before it rights itself. This sounds like an enumeration problem. When the issue happens, does MUSB generate MUSB_CONNECT interrupt? If so, it is likely an software problem, you can debug the drivers where the enumeration failed. If not, it sounds like electrical issue, you can first probe the USB bus lines, VBUS, D+/D-, to check if the signals are correct from timing perspective. > > I've looked for kernel and u-boot patches related to this (particularly in > musb) without finding anything, but since we're stuck on a kernel right > before major usb rewrites and the introduction of device tree, it may have > slipped past me. > > Do you recall any fixes that could be related to the issue I'm seeing? Sorry no. Regards, -Bin. -- 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
