Kevin Hilman wrote:
I was just trying to outline the large difference between 3.0 and 4.1 that warrants a new driver, so I'm not sure why TI people started to argue...
I think the pushback was on your statement that they're so different as to be incompatible through the only programming interface (musb_hdrc) that will use this.
So, if I understand this correctly, they are indeed quite different, but none of those differences are actually relevant to the programming interface actually used.
So, let's then support all MUSB DMA flavors with one bug driver -- cause the interface is all the same anyway.
So, that begs the original question:
Why can't the current version simply be extended instead of creating an entirely new driver?
I'm getting tired. Do I need to go into even more techical details on why I think extending an existing driver would be a bad idea? Or anybody of the people askinf this question will actually go as far as comparatively study the documentation and/or the source I've already presented (I think I now need to present the MUSB DMA driver too soon) to finally figure out the great difference in CPPI 3.0 and 4.1 approaches (and lack of any actual similarity between them).
Kevin
WBR, Sergei _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
