Hi Felipe, On Wed, Feb 24, 2016 at 7:47 AM, Felipe Balbi <[email protected]> wrote:
> Then what DOES get called ? If we don't reach runtime_pm of the PHY, we > must reach runtime_pm of chipidea. In that case, detect _there_ if > you're running on one of the known broken ones and return -EBUSY or > something like that. We don't reach runtime_pm in chipidea either. The reason is that mx23/mx28 do not turn on the CI_HDRC_SUPPORTS_RUNTIME_PM flag in drivers/usb/chipidea/ci_hdrc_imx.c. The errors are: hub 1-1:1.0: USB hub found hub 1-1:1.0: 2 ports detected usb 1-1: USB disconnect, device number 2 usb usb1-port1: cannot reset (err = -32) usb usb1-port1: cannot reset (err = -32) usb usb1-port1: cannot reset (err = -32) usb usb1-port1: cannot reset (err = -32) usb usb1-port1: cannot reset (err = -32) usb usb1-port1: Cannot enable. Maybe the USB cable is bad? which come from drivers/usb/core/hub.c. Passing "usbcore.autosuspend=-1" make things to work fine. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
