• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 670 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OMAP4 OTG broken in Linux 3.16

Edward Bockhoefer
Prodigy 120 points


Greetings,

I'm using the Panda-es omap4460 development board. Just moved from kernel 3.12 to kernel 3.16 and OTG port appears to be broken now using the same kernel config. The software comes from Robert Nelson at
"http://eewiki.net/display/linuxonarm/PandaBoard".
I know some power management improvements were added to the kernel by TI recently. Don't know if that is a possible cause. I'm only interest in the USB B side of the OTG port (client side). None of the gadget devices seem to be working now. I do not see anything on the PC side other than an occasional error from dmesg on the PC side of "sdb: detected capacity change from 127864930304 to 0" when I insert the g_mass_storage gadget driver.

The Panda-es board has the following error at dmesg of
" musb-hdrc musb-hdrc.0.auto: configured as A device timeout"
from dev_err(musb->controller, "configured as A device timeout"). The omap2430_musb_set_vbus function in the omap2430.c file. This was working in 3.12. Not sure where to start debugging. Might be hardware related??? Maybe something changed with the device tree files. I'm also using U-Boot SPL 2014.07.

Best Regards,
Ed

  • 0
    TI__Genius 10965 points

    Hi Ed,

    There are no TI official releases for omap4  based on the 3.16 kernel.

    On the other hand , the issue maybe caused because of the pm runtime patches applied there.

    Best you can do is browse the patch history and try to  exclude them with a minimum change.

    Regards,

    Boyko

  • 0 in reply to Boyko Kazakov
    Prodigy 120 points

    Hi Boyko,
    Yes...I do realize this. I would like the PM working. Which it seems to work now thanks to TI. I was hoping someone else would be using the same sources and found a similar result, and or a fix. No worries. I can post soemthing to the Nelson blog or ask Nishanth Menon at TI. This forum was probably not the place to ask. My bad.

    Take care,
    Ed