I still don't get this "MIPI" thing. If it is so complicated to get an LCD working on an SoC, how the hell do all the gazillion Mobile Devices out there solve these issues? They pop out so fast, I can't imagine they have to deal alot with such issues at all.
" Does really every single one uses custom, "dirty" hacks just to get every LCD/SoC combo working? And if the OMAP5 has a (general?) bug that prevents it from communicating properly with an LCD, how do other OMAP5 mobile devices (if tere are any) get an image on screen? If they have solutions, it could help to just ask them for the workaround.
The problem is that "MIPI" is not a standard plug where both ends are certified. Yes, they are - but not completely. Only on the physical layers. It is like that you can plug in any USB device into a USB socket. But it does not work on your machine, because you don't find a compatible driver. But it may work on another one. So you try to write your own driver. Or you have a web browser and can't open some page (isn't http and html standardized?).Why do the gazillions devices appear to have less problems?
1. they don't use the latest and greatest display like we try
2. they have more people on their payroll to run around the world to knock at doors (so they may get answers faster than we do)
3. they are members of the MIPI organization (I think that costs >25000 USD membership fee per year) and therefore have a more direct contact
4. they have much more expensive equipment for analyzing circuits (e.g. a 16 channnel 5 GHz logic analyser or a special MIPI-DSI tester like one built by Agilent)
5. they buy reference designs where someone has done exactly the same challenging and time-consuming task we are doing (and reporting to the public) - but some months ago and behind the curtain - so it appears that it was easy for them
So they don't talk as much about issues, and may be faster because they spend more money on it.