>-----Original Message----- >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Bill >Gatliff >Sent: Friday, December 18, 2009 1:11 PM >To: Gadiyar, Anand >Cc: linux-omap@xxxxxxxxxxxxxxx; beagleboard@xxxxxxxxxxxxxxxx >Subject: Re: Anyone using an ISP1505? > <snip> > >> If it's with the EHCI controller, you need to take care of a couple of >> issues on the board (due to the input clocking mode used in the OMAP3). >> > >Can you elaborate? Thanks! > For omap-ehci, the OMAP feeds in the 60Mhz clock to the PHY(1505 in your case). This is the input clocking mode of phy. It looks like the PHY state machine requires sometime to stabilize and lock into this 60Mhz clock input and this is done with a GPIO form omap. In ehci_hcd_omap_platform_data, Typically boards have . phy_reset = true . reset_gpio_port[0] = GPIO going to phy reset pin On your board you need to find, if there is a GPIO hooked from omap to PHY. And the GPIO behavior is decided by the PHY pin property ( whether its active high/low and whether its chipselect or reset of phy). By default the code assumes that the GPIO is connected to RESET pin: going 0 while the 60mhz clock input stabilizes and then once done, make it 1. So find out what GPIO from omap is connected to phy to control the phy. -- 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
