On Tue, Aug 18, 2009 at 01:46:52PM +0400, Sergei Shtylyov wrote: > Daniel Mack wrote: > >> I don't have the full ULPI specification unfortunately, > > So I thought. Here it is: > > http://www.smsc.com/media/Downloads_Public/usb/ulpi_v1_1.zip Thanks. >> so I can't >> really tell. But as far as I understand, especially these registers are >> outside the ULPI standard and hence they are device specific. >> > > No, they are not -- see the spec... Ok, agreed, I wasn't aware of that. I'll rename the whole thing to ULPI generic as you suggested earlier. >> That made it work for many boards. What would your proposal be? Add a >> parameter to the API to decide that? >> > > No, probably that should be initialized in the init() method or in > board specific code. If that is done from board specific code, there needs to be a function in the API to actually do the register access. That's what I mean. So it looks like we need some more functions to have more fine-grained control of what the transceiver does. Daniel -- 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
