Sorry, but I think that's not correct... Indeed, you can use fsl,imx-parallel-display, but then you're using the opensource/drm mainline way of addressing the ipu, and not the freescale proprietary way.
fbdev/mxc/ldb.c is still providing the freescale proprietary way of configuring a mxcfb device fbdev/mxc/mxc_lcdif.c is also using the imx6q/dl ipu for it's parallel lcd display, only it is gone since kernel 4.9-imx, which is strange as even the imx6qdl-sabresd.dtsi in the 5.4-2.0.x-imx branch is referring to it.. The way it is now, nothing is handling the compatible "fsl,lcd" in the whole 4.9-imx or 5.4-imx kernels, which is wrong according to me. I think it is just forgotten in a previous merge... That would mean that commit https://github.com/Freescale/linux-fslc/commit/afcde9250592b07f165e2f66217726e26ac54e7c ( https://github.com/Freescale/linux-fslc/commit/afcde9250592b07f165e2f66217726e26ac54e7c ) was incomplete. As a test, I just put back the mxc_lcdif.c, and now my display is working perfectly again with configured devicetree: lcd@0 { compatible = "fsl,lcd"; ipu_id = <0>; disp_id = <0>; default_ifmt = "RGB24"; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_ipu1>; status = "okay"; }; mxcfb1: fb@0 { compatible = "fsl,mxc_sdc_fb"; disp_dev = "lcd"; interface_pix_fmt = "RGB24"; mode_str ="CLAA-WVGA"; default_bpp = <16>; int_clk = <0>; late_init = <0>; status = "disabled"; }; If you think I am correct, I can create a pullrequest...
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#24386): https://lists.yoctoproject.org/g/meta-freescale/message/24386 Mute This Topic: https://lists.yoctoproject.org/mt/76164765/21656 Group Owner: meta-freescale+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
