[opensuse-arm] Beaglebaord xM - USB is broken
Hi, I tried the latest beagle raw image (10.7) and USB is broken (so no Ethernet which is connected on USB internally, no USB stick). USB errors I get: (output of "dmesg | grep -i usb") ******************************************************************************** [ 0.092529] usbhs_omap: alias fck already exists [ 0.107055] usbcore: registered new interface driver usbfs [ 0.107177] usbcore: registered new interface driver hub [ 0.107391] usbcore: registered new device driver usb [ 0.171813] usbhs_omap usbhs_omap: xclk60mhsp1_ck set parentfailed error:-22 [ 0.171813] usbhs_omap usbhs_omap: xclk60mhsp2_ck set parentfailed error:-22 [ 1.666625] usbcore: registered new interface driver asix [ 1.672393] usbcore: registered new interface driver cdc_ether [ 1.678619] usbcore: registered new interface driver smsc95xx [ 1.684722] usbcore: registered new interface driver net1080 [ 1.690734] usbcore: registered new interface driver cdc_subset [ 1.697021] usbcore: registered new interface driver zaurus [ 1.702972] usbcore: registered new interface driver cdc_ncm [ 1.709228] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.716278] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.729431] drivers/usb/core/inode.c: creating file 'devices' [ 1.729461] drivers/usb/core/inode.c: creating file '001' [ 1.729766] ohci-omap3 ohci-omap3.0: new USB bus registered, assigned bus number 1 [ 1.821533] usb usb1: default language 0x0409 [ 1.821594] usb usb1: udev 1, busnum 1, minor = 0 [ 1.821594] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.828765] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.836334] usb usb1: Product: OMAP3 OHCI Host Controller [ 1.841979] usb usb1: Manufacturer: Linux 3.3.0-omap2plus+ ohci_hcd [ 1.848571] usb usb1: SerialNumber: ohci-omap3.0 [ 1.853973] usb usb1: usb_probe_device [ 1.854003] usb usb1: configuration #1 chosen from 1 choice [ 1.854034] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 1.854217] hub 1-0:1.0: usb_probe_interface [ 1.854217] hub 1-0:1.0: usb_probe_interface - got id [ 1.854248] hub 1-0:1.0: USB hub found [ 1.862457] hub 1-0:1.0: no power switching (usb 1.0) [ 1.862945] drivers/usb/core/inode.c: creating file '001' [ 1.863220] usbcore: registered new interface driver cdc_wdm [ 1.869201] Initializing USB Mass Storage driver... [ 1.874481] usbcore: registered new interface driver usb-storage [ 1.880767] USB Mass Storage support registered. [ 1.885742] usbcore: registered new interface driver libusual [ 1.891876] usbcore: registered new interface driver usbtest [ 2.173339] usbcore: registered new interface driver usbhid [ 2.179229] usbhid: USB HID core driver ******************************************************************************** Previous USB related dmesg (beagle raw image 10.6): ******************************************************************************** [ 0.074829] usbcore: registered new interface driver usbfs [ 0.074981] usbcore: registered new interface driver hub [ 0.075195] usbcore: registered new device driver usb [ 3.407592] usbcore: registered new interface driver asix [ 3.413391] usbcore: registered new interface driver cdc_ether [ 3.419616] usbcore: registered new interface driver smsc95xx [ 3.425720] usbcore: registered new interface driver net1080 [ 3.431701] usbcore: registered new interface driver cdc_subset [ 3.437988] usbcore: registered new interface driver zaurus [ 3.447296] usbcore: registered new interface driver cdc_ncm [ 3.453613] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 5.478576] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file 'devices' [ 5.478607] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '001' [ 5.479034] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1 [ 5.503753] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 [ 5.509948] usb usb1: default language 0x0409 [ 5.510009] usb usb1: udev 1, busnum 1, minor = 0 [ 5.510009] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 5.517150] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.524749] usb usb1: Product: OMAP-EHCI Host Controller [ 5.530334] usb usb1: Manufacturer: Linux 3.2.0-2-omap2plus ehci_hcd [ 5.536987] usb usb1: SerialNumber: ehci-omap.0 [ 5.542297] usb usb1: usb_probe_device [ 5.542297] usb usb1: configuration #1 chosen from 1 choice [ 5.542358] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 5.542541] hub 1-0:1.0: usb_probe_interface [ 5.542572] hub 1-0:1.0: usb_probe_interface - got id [ 5.542572] hub 1-0:1.0: USB hub found [ 5.551300] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '001' [ 5.581848] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 5.594787] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '002' [ 5.595123] ohci-omap3 ohci-omap3.0: new USB bus registered, assigned bus number 2 [ 5.685668] usb usb2: default language 0x0409 [ 5.685699] usb usb2: udev 1, busnum 2, minor = 128 [ 5.685729] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 5.692871] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.700439] usb usb2: Product: OMAP3 OHCI Host Controller [ 5.706115] usb usb2: Manufacturer: Linux 3.2.0-2-omap2plus ohci_hcd [ 5.712799] usb usb2: SerialNumber: ohci-omap3.0 [ 5.718170] usb usb2: usb_probe_device [ 5.718170] usb usb2: configuration #1 chosen from 1 choice [ 5.718231] usb usb2: adding 2-0:1.0 (config #1, interface 0) [ 5.718414] hub 2-0:1.0: usb_probe_interface [ 5.718414] hub 2-0:1.0: usb_probe_interface - got id [ 5.718444] hub 2-0:1.0: USB hub found [ 5.726654] hub 2-0:1.0: no power switching (usb 1.0) [ 5.727142] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '001' [ 5.727478] usbcore: registered new interface driver cdc_wdm [ 5.733459] Initializing USB Mass Storage driver... [ 5.738739] usbcore: registered new interface driver usb-storage [ 5.745056] USB Mass Storage support registered. [ 5.750030] usbcore: registered new interface driver libusual [ 5.756195] usbcore: registered new interface driver usbtest [ 5.902160] usb 1-2: new high-speed USB device number 2 using ehci-omap [ 6.061004] usbcore: registered new interface driver usbhid [ 6.066894] usbhid: USB HID core driver [ 6.142974] usb 1-2: udev 2, busnum 1, minor = 1 [ 6.143035] usb 1-2: New USB device found, idVendor=0424, idProduct=9514 [ 6.150115] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 6.158172] usb 1-2: usb_probe_device [ 6.158203] usb 1-2: configuration #1 chosen from 1 choice [ 6.158477] usb 1-2: adding 1-2:1.0 (config #1, interface 0) [ 6.158691] hub 1-2:1.0: usb_probe_interface [ 6.158691] hub 1-2:1.0: usb_probe_interface - got id [ 6.158721] hub 1-2:1.0: USB hub found [ 6.189483] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '002' [ 6.386688] usb 1-2: link qh256-0001/c24aa4e0 start 1 [1/0 us] [ 6.472656] usb 1-2.1: new high-speed USB device number 3 using ehci-omap [ 6.598022] usb 1-2.1: udev 3, busnum 1, minor = 2 [ 6.598052] usb 1-2.1: New USB device found, idVendor=0424, idProduct=ec00 [ 6.605316] usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 6.628997] usb 1-2.1: usb_probe_device [ 6.629028] usb 1-2.1: configuration #1 chosen from 1 choice [ 6.631408] usb 1-2.1: adding 1-2.1:1.0 (config #1, interface 0) [ 6.631622] smsc95xx 1-2.1:1.0: usb_probe_interface [ 6.631652] smsc95xx 1-2.1:1.0: usb_probe_interface - got id [ 6.721282] smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, c2:7a:cd:e3:cb:21 [ 6.746002] /home/abuild/rpmbuild/BUILD/kernel-omap2plus-3.2.0/linux-3.2/drivers/usb/core/inode.c: creating file '003' [ 152.115692] usb 1-2.1: link qh8-0001/d96d52e0 start 2 [1/0 us] ******************************************************************************** It seems there is no EHCI detection. It may be due to bad clock? Do you have this problem on Beagleboard (original, not xM) and on pandaboard also or is it a BB xM only problem? Any idea to solve the problem? Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 04/04/2012 15:52, Guillaume Gardet a écrit :
Hi, I tried the latest beagle raw image (10.7) and USB is broken (so no Ethernet which is connected on USB internally, no USB stick). [...]
It seems there is no EHCI detection. It may be due to bad clock? Do you have this problem on Beagleboard (original, not xM) and on pandaboard also or is it a BB xM only problem?
Any idea to solve the problem?
I tracked down the problem to a bad configuration of the reset pin of the USB hub (USB3320). The last update added the use of a common omap serial init which init ALL uarts whereas on the BB xM, we use one of uart pin for the reset of the USB3320. So USB3320 was always in reset mode. Moreover if CONFIG_USB_EHCI_MV is enabled, OMAP EHCI will not work anymore, so we need to disable it. Is it used by some supported OMAP2+ boards? I don't think so but I is always best to ask and double check! I will prepare two patches I will send to opensuse-kernel. Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 05/04/2012 13:17, Guillaume Gardet a écrit :
Hi,
Le 04/04/2012 15:52, Guillaume Gardet a écrit :
Hi, I tried the latest beagle raw image (10.7) and USB is broken (so no Ethernet which is connected on USB internally, no USB stick). [...]
It seems there is no EHCI detection. It may be due to bad clock? Do you have this problem on Beagleboard (original, not xM) and on pandaboard also or is it a BB xM only problem?
Any idea to solve the problem? I tracked down the problem to a bad configuration of the reset pin of the USB hub (USB3320). The last update added the use of a common omap serial init which init ALL uarts whereas on the BB xM, we use one of uart pin for the reset of the USB3320. So USB3320 was always in reset mode.
Moreover if CONFIG_USB_EHCI_MV is enabled, OMAP EHCI will not work anymore, so we need to disable it. Is it used by some supported OMAP2+ boards? I don't think so but I is always best to ask and double check!
I will prepare two patches I will send to opensuse-kernel.
Here are the patches sent to opensuse-kernel list: http://lists.opensuse.org/opensuse-kernel/2012-04/msg00011.html http://lists.opensuse.org/opensuse-kernel/2012-04/msg00012.html Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 05.04.2012, at 16:08, Guillaume Gardet wrote:
Le 05/04/2012 13:17, Guillaume Gardet a écrit :
Hi,
Le 04/04/2012 15:52, Guillaume Gardet a écrit :
Hi, I tried the latest beagle raw image (10.7) and USB is broken (so no Ethernet which is connected on USB internally, no USB stick). [...]
It seems there is no EHCI detection. It may be due to bad clock? Do you have this problem on Beagleboard (original, not xM) and on pandaboard also or is it a BB xM only problem?
Any idea to solve the problem? I tracked down the problem to a bad configuration of the reset pin of the USB hub (USB3320). The last update added the use of a common omap serial init which init ALL uarts whereas on the BB xM, we use one of uart pin for the reset of the USB3320. So USB3320 was always in reset mode.
Moreover if CONFIG_USB_EHCI_MV is enabled, OMAP EHCI will not work anymore, so we need to disable it. Is it used by some supported OMAP2+ boards? I don't think so but I is always best to ask and double check!
I will prepare two patches I will send to opensuse-kernel.
Here are the patches sent to opensuse-kernel list: http://lists.opensuse.org/opensuse-kernel/2012-04/msg00011.html http://lists.opensuse.org/opensuse-kernel/2012-04/msg00012.html
Awesome. Thanks a lot for tracking this down! If there are none yet, it might be a good idea to also file bugs on kernel.org against those issues, so people are aware of them :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 15/04/2012 12:03, Alexander Graf a écrit :
On 05.04.2012, at 16:08, Guillaume Gardet wrote:
Le 05/04/2012 13:17, Guillaume Gardet a écrit :
Hi,
Le 04/04/2012 15:52, Guillaume Gardet a écrit :
Hi, I tried the latest beagle raw image (10.7) and USB is broken (so no Ethernet which is connected on USB internally, no USB stick). [...]
It seems there is no EHCI detection. It may be due to bad clock? Do you have this problem on Beagleboard (original, not xM) and on pandaboard also or is it a BB xM only problem?
Any idea to solve the problem? I tracked down the problem to a bad configuration of the reset pin of the USB hub (USB3320). The last update added the use of a common omap serial init which init ALL uarts whereas on the BB xM, we use one of uart pin for the reset of the USB3320. So USB3320 was always in reset mode.
Moreover if CONFIG_USB_EHCI_MV is enabled, OMAP EHCI will not work anymore, so we need to disable it. Is it used by some supported OMAP2+ boards? I don't think so but I is always best to ask and double check!
I will prepare two patches I will send to opensuse-kernel. Here are the patches sent to opensuse-kernel list: http://lists.opensuse.org/opensuse-kernel/2012-04/msg00011.html http://lists.opensuse.org/opensuse-kernel/2012-04/msg00012.html
Awesome. Thanks a lot for tracking this down! If there are none yet, it might be a good idea to also file bugs on kernel.org against those issues, so people are aware of them :).
Done here: https://bugzilla.kernel.org/show_bug.cgi?id=43108 CONFIG_USB_EHCI_MV var seems to be no more available so that is fine. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 16.04.2012, at 12:04, Guillaume Gardet wrote:
Le 15/04/2012 12:03, Alexander Graf a écrit :
On 05.04.2012, at 16:08, Guillaume Gardet wrote:
Le 05/04/2012 13:17, Guillaume Gardet a écrit :
Hi,
Le 04/04/2012 15:52, Guillaume Gardet a écrit :
Hi, I tried the latest beagle raw image (10.7) and USB is broken (so no Ethernet which is connected on USB internally, no USB stick). [...]
It seems there is no EHCI detection. It may be due to bad clock? Do you have this problem on Beagleboard (original, not xM) and on pandaboard also or is it a BB xM only problem?
Any idea to solve the problem? I tracked down the problem to a bad configuration of the reset pin of the USB hub (USB3320). The last update added the use of a common omap serial init which init ALL uarts whereas on the BB xM, we use one of uart pin for the reset of the USB3320. So USB3320 was always in reset mode.
Moreover if CONFIG_USB_EHCI_MV is enabled, OMAP EHCI will not work anymore, so we need to disable it. Is it used by some supported OMAP2+ boards? I don't think so but I is always best to ask and double check!
I will prepare two patches I will send to opensuse-kernel. Here are the patches sent to opensuse-kernel list: http://lists.opensuse.org/opensuse-kernel/2012-04/msg00011.html http://lists.opensuse.org/opensuse-kernel/2012-04/msg00012.html
Awesome. Thanks a lot for tracking this down! If there are none yet, it might be a good idea to also file bugs on kernel.org against those issues, so people are aware of them :).
Done here: https://bugzilla.kernel.org/show_bug.cgi?id=43108
CONFIG_USB_EHCI_MV var seems to be no more available so that is fine.
Cool, thanks a lot! Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Alexander Graf
-
Guillaume Gardet