> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of twebb > Sent: Wednesday, April 15, 2009 9:35 PM > To: linux-omap@xxxxxxxxxxxxxxx Mailing List > Subject: ehci problem on OMAP35xx > > I'm having issues getting USB up and going on HSUSB2/EHCI on > OMAP35xx-based hardware (very similar to beagle board). We're using > an SMSC3317 connected to HSUSB2, and in turn, the 3317 is connected to > an onboard hub - a SMSC USB2513. When the hub is removed from reset, > it appears that handshaking/chirping starts to happen between xcvr and > hub, but ends with the code announcing that it is "unable to enumerate > USB device on port 2". I'm guessing it's failing because we never see > PED set in the PORTSC_1 reg (and we are seeing PO=1 which doesn't make > any sense). Here is the PED (Port Enable/Disable) description: Ports can only be enabled by the host controller as a part of the reset and enable. Software cannot enable a port by writing a one to this field. "The host controller will only set this bit to a one when the reset sequence determines that the attached device is a high-speed device" So it seems there is some problem in detecting high speed signaling. PO (Port Ownership) description: System software uses this field to release ownership of the port to a selected Host controller (in the event that the attached device is not a high-speed device). Software writes a one to this bit when the attached device is not a high-speed device. "A one in this bit means that a companion host controller owns and controls the port." This is in same line as above. As there is problem in detecting high speed Signaling so the ownership is given to other host controller for the attached hub. Ajay > > I'm running a l-o git-based 2.6.28-omap1 kernel with > omap3_beagle_defconfig. Beagle board works fine (with patch to > ehci-omap.c and with CONFIG_USB_EHCI_HCD turned on), but my hardware > (with virtually same xcvr and and onboard hub) does not. > > Kind of new to this low level USB functionality, so a few questions... > 1. Any ideas why we'd see PORTSC_1[PO] = 1? > 2. Any suggestions on debugging basic connectivity between 35xx EHCI > controller and transceiver + hub? > > Thanks, > twebb > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
