OMAPL138: USB driver

For Question #1:

          If you are using the OMAPL138, i think you are talking about OHCI support in uboot (please confirm). If yes no OHCI support available in u-boot.

For Question #2:

           I did not understand your question completely. Can you explain issue in detail ? whether OMAPL138 is configured in host mode or device mode. What is the setup or system scenario?

Regards

Ravi B

Stefan

see my answers....

For question 1, we did not talk about USB1.1 OHCI, Customer want to know whether USB2.0 support EHCI (Enhanced Host Controller Interface, in the attachment is the EHCI specification from intel) or not.  If we support, did we test it

[Ravi ] : If you are referring to OMAPL138 platform, EHCI is not supported. OMAPL138 platform supports only the USB2.0 musb support and USB1.1 OHCI. Can you point me to the spec of platform you are referring where EHCI is mentioned. Please confirm this.

For second question,

   Customer use USB 2.0 to extend Ethernet( they use SMSC’s Ethernet CHIP, the chip connect to our OMAPL138 via USB 2.0), our OMAPL138 USB2.0 work at host mode,   

[Ravi] If I understand correctly, the OMAPL138 as CDC-Host to connected the USB-Ethernet network device (SMSC Ethernet CHIP) to USB2.0 port. As part of PSP release, this feature is not in scope. But if CDC-HOST enabled in usb kernel configuration it will work.

customer just want to know if they send a big size package data to the Ethernet chip Via USB, did our USB driver just divide the big size package to several small size package? Or other methods to deal with big size package.

   If our driver divide the big size package into several small size package, what ‘s the max size of small one?

   If you have any question, please let me know. Thanks a lot.

[Ravi] This feature is part of CDC-host application driver, this feature do not have any impact on USB2.0 musb driver is concerned.

Regards

Ravi B

Adding the replies discussed on mail:

Mail from Ajay to Steven:

===================

EHCI and MUSB are two different host controller and SMSC LAN9500 device can work with either of them.

OMAPL138 has only MUSB controller and thus customer can use this to connect SMSC LAN9500 device.

I didn’t understand your 2^nd point so can you please provide the descriptor set of SMSC9500 by sending us

the output of “cat /proc/bus/usb/devices” when it is connected to linux host.

Steven's reply to above:

=================

For the “bulk package”, SMSC think they need to divide some big size package to some small size package to process. So, they want to know how to handle the big size package in our release.

For your information, below is the “devices” file content. Would you help to check?

================= Ajay's reply

The descriptor data shows that the LAN device has one BULK IN , one BULK OUT and an INTERRUPT In endpoint.

E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms => BULK IN with packet size = 512
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms   => BULK OUT with packet size= 512

E:  Ad=83(I) Atr=03(Int.) MxPS=  16 Ivl=125us => INTERRUPT IN with packet size=16

This is a high speed device and so it has to use packet size of 512 bytes on BULK endpoints.

==================== Steven's reply

So, our PSP release (OMAPL138 PSP release 03.20.00.14) can meet this package processing requirement (512 Bytes package)? Or this need their driver to do?

====================== Ajay's reply

PSP drivers can handle high speed request with bulk packet size of 512.

======================== END

Hi Ajay/Ravi,

I am using OMAPL138 chip for our project.

For USB0 (USB2.0) we have connected smsc9500 and we are using QNX.

USB0 and smsc9500 interface is working fine for normal ping and data connection.

But when we bombard the smsc9500 Ethernet port with UDP packets of size more than 1500 Bytes continuously without pause  cpu usage is going 100% and QNX freezes all its operation. If we stop bombarding of UDP packets, then QNX start working smoothly.

In QNX, io-net and io-usb is taking full CPU time.

smsc9500 is working fine with EHCI interface on panda board and for above test it is taking 1% of CPU usage.

Have you tried above test on OMAPL138 Linux environment?

your post say that EHCI and MUSB  can be used for smsc9500, What is the EHCI and MUSB speed support? are they same?(If speed is same then On QNX smsc9500 should work)

OMAPL138 document I've not seen any MUSB info, but for USB1 USB1.1 I've seen OHCI info. Let us know more info on MUSB with respect to OMAPL138.

Thanks in Adavance

Hi Sheshadri,

Could you please create new post for your question ?