This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[OMAP35x]MUSB: musb not working after system resume

Other Parts Discussed in Thread: TPS65930, OMAP3530

Hi

    We are using 2.6.32 kernel from TI PSP: 3.0.1.6 on OMAP3530 with TPS65930.

We are observing that MUSB does not generate interrupts after resuming from system standby. This behavior is same whetjer the system is put into retention or in OFF mode during the standby.

TPS65930 generates USB interrupt without any problem when USB cable connected/disconnected.

Has anybody faced this issue? Is there any workaround for this problem?

 

Thanks and Regards

Ratheesh

  • TI PSP 3.0.1.6 is tested with OMAP3EVM which uses ISP1507 PHY and not TPS65930 PHY.

    So are you saying that MUSB doesn't work at all after resuming? whats your use case? Have you connected the cable to PC while in device mode or connected external devices to it while in host?

    Regards,
    Ajay

  • Hi

         We are connecting cable to PC in OTG mode. 

    Yes, MUSB doesn't work after resuming. I put printk in the MSUB ISR to confirm this. However if we remove and reinsert the gadget module, it will start working.

    One more observation we have made; if we insert and remove the USB cable repeatedly for serveral times, MUSB will stop responding occasionaly.

    Have you come accross this situation? Is there any fix for this issue?

    PS: We use g_file_storage USB gadget for testing MUSB.

    Thanks and Regards

    Ratheesh

     

     

     

  • you should first disconnect the cable or suspend the device from host PC first and then initiate the suspend.I have seen that system not entering into off mode with twl4030 USB PHY  and when cable is not connected also. below patch had helped me in this,

    http://marc.info/?l=linux-usb&m=129975136202670&w=2

    Regards,
    ajay