Hi Inki, On 02/28/2014 03:28 AM, Inki Dae wrote: (...) > > Andrzej Hajda from our team is already working on addressing remaining > issues with Sean's series, including fixing removed parallel display > support. Earlier this month he sent a series restoring support for DSI > panels: http://thread.gmane.org/gmane. > > Already merged to internal kernel for test. > >> linux.kernel.samsung-soc/27044 . Now he's also trying to make the design >> more modular. He will give you more information on Monday, as he's on >> holiday for next two days. Thanks Tomasz for pointing it out. I try to properly restore parallel panel support. I have come to the conclusion that the most natural way is to implement crtc/encoder/connector in FIMD, as the FIMD directly produces parallel RGB stream (or I80 in command mode). I think implementing crtc/encoder/connector in FIMD in case of DSI and eDP panel is also more natural. In such case I would convert DSIM, eDP and ptn3460 to drm_panel framework similarly as I already did for TC358764 DSI/LVDS bridge.
Here are different scenarios of HW pipelines: 1. Parallel panel: FIMD ---> Parallel Panel 2. DSI panel: FIMD ---> DSIM ---> DSI Panel 3. Arndale: FIMD ---> DSIM ---> DSI/LVDS bridge ---> LVDS panel 4. Snow: FIMD ---> eDP ---> eDP/LVDS bridge ---> LVDS panel 5. In case mobile image enhancer(MIE) will be used pipeline can be extended to: FIMD ---> MIE ---> DSIM ---> ..... or FIMD ---> MIE ---> eDP ---> ..... Pros of implementing all drm components (crtc,encoder,connector) in FIMD, and using drm_panel framework for panels, DSIM, eDP and external bridges: - it is natural, FIMD produces already encoded stream, DSIM and eDP are just optional converters, - easy to extend, adding/removing image processors or bridges will require only changing video paths in DTS (in addition to adding device nodes), - consistency. What do you think about it? Anyway the patch adding parallel support with current design should be ready soon. Regards Andrzej