2006/3/23, David Brownell <[EMAIL PROTECTED]>:
> On Monday 20 March 2006 1:50 am, Franck Bui-Huu wrote:
>
> > Same question for usb->pullup. Who is supposed to call this method ?
>
> The gadget driver, if it wants to support a mode where it's not always
> active. For example, maybe the kernel component needs to be configured
> from userspace -- opened by a daemon or something -- before it can be
> properly enumerated by a USB host. It's how "softconnect" mechanisms
> are packaged.
>
> In such a case, the driver probe() would call usb_gadget_disconnect()
> to change from the default state of "ready to enumerate". Then after
> it's configured it would call usb_gadget_connect() to allow the pullup
> to be used. (Those two calls wrap the ->pullup method.)
>
> This interacts with the VBUS detection, note. Normally the pullup would
> be disabled all the time until both (a) VBUS is provided, and (b) the
> driver indicates it's ready, with that softconnect flag in the "ok to
> connect" state. The application to OTG is straightforward. :)
>
OK, thanks for these information.
--
Franck
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
