On Mon, 19 Sep 2011 09:33:34 +0300, Tomi Valkeinen <tomi.valkeinen@xxxxxx> wrote: > 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. So DSI is more like i2c than the DisplayPort aux channel or DDC. That seems fine; you can create a DSI infrastructure like the i2c infrastructure and then just have your display drivers use it to talk to the panel. We might eventually end up with some shared DRM code to deal with common DSI functions for display devices, like the EDID code today, but that doesn't need to happen before you can write your first DSI-using display driver. -- keith.packard@xxxxxxxxx
Attachment:
pgpgxWdhvxM_q.pgp
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
