On Fri, 2011-09-16 at 17:53 +0100, Alan Cox wrote: > > I'm not sure a common interface to all of these different > > channels makes sense, but surely a DSI library and an aux channel > > library would fit nicely alongside the existing DDC library. > > DSI and the various other MIPI bits tend to be horribly panel and device > specific. In one sense yes its a standard with standard commands, > processes, queries etc, on the other a lot of stuff is oriented around > the 'its a fixed configuration unit we don't need to have queries' view. I think it's a bit more complex than that. True, there are MIPI standards, for the video there are DPI, DBI, DSI, and for the commands there is DCS. And, as you mentioned, many panels need custom initialization, or support only parts of the DCS, or have other quirks. However, I think the biggest thing to realize here is that DSI peripherals can be anything. It's not always so that you have a DSI bus and a single panel connected to it. You can have hubs, buffer chips, etc. We need DSI peripheral device drivers for those, a single "DSI output" driver cannot work. And this is also the most important thing in my original proposition. > There also tends to be a lot of vendor magic initialisation logic both > chipset and device dependant, and often 'plumbing dependant' on SoC While I have DSI experience with only one SoC, I do believe it'd be possible to create a DSI API that would allow us to have platform independent DSI peripheral drivers. Can you share any SoC side DSI peculiarities on Intel's SoCs? Tomi _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
