On Wed, Jan 12, 2011 at 10:30:59PM +0800, loody wrote: > hi: > 2011/1/12 Felipe Balbi <balbi@xxxxxx>: > > Hi, > > > > On Wed, Jan 12, 2011 at 03:16:27PM +0100, Johannes Reisinger wrote: > >> >Are they both designed for OTG or only host or only device chip? > >> > >> we will have two interfaces, one for host and the other one for device > >> operation. To replace them both with only one OTG is not an option, > >> because we have use-cases where we need both interfaces concurrently. > > > > So you have an OTG transceiver to switch operation between host and > > device, right ? > > > > Considering that, is the transceiver ULPI compliant ? if it is, then you > > can probably use the nop-xceiv driver for that. But you sure need a > > driver. > after google the ULPI, I found it is a new interface to decrease the > original pin# of UTMI. > But if I remember correctly, usb driver usually will not touch this > part, since it is wrapped in host/device controller, right? You have to check how transceiver talks to your CPU, do you have e.g. I2C to control the PHY or is it just a "plug&play" PHY ? Meaning there's no need to CPU to touch it ? -- balbi -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
