Hi InKi, 2010/7/2 InKi Dae <inki.dae@xxxxxxxxxxx>: > this patch addes MIPI-DSI Driver. > > to use this driver, some structures below should be added to machine > specific file. A quick question. I'm having difficulty understanding the larger picture here. There's the MIPI-DSI host controller driver (which I think is what this patch is) which is specific to this platform. Then there's the MIPI-DSI LCD panels which are supposed to be fully platform independent, right? and would thus ideally have a platform independent MIPI-DSI client driver? Would I be correct in saying this patch below does not provide such an abstraction and so structures that would be necessary for such a display driver (eg: struct mipi_lcd_driver ) appear to be declared in the samsung platform specific files. In other words, if we wanted to support a particular MIPI-DSI LCD panel, it would require a client driver that is tied intimately to this platform? Could you point us to an example mipi-dsi client driver that is using the patch you provided? ie: something that is calling s5p_dsim_register_lcd_driver. That would help us understand the abstraction that is being made here. Thanks, jaya -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html