From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: imx: clk-imx6ul: allow lcdif_pre_sel to change parent rate
Date: Thu, 2 Nov 2017 00:25:50 -0700 [thread overview]
Message-ID: <20171102072550.GQ30645@codeaurora.org> (raw)
In-Reply-To: <20171012132935.3508-1-p.zabel@pengutronix.de>
On 10/12, Philipp Zabel wrote:
> Allowing the lcdif_pre_sel to propagate rate changes to its parent PLL
> allows more fine grained control over the LCDIF pixel clock rate.
>
> For example, the Innovision AT043TN24 LCD panel described in the
> imx6ul-14x14-evk device tree requires a 9 MHz pixel clock.
> Before this patch, the lcdif_pre_sel clock rate is fixed, and just
> setting the lcdif_pred and lcdif_podf dividers only allows to get as
> close as about 8.44 MHz:
>
> pll3 1 1 480000000 0 0
> pll3_bypass 1 1 480000000 0 0
> pll3_usb_otg 1 1 480000000 0 0
> pll3_pfd1_540m 1 1 540000000 0 0
> lcdif_pre_sel 1 1 540000000 0 0
> lcdif_pred 1 1 67500000 0 0
> lcdif_podf 1 1 8437500 0 0
> lcdif_pix 1 1 8437500 0 0
>
> Once lcdif_pre_sel is allowed to propagate rate requests to its parent,
> the actual pixel clock matches the requested value:
>
> pll3 1 1 480000000 0 0
> pll3_bypass 1 1 480000000 0 0
> pll3_usb_otg 1 1 480000000 0 0
> pll3_pfd1_540m 1 1 288000000 0 0
> lcdif_pre_sel 1 1 288000000 0 0
> lcdif_pred 1 1 36000000 0 0
> lcdif_podf 1 1 9000000 0 0
> lcdif_pix 1 1 9000000 0 0
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-11-02 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 13:29 [PATCH] clk: imx: clk-imx6ul: allow lcdif_pre_sel to change parent rate Philipp Zabel
2017-10-12 13:39 ` Fabio Estevam
2017-11-02 7:25 ` Stephen Boyd [this message]
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=20171102072550.GQ30645@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).