Hi all, If I am not mistaken the current policy is to leave port power enabled at all times during over-current situations and let the power provider handle current limitation.
I experienced problems with the EHCI on an MPC8343E, which after some over-current situations no longer asserts the Connect Change Status Bit in the Port Status and Control Register, leading to the result that USB would be fully functional, but is no longer effectively serviced... The solution to this problem according to Freescale support would be to disable and re-enable port power after the over-current situation. Trying this with a hardware debugger gets us back in service. As I am no big fan of work-arounds and rather new to the USB-subsystem, might I ask what would be an accaptable way to patch this behaviour? Regards - Christian ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
