From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: imx6q: Fix imx6sx low frequency support
Date: Mon, 28 Aug 2017 14:07:51 +0200 [thread overview]
Message-ID: <1503922071.2347.0.camel@pengutronix.de> (raw)
In-Reply-To: <4304e578a343c9acaed46b7e205d49bb63323f80.1503918257.git.leonard.crestez@nxp.com>
Am Montag, den 28.08.2017, 14:05 +0300 schrieb Leonard Crestez:
> This patch contains the minimal changes required to support imx6sx OPP
> of 198 Mhz. Without this patch cpufreq still reports success but the
> frequency is not changed, the "arm" clock will still be at 396000000 in
> clk_summary.
>
> In order to do this PLL1 needs to be still kept enabled while changing
> the ARM clock. This is a hardware requirement: when ARM_PODF is changed
> in CCM we need to check the busy bit of CCM_CDHIPR bit 16 arm_podf_busy,
> and this bit is sync with PLL1 clock, so if PLL1 NOT enabled, this
> bit will never get clear.
>
> Keep pll1_sys explicitly enabled until after the rate is change to deal
> with this. Otherwise from the clk framework perspective pll1_sys is
> unused and gets turned off.
>
> Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> Changes since v1:
> - Link: https://lkml.org/lkml/2017/7/19/302
> - Only keep pll1_sys enabled until after ARM rate is changed.
> - Incorporate more elaborate explanation from Anson
> - Do not add new clocks or bypass PLL1. Just let it get disabled.
>
> drivers/cpufreq/imx6q-cpufreq.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/cpufreq/imx6q-cpufreq.c b/drivers/cpufreq/imx6q-cpufreq.c
> index b6edd3c..14466a9 100644
> --- a/drivers/cpufreq/imx6q-cpufreq.c
> +++ b/drivers/cpufreq/imx6q-cpufreq.c
> @@ -47,6 +47,7 @@ static int imx6q_set_target(struct cpufreq_policy *policy, unsigned int index)
> struct dev_pm_opp *opp;
> unsigned long freq_hz, volt, volt_old;
> unsigned int old_freq, new_freq;
> + bool pll1_sys_temp_enabled = false;
> int ret;
>
> new_freq = freq_table[index].frequency;
> @@ -124,6 +125,10 @@ static int imx6q_set_target(struct cpufreq_policy *policy, unsigned int index)
> if (freq_hz > clk_get_rate(pll2_pfd2_396m_clk)) {
> clk_set_rate(pll1_sys_clk, new_freq * 1000);
> clk_set_parent(pll1_sw_clk, pll1_sys_clk);
> + } else {
> + /* pll1_sys needs to be enabled for divider rate change to work. */
> + pll1_sys_temp_enabled = true;
> + clk_prepare_enable(pll1_sys_clk);
> }
> }
>
> @@ -135,6 +140,10 @@ static int imx6q_set_target(struct cpufreq_policy *policy, unsigned int index)
> return ret;
> }
>
> + /* PLL1 is only needed until after ARM-PODF is set. */
> + if (pll1_sys_temp_enabled)
> + clk_disable_unprepare(pll1_sys_clk);
> +
> /* scaling down? scale voltage after frequency */
> if (new_freq < old_freq) {
> ret = regulator_set_voltage_tol(arm_reg, volt, 0);
next prev parent reply other threads:[~2017-08-28 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 11:05 [PATCH] cpufreq: imx6q: Fix imx6sx low frequency support Leonard Crestez
2017-08-28 12:07 ` Lucas Stach [this message]
2017-08-30 23:31 ` Rafael J. Wysocki
2017-08-30 15:26 ` A.s. Dong
-- strict thread matches above, loose matches on Subject: below --
2017-07-19 9:54 Leonard Crestez
2017-07-19 10:28 ` Lucas Stach
2017-07-20 1:16 ` Anson Huang
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=1503922071.2347.0.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--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).