On Monday 02 January 2006 3:24 pm, Richard Purdie wrote: > > usb_ep_autoconfig can then optionally call a driver provided > configuration function (ops->ep_alloc) instead of using its > autoconfigure logic. This shouldn't change any existing behaviour and > reading the comments in that function, it looks like such a function was > already envisaged?
Various controllers have adopted that "dynamic fifo config" model; examples include omap_udc (see the comments at the top of that driver!), some silicon derived from the Mentor IP, and ISTR the au1xx_udc. I'm sure that sort of model would find decent use. > 4. Perhaps some kind of interfacing with the pxa27x ohci_hcd (is there > some similar code for the omap udc?) I presume you mean for OTG... You'd need something more like a Mainstone than a Zaurus to test that code. :) OMAP did that coordination through a separate OTG driver; the isp1301_omap driver. I understand TI has an updated version that factors the functionality better, for use with other kinds of transceiver. If you started with a Mainstone you'd at least be able to use the isp1301 parts of that as a model. But I don't think that's the final word on doing that sort of synchronization smoothly. Especially with regards to the power management stuff ... e.g. clocking everyting out until some ID or VBUS interrupt arrives, and only then gating the relvant PLLs and firing up the charge pump or whatever. - Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
