On 2 March 2012 15:23, Heiko Stübner <<a href="mailto:heiko@sntech.de">heiko@sntech.de</a>> wrote: <div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Am Freitag, 17. Februar 2012, 00:25:51 schrieb Laurent Pinchart: [...] <div class="im">> For DSI, a possible abstraction level would be a DCS (Display Command > Set) bus. Panels and/or HDMI-on-DSI transmitter drivers would be > implemented as DCS drivers. > > Action points: > - Marcus to work on a proposal for DCS-based panels (with Tomi Valkeinen > and Morimoto-san). </div>It would also be interesting to see something similar for MIPI-DBI (type B for me) [aka rfbi on omap], as most epaper displays use this to transmit data and currently use half-baked interfaces. So hopefully I'll be able to follow the discussion and can then try to convert your findings to the dbi case. Heiko </blockquote></div> The idea is to abstract the DSI/DBI-2 type of transport and focus on the DCS command set level. The driver should be able to select between DBI and DSI by providing some "struct dcs_device { ifc = DSI/DBI2, ... }" data to the DCS bus. Something like a stripped version of <a href="http://www.igloocommunity.org/gitweb/?p=kernel/igloo-kernel.git;a=blob;f=include/video/mcde.h#l113">www.igloocommunity.org/gitweb/?p=kernel/igloo-kernel.git;a=blob;f=include/video/mcde.h#l113</a>, but for DBI/DSI only. /BR /Marcus