• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 100 subscribers
  • Views 1340 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.

OMAP L138 as Multifunction Composite gadget

jumpto jumpto
Prodigy 10 points
Other Parts Discussed in Thread: OMAPL138

Dear all!

I have a question about Composite Device Drivers for OMAP L138. I am trying to create composite USB device with various drivers.

g_cdc works fine, but  g_multi causes a error message like:

root@arago:~# modprobe g_multi host_addr=00:cc:cc:01:23:45 dev_addr=00:dd:dd:67:
89:ac file=/dev/mmcblk0p1 cdrom=0 ro=0 iSerialNumber=123456789
[   52.165977] usb0: MAC 00:dd:dd:67:89:ac
[   52.188269] usb0: HOST MAC 00:cc:cc:01:23:45
[   52.229238] g_multi gadget: Mass Storage Function, version: 2009/09/11
[   52.235850] g_multi gadget: Number of LUNs=1
[   52.260155]  lun0: LUN: removable file: /dev/mmcblk0p1
[   52.288867] g_multi gadget: unable to autoconfigure all endpoints
[   52.368501] netconsole: network logging stopped, interface usb0 unregistered
FATAL: Error inserting g_multi (/lib/modules/2.6.37/kernel/drivers/usb/gadget/g_multi.ko): Unknown error 524

I use DVSDK 4.00.03.06, kernel 2.6.37

Is it possible to use L138 in multifunction mode?

  • 0
    TI__Expert 7885 points

    Hi

    Can you check whether g_multi gadget works in PIO mode ?

    In gadget mode the DMA is supported only for g_file_storage and g_ether gadget driver. It is not supported for g_multi gadget. This is limitation in DMA driver.

    There are patches available on 2.6.37 kernel for TI81XX platform which fixes this limitation. you can check in arago for latest patches.

    http://arago-project.org/git/projects/?p=linux-omap3.git;a=commit;h=6302b7f0dcc525362ae47850d30ebf37b3ccaadf

    Regards

    Ravi B

  • 0 in reply to Ravi B
    TI__Expert 7885 points

    Have you tried in PIO mode ?

    Regards

    Ravi B

  • 0 in reply to Ravi B
    Prodigy 20 points

    Hello Ravi,

    thanks for your answers!

    It works in PIO mode now.

    Sorry, we couldn't buid and check your patch for our device. We are working on OMAPL138 project. But your patch targets on OMAP3 as we understood. I quess these are quite diferent platforms. We would deeply appreciate if you can confirm that this DMA mode can be implemented for our device. For the time being we have some douts that it is supported by our hardware.

    Thank you in advance!

    Best Regards,

    Maxim Kostin

  • 0 in reply to Maxim Kostin
    TI__Expert 7885 points

    Maxim

    You need to back port all the DMA fixes to OMAPL138. Otherwise as you mentioned  PIO mode is working, at present you have to live with PIO mode.

    Regards

    Ravi B

  • 0 in reply to Ravi B
    Prodigy 20 points

    Ravi

    I am not sure I got you clearly. What do you mean by "to back port all DMA patches" ? Are there any DMA patches for OMAP L138? If you talk about patches for another platform it looks to be a big job and we must be sure it makes sense to do it. Could you just confirm that the DMA mode for both our gadgets is possible for OMAP L138 and there are no any HW issues?

    Thank you in advance!

    Maxim

  • 0 in reply to Maxim Kostin
    TI__Expert 7885 points

    Maxim

    >> what do you mean by "to back port all DMA patches"?

    The omapl138 uses cppi41 dma and ti81xx also uses the cppi41dma with more eps (15 Tx, 15 Rx). The cppi41dma driver used in ti81xx is based on omapl138, + with additional usb dma fixes. But these are not back ported on omapl138. That is the reason i said pull in the fixes from omapl138. Some of cppi41 dma features may not be applicable to omapl138, like txfifo empty interrupt feature, etc should be disabled for omapl138.

    Yes, it needs some effort port these patches.

    Regards

    Ravi B