We are using imx6Q custom platform for our development which is based on sabresd platform.
We are using Linux 3.14.28_1.0.0-GA BSP for our development. But initially we used Linux 3.10.53_1.0.0-GA BSP.
From Linux 3.10.53_1.0.0-GA BSP, we have referred the below Linux kernel clock file.
We understood that the below function will set the LDB clock parent and the default LDB clock parent is "pll2_pfd0_352m".
But In Linux 3.14.28_1.0.0-GA BSP, we couldn't identify the parent clock of LDB clock. Please help us to understand
In our custom board, we are having LVDS0 800x480 display which is working with Linux 3.10.53_1.0.0-GA BSP.
The issue we are facing is,
In Linux 3.14.28_1.0.0-GA BSP, we have modified the corresponding lvds0 timing parameters in device tree. Now we are not getting the LVDS0 display.
But if we keep the clock frequency as 65Mhz (as used in ~/linux-imx/arch/arm/boot/dts/imx6qdl-sabresd.dtsi) then we are able to get the display.
Please note that, we have changed only clock frequency value and other timing parameters are kept for 800x480 resolution.
We believe, the LDB clock's parent is the problem for our above issue.
Please help us to resolve the issue.
I know you have seens this discussion:
I wonder if you have tried it out. I have been checking the code in 3.14.28 and it seems that it is not possible to change the parent clock the same way that in 3.10.53 (using a environment variable in u-boot).
You can also try the next in the clk-imx6q.c file:
I have not tried that and comparing with 3.10.53 the clock is set in a totally different way, not so sure if this due a restriction. But as I see the simpler way is to modify u-boot code the way is mentioned in the above discussion.
Thank you for your input.
In U-boot level, we are not supporting any display(including LVDS) and we are supporting the displays (including LVDS) in kernel level only.
As per your referred community link, the LVDS clock parent settings has to be added during the "setup_display".
But in our case(in our custom board file) "setup_display" function is not there.
Please suggest us.