On Fri, Nov 28, 2008 at 09:25:26AM -0800, David Brownell wrote: > So the answer for you is obviously to have something > other than the musb driver hold your otg_transceiver > driver. Like ... an isp1504.c I2C driver, which will > eventually move to drivers/usb/otg and which calls > the otg_set_transceiver() utility. There's one problem here. If this is similar to isp1704, it doesn't have a control interface. And the only way to talk to the transceiver is via ULPI. I have patches that add musb_ulpi_read/write functions using the musb ulpi wrapper. BUT, isp1x04 is pretty much autonomous, there isn't much you can/have to do, the problem with them is that they don't have an interrupt line with omap (afaict) so it's difficult to be sure when we have to e.g. switch to host mode unless we keep polling the INT_STS register for changes. That's too bad. But other than that, I agree with you completely. I won't queue up patches adding such kind of ifdefs. -- balbi -- 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
