From: Fabio Estevam <festevam@gmail.com>
To: rafael.j.wysocki@intel.com
Cc: viresh.kumar@linaro.org, ping.bai@nxp.com, shawnguo@kernel.org,
kernel@pengutronix.de, linux-pm@vger.kernel.org,
Fabio Estevam <fabio.estevam@nxp.com>, <stable@vger.kernel.org>
Subject: [PATCH] cpufreq: imx6: Fix the secondary_sel_clk clock string
Date: Thu, 19 May 2016 23:59:47 -0300 [thread overview]
Message-ID: <1463713188-6896-1-git-send-email-festevam@gmail.com> (raw)
From: Fabio Estevam <fabio.estevam@nxp.com>
Commit a35fc5a33b62a6 ("cpufreq: imx: update the clock switch flow to
support imx6ul") introduced the 'secondary_sel_clk' clock, which is
specific for the i.mx6ul case, but used the wrong clock string inside
the clk_get() function.
Use the correct clock string: "secondary_sel_clk".
This fixes a kernel crash after running the 'reboot' command on a
mx6ul.
Fixes: a35fc5a33b62a6 ("cpufreq: imx: update the clock switch flow to support imx6ul")
Cc: <stable@vger.kernel.org> # 4.4.x
Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
---
drivers/cpufreq/imx6q-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/imx6q-cpufreq.c b/drivers/cpufreq/imx6q-cpufreq.c
index ef1fa81..00b481e 100644
--- a/drivers/cpufreq/imx6q-cpufreq.c
+++ b/drivers/cpufreq/imx6q-cpufreq.c
@@ -212,7 +212,7 @@ static int imx6q_cpufreq_probe(struct platform_device *pdev)
if (of_machine_is_compatible("fsl,imx6ul")) {
pll2_bus_clk = clk_get(cpu_dev, "pll2_bus");
- secondary_sel_clk = clk_get(cpu_dev, "secondary_sel");
+ secondary_sel_clk = clk_get(cpu_dev, "secondary_sel_clk");
if (IS_ERR(pll2_bus_clk) || IS_ERR(secondary_sel_clk)) {
dev_err(cpu_dev, "failed to get clocks specific to imx6ul\n");
ret = -ENOENT;
--
1.9.1
next reply other threads:[~2016-05-20 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 2:59 Fabio Estevam [this message]
2016-05-20 3:03 ` [PATCH] cpufreq: imx6: Fix the secondary_sel_clk clock string Viresh Kumar
2016-05-20 3:09 ` Fabio Estevam
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=1463713188-6896-1-git-send-email-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-pm@vger.kernel.org \
--cc=ping.bai@nxp.com \
--cc=rafael.j.wysocki@intel.com \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=viresh.kumar@linaro.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