On Mon, Nov 03, 2008 at 08:33:26PM +0530, Ajay Kumar Gupta wrote: > I agree but currently in host only mode after disconnect vbus is switched off and > there is no way to switch it on. Now if we connect other device it doesn't work > as musb is dead. Hmm... sounds odd. I haven't been using musb as host only for a long time, last time I think was on n800 time :-p Anyways, enable debugging and echo 8 > /sys/modules/musb_hdrc/parameters/debug and see if you get any event upon cable attach. You should have an id pin grounded event, then that should trigger vbus on > > I believe that we should have a "session" entry on sysfs and upon cable > > connection, one side switches to a_idle and the other stays in b_idle. > > The device that writes to session (echo 1 > session) will become host > > (either b_host or a_host, meaning that hnp would also trigger based on > > that). > > This is the case of OTG build but what if we configure for only host mode ? All > OTG related stuff shouldn't be there in host only mode right ? most likely, yeah. But still, it would appear more like an embedded host than a real host controller. Which means we can still switch off vbus when not in use, I suppose. -- 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
