Forums » Software Development »
can't detect USB2.0 device
Added by yilin wang over 11 years ago
I'm using a USB 2.0 ethernet adapter with mityARM-1808.
It works good in 2.6.34.rc1 kernel but bad in 3.2.0.
I do almost same configuration to build the kernel, but the results turn different.
When boot 2.6.34, the kernel could detect the USB 2.0 ethernet adapter, and print message like this:
...
...
musb_hdrc: version 6.0, pio, host, debug=0
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.34-rc1 musb-hcd
usb usb1: SerialNumber: musb_hdrc
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
...
...
usb 1-1: new high speed USB device using musb_hdrc and address 2
usb 1-1: New USB device found, idVendor=0424, idProduct=7500
usb 1-1: New USB strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: LAN7500
usb 1-1: Manufacturer: SMSC
usb 1-1: SerialNumber: 00000001b
...
...
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci ohci.0: DA8xx OHCI
ohci ohci.0: new USB bus registered, assigned bus number 2
ohci ohci.0: irq 59, io mem 0x01e25000
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: DA8xx OHCI
usb usb2: Manufacturer: Linux 2.6.34-rc1 musb-hcd
usb usb2: SerialNumber: ohci.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
...
When boot 3.2.0, the kernel could not detect the device, only print message like this:
...
...
musb_hdrc: version 6.0, ?dma?, otg (peripheral+host)
Waiting for USB PHY clock good...
musb_hdrc musb_hdrc: USB OTG mode controller at fee00000 using PIO, IRQ 58
...
...
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci ohci.0: DA8xx OHCI
ohci ohci.0: new USB bus registered, assigned bus number 1
Waiting for USB PHY clock good...
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
...
Why 3.2.0 kernel couldn't detect the device?
support in kernel I selected as follow:
[*]Inventra Highspeed Dual Role Controller (TI, ADI, ...)
[*]Platform Glue Layer "DA8xx/OMAP-L1x"
[*]Disable DMA (always use PIO)
Another question is that, why we should disable dma here?
I notice this illustration for the config MUSB_PIO_ONLY:
Do not select 'n' here unless DMA support for your SOC or board is unavailable (or unstable). When DMA is enabled at compile time, you can still disable it at run time using the "use_dma=n" moduleparameter.
Appreciate any help.
-wang
Replies (1)
RE: can't detect USB2.0 device - Added by Michael Williamson over 11 years ago
Not sure why the 3.2 kernel is causing problems for you. It could be that you need to recompile our 3.2 kernel branch and run a menuconfig and make sure that support for the driver for that ethernet adaptor is enabled. If it's compiled as a module, the module support may not be installed.
Support for DMA for the OTG port was only recently added to our kernel tree (it wasn't included in the mainline in versions up to 3.8, it may still not be available). That's why the menu item is there. However, we've brought over some patches from a combination of folks at TI and MonteVista (sp) to include DMA support, so you should be able to disable the "Disable DMA" option.
I am sorry for the delay in response.
-Mike
