Hi, On Tue, Dec 22, 2009 at 11:37:05PM +0100, ext Mike Frysinger wrote:
afaik, the current silicon out there (BF52x/BF54x) is based on MUSB 1.9. every anomaly/issue we've found so far is due to bugs in 1.9 and are fixed in 2.0, or due to how we hooked it up. unfortunately, the risk of upgrading the silicon in the current series of parts too great and so we're going to have to live with most of them.
if the dma problem is related to this IP revision, then it's easy: we do revision detection on run-time and use dma mode1 or mode0 based on that.
It'll require a bit of change on the code we wrote but it should be fairly simple to add another parameter to our start_dma() for the desired dma mode :-)
all future Blackfin parts will have the latest MUSB IP and the other connection fixes, so things should be peachy there.
you're in good position. Omap3430 uses rtl1.4 and 3630 uses (finally) 1.8.
as for anomaly lists, you can find a concise public mirror here: http://blackfin.uclinux.org/gf/project/bfin-docs/frs
good, will bookmark :D
if you're interested in even more back story on a specific anomaly, i can facilitate private information leakage in your direction ;).
you shouldn't say that on the list :-)
i can start a thread of "here's our crappy patches that work for us, please 2 help out" ... obvious understanding is that we dont get blasted on every one with "this is not how you do things!". we know that much already :P.
we can do this part off list if you want. I too am interested in getting musb in a good shape. We have our mode1 patches that works for us and they have been sent here for reference but no-one besides ajay and anand actually tested them so we only have them fully tested on omap3. I could (finally) found an n810 with development accessories available for testing on omap2. Let's see how that goes.
-- balbi -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
