From: ansaris <ansaris@iwavesystems.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: i.MX6Q - LDB clock's parent selection
Date: Thu, 21 May 2015 21:58:13 +0530 [thread overview]
Message-ID: <555E079D.8000909@iwavesystems.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2138 bytes --]
reply other threads:[~2015-05-21 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555E079D.8000909@iwavesystems.com \
--to=ansaris@iwavesystems.com \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.