Hi, On Mon, Dec 10, 2012 at 11:48:51AM +0200, Roger Quadros wrote: > >>> (or in appropriate order if the above isn't) > >>> That way insmod/rmmod'ing the USB3320C driver would power-up/down the > >>> whole subsystem. > >> > >> Yes, this is where we can think of a generic PHY driver to make sure thy > >> PHY has necessary resources enabled. In the Panda case it would be the > >> PHY clock and RESET gpio. > >> > > I wonder if ehci-omap should assume, besides regulator, a clock might > > also be need to setup for the transceiver chip. > > Maybe "usbhs_bdata" in board-omap4panda.c should have > > .reset_gpio_port[0] = GPIO_HUB_NRESET ? > > > > Just like the regulator, reset_gpio_port has nothing to do with OMAP > EHCI. So we would want to get rid of that too from the OMAP USB driver. +1 to that. That's a requirement from the LAN95xx hub controller, not OMAP EHCI ;-) -- balbi
Attachment:
signature.asc
Description: Digital signature
