From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 8AB39E009C5; Thu, 21 May 2015 09:28:32 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, T_FROM_12LTRDOM autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.0 T_FROM_12LTRDOM From a 12-letter domain Received: from sip2-98.nexcess.net (iwavesystems.com [207.32.180.10]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3491EE009B6 for ; Thu, 21 May 2015 09:28:31 -0700 (PDT) Received: (qmail 15109 invoked by uid 108); 21 May 2015 12:28:30 -0400 Received: from unknown (HELO ?192.168.2.104?) (124.124.219.234) by sip2-98.nexcess.net with SMTP; 21 May 2015 12:28:30 -0400 Message-ID: <555E079D.8000909@iwavesystems.com> Date: Thu, 21 May 2015 21:58:13 +0530 From: ansaris User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "meta-freescale@yoctoproject.org" Subject: i.MX6Q - LDB clock's parent selection X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 16:28:32 -0000 Content-Type: multipart/alternative; boundary="------------050700090007070803020104" --------------050700090007070803020104 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi, 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. ~/linux-imx/arch/arm/mach-imx/clk-imx6q.c We understood that the below function will set the LDB clock parent and the default LDB clock parent is "pll2_pfd0_352m". "init_ldb_clks" But In Linux 3.14.28_1.0.0-GA BSP, we couldn't identify the parent clock of LDB(LDB_DI0_SEL) 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. Thank You, Regards, Ansari --------------050700090007070803020104 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Hi,

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.
~/linux-imx/arch/arm/mach-imx/clk-imx6q.c
We understood that the below function will set the LDB clock parent and the default LDB clock parent is "pll2_pfd0_352m".
"init_ldb_clks"

But In Linux 3.14.28_1.0.0-GA BSP, we couldn't identify the parent clock of LDB(LDB_DI0_SEL) 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.

Thank You,
Regards,
Ansari --------------050700090007070803020104--