11:03 <mwalle> kholk: what is that ovl_adaptor thingy?

11:11 <kholk> mwalle: mtk_drm_drv.c check the ddp_ext array for 8195

11:12 <kholk> also there's a kind of hack in mtk_drm_probe()

11:12 <kholk> /* Bringup ovl_adaptor */

11:12 <kholk> if (mtk_drm_find_mmsys_comp(private, DDP_COMPONENT_DRM_OVL_ADAPTOR)) {

11:12 <kholk> ovl_adaptor = platform_device_register_data(dev, "mediatek-disp-ovl-adaptor",

11:12 <kholk> (etc etc)

11:14 <kholk> oh wait

11:14 <kholk> I got confused for some reason

11:14 <kholk> and I have to re-reply to myself - it's not true, the OVL_ADAPTOR *is* accounted for, because I'm building the DDP path before checking if there's any ovl_adaptor component in the pipeline

11:17 <mwalle> kholk: but what is that (virtual) device for?

11:18 <kholk> ah, opens direct paths between display output, ET-HDR block and MDP RDMA blocks

11:18 <kholk> so that:

11:19 <kholk> 1. you can get HDR 10bit streams to the display; and

11:19 <kholk> 2. you can get a direct MDP3 -> display stream

11:19 <kholk> :-)