Hi Linus, Maybe a little unrelated to this patch but this IP is also used on the MStar/SigmaStar chips (albeit only the host (FUSBH200) part that used to have its own driver that got removed at some point...) and I noticed this when rebasing my tree and hitting conflicts with your recent changes... For what it's worth I could not get this driver to function correctly with UVC cameras etc and was fed up with hacking it apart to try to get it to work when it's mostly a copy/paste of an old copy of the common EHCI driver. So I added some extra quirks to the common EHCI driver to allow it to run this IP too and deleted the custom driver in my tree (hence the conflicts..). I'm not sure how using the common EHCI driver works with the OTG part but if it's possible to make that work maybe my way is a better solution than trying to maintain this driver? Cheers, Daniel
