> > > Later on, it would be nice to let HCDs to handle all otg stuff by using > > > those function pointers in struct otg_transceiver. > > > > It's not clear what you mean by that, since HCDs can already call > > the relevant host side functions. > > At least in musb driver, we're not using otg_trasnceiver's function > pointers afaik. Sorry if I didn't make me clear, reading again it really > sounds awful :-p > > What I mean is setting correct functions in tusb6010.c so we can call it > from musb_core.c as xceiv->set_host() for example. I'm not sure I'd worry about set_host() and set_peripheral() methods; musb_hdrc can just set those fields directly. Those methods are more important when the host and peripheral sides involve two different controllers that initialize independently (and in either order), as needed by OTG on OMAP1 systems (and OMAP2 ones using the older hardware). With musb_hdrc there isn't really a separate OTG driver, so it doesn't have as much need for one place to coordinate things. - Dave - 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
