On Tue, May 27, 2014 at 11:24:49PM +0900, Inki Dae wrote: > 2014-05-27 16:53 GMT+09:00 Thierry Reding <thierry.reding@xxxxxxxxx>: > > On Tue, May 27, 2014 at 08:28:52AM +0200, Andrzej Hajda wrote: > >> Hi Thierry, > >> > >> On 05/26/2014 03:41 PM, Thierry Reding wrote: > >> > On Wed, May 21, 2014 at 01:43:05PM +0900, YoungJun Cho wrote: > >> >> This patch adds DT bindings for s6e3fa0 panel. > >> >> The bindings describes panel resources, display timings and cpu mode timings. > >> >> > >> >> Signed-off-by: YoungJun Cho <yj44.cho@xxxxxxxxxxx> > >> >> Acked-by: Inki Dae <inki.dae@xxxxxxxxxxx> > >> >> Acked-by: Kyungmin Park <kyungmin.park@xxxxxxxxxxx> > >> >> --- > >> >> .../devicetree/bindings/panel/samsung,s6e3fa0.txt | 45 ++++++++++++++++++++ > >> >> 1 file changed, 45 insertions(+) > >> >> create mode 100644 Documentation/devicetree/bindings/panel/samsung,s6e3fa0.txt > >> > You're totally confusing me here. Half of this patch series is about > >> > adding i80 support to Exynos FIMD, and then you go and add what is > >> > apparently a DSI peripheral driver here that's supposed to be used by > >> > this new i80 support. Nothing I've been able to dig up indicates that > >> > i80 or DSI are in anyway related. > >> > >> FIMD can produce parallel RGB output or command mode in i80 style output > >> via parallel lines. > >> DSIM can accept parallel RGB stream in this case it produces MIPI DSI > >> video mode signal or it can accept i80 and in this case it translates it > >> to MIPI DSI command mode. > > > > Then the command mode timings aren't a property of the panel at all. > > Then the video mode timings aren't also a property of the panel. > > Which interface mipi and display controller should use would be > decided by lcd panel type: display controller can use i80 interface > based lcd panel, and also mipi controller can use i80 interface based > lcd panel. > In here, the only difference is that lcd panel receives packets, > which includes video data or command data, packed with mipi protocol > via lane lines or receives video data or command data via parallel > lines. > > And the below is LCD types, > RGB interface panel. > i80 interface panel. > MIPI based RGB interface panel. > MIPI based i80 interface panel. > > RGB interface also is called video mode, and i80 interface also is > called cpu mode. In case of omap SoC, it is also called Smart panel. > i80 interface is just one of LCD types. So I think this interface > timings should be handled by frameworks related to mode in same way as > RGB interface. LCD is a display technology, it has nothing to do with the interface. My point is that from Andrzej's description, and in fact from this patch series in general, the S6E3FA0 panel is a DSI panel. Associating timings that are i80 specific to it is therefore wrong. Consider for instance what would happen if somebody were to use the same panel on some other device (connected to a DSI controller). If you specify i80 timings for the panel then the new device won't know what to do with them because it expects DSI-related timings. Let me try to summarize the above to make sure we're all on the same page: - FIMD is a display controller that can be configured to either send RGB data or i80 data - DSIM takes either RGB as input and outputs DSI (video mode) or i80 as input and outputs DSI (command mode) In both cases the panel is connected to DSIM and it takes DSI as input, because it is a DSI panel (it doesn't understand RGB or i80). The panel needs to describe the properties of the DSI interface so that DSIM can be configured appropriately. DSIM in turn works as a bridge or encoder that converts RGB or i80 to DSI (video or command mode). So it makes no sense to describe the i80 timings for the panel because it has nothing to do with i80. Instead the DSIM is the hardware that needs to specify the i80 timings, so that FIMD can be configured to generate the timings that DSIM needs. Thierry
Attachment:
pgpJOepvkJOK9.pgp
Description: PGP signature
