11:04 <ungeskriptet[m]> Marijn: If I use qcom,sync-dual-dsi, will it write dsi data to both hosts simultaneously without me having to make the panel driver write to dsi0 and dsi1? Do I understand this right?

12:19 <ungeskriptet[m]> Right now I have the driver write to dsi0 and dsi1 without qcom,sync-dual-dsi. For some reason it refuses to make use of dsi1 and is cramping the whole framebuffer into dsi0. Device is ZTE Axon 7 with msm8996 and my driver is here: https://github.com/ungeskriptet/linux/blob/msm8996/drivers/gpu/drm/panel/panel-samsung-s6e3ha3-lmdpdg.c

12:30 <konradybcio> lumag ^ 8996 and dual-dsi!

15:36 <Marijn[m]> ungeskriptet: registering both DSIs *should* in theory already make drm/msm use both hosts/intfs (but you can check/debug the topology-related codepaths). `sync-dsi` is another feature afaik

15:40 <ungeskriptet> ah okay, so writing data with mipi_dsi_dcs_write_seq to just one dsi host is enough on a dual dsi panel?

15:59 <Marijn[m]> ungeskriptet: as far as I recall there are no commands in a panel driver that need to be sent to both hosts. All commands are only intended for the panel, and the panel only listens to such commands from DSI0

15:59 <Marijn[m]> But I am not 100% confident in that

16:06 <konradybcio> ungeskriptet: the "easiest" would be to just debugbomb downstream and see what's getting sent

20:07 <ungeskriptet> konradybcio: Do you have a example on hand on how to implement this in downstream?

20:14 <aka_[m]> Hack some functions there and there?

20:15 <aka_[m]> There must be some mipi_dcs_write