Hi Richard, On Wed, 30 Jan 2008 09:30:14 -0600, "Woodruff, Richard" <r-woodruff2@xxxxxx> wrote: >> > Paul confirmed that there are still issues with clock framework and >> DPLL5 >> > enabling. >> > So not to have a dependency on Clock framework, I use the attached >> > ALL-CLOCK-ENABLE patch. >> > You can do the same for now. >> >> Thanks, >> >> This will help me a lot. In any case, USBHOST_L4_ICLK has changed from >> ES1.0 to ES2.0, you can confirm in the TRMs. >> I'm trying to find a way to make it work on current omap. > > Felipe, > > Yes, on ES2 there has been major change with respect to USB. The old FS > block has been removed completely. It is replaced with a multi-port > EHCI (host only). The MUSB single (otg/host/cliet) port is still there. > Connectivity around this (options via pin mux, tll or not is somewhat > involved). > > The PRCM with respect to these guys has changed. It is documented in > the ES2 TRM. There is a special difference TRM between ES1 and ES2 > which fully highlights this. Through your Nokia affiliations you should > have access to these. We have a public TRM in the works, not sure when > that shows up. Probably in a few months. > > ** You should have access to our TI kernel code drop, snapshots are on > our website, and up to date versions are there in CDP. These versions > are fully working for USB. The underlying PRCM details and changes are > fully coded. > > You can use that for reference. If you need this in a hurry or want to > spend the time, all the information in code form is already there to > make it work and has been since ES2 appeared (at the prcm anyway). > > * To help understanding, we have an internal tree based on 2.6.22 where > everything works. As development was done in advance of open source for > people who needed it last year, the implementation is different from > what is omap-git present, but it's a related elder cousin. We also have > a tree which is in sync with latest omap-git, however, this tree > everything is not yet fully forward ported. At any rate both are > available to you I believe, so you should be enabled to make it work. > > Regards, > Richard W. Thanks for the answer. This clarified a bit some missing bits I had :-p I'll get your code from 2.6.22 and try to make it work internally. -- Best Regards, Felipe Balbi http://felipebalbi.com me@xxxxxxxxxxxxxxx - 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
