From: Mike Turquette <mturquette@ti.com>
To: linux@arm.linux.org.uk
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
khilman@ti.com, tony@atomide.com, b-cousson@ti.com,
rnayak@ti.com, jeremy.kerr@canonical.com, paul@pwsan.com,
broonie@opensource.wolfsonmicro.com, tglx@linutronix.de,
linus.walleij@stericsson.com, amit.kucheria@linaro.org,
dsaxena@linaro.org, patches@linaro.org,
linaro-dev@lists.linaro.org, grant.likely@secretlab.ca,
sboyd@quicinc.com, shawn.guo@freescale.com, skannan@quicinc.com,
magnus.damm@gmail.com, arnd.bergmann@linaro.org,
eric.miao@linaro.org, richard.zhao@linaro.org,
mturquette@linaro.org, mturquette@ti.com, andrew@lunn.ch
Subject: [PATCH 4/6] HACK: cpufreq: omap: change mpu_clk's rate
Date: Tue, 13 Dec 2011 20:31:26 -0800 [thread overview]
Message-ID: <1323837088-2469-5-git-send-email-mturquette@ti.com> (raw)
In-Reply-To: <1323837088-2469-1-git-send-email-mturquette@ti.com>
As a proof of concept, change OMAP's cpufreq driver to use mpu_clk in
place of directly using the DPLL. This better reflects reality as there
are some functional clks between the ARM IP and the PLL.
To make this work mpu_clk uses the new .round_rate function
omap2_passthrough_round_rate, which simplies passing up a rate change
request to the parent.
Not for merging, just to get discussion going around the common clk
patches and future OMAP adaptations.
Not-signed-off-by: Mike Turquette <mturquette@ti.com>
---
drivers/cpufreq/omap-cpufreq.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/cpufreq/omap-cpufreq.c b/drivers/cpufreq/omap-cpufreq.c
index 5d04c57..45cb7f9 100644
--- a/drivers/cpufreq/omap-cpufreq.c
+++ b/drivers/cpufreq/omap-cpufreq.c
@@ -247,7 +247,7 @@ static int __init omap_cpufreq_init(void)
else if (cpu_is_omap34xx())
mpu_clk_name = "dpll1_ck";
else if (cpu_is_omap44xx())
- mpu_clk_name = "dpll_mpu_ck";
+ mpu_clk_name = "mpu_clk";
if (!mpu_clk_name) {
pr_err("%s: unsupported Silicon?\n", __func__);
--
1.7.5.4
next prev parent reply other threads:[~2011-12-14 4:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 4:31 [PATCH 0/6] HACK: OMAP: testing common clk features Mike Turquette
2011-12-14 4:31 ` [PATCH 1/6] HACK: omap: opp: add fake 400MHz OPP to bypass MPU Mike Turquette
2011-12-14 4:31 ` [PATCH 2/6] omap: clk: .round_rate for propagating to parents Mike Turquette
2011-12-14 4:31 ` [PATCH 3/6] HACK: omap: clk: add mpu_periphclk clk node Mike Turquette
2011-12-14 4:31 ` Mike Turquette [this message]
2011-12-14 4:31 ` [PATCH 5/6] smp_twd: Reconfigure clockevents after cpufreq change Mike Turquette
2011-12-14 4:31 ` [PATCH 6/6] HACK: arm: reprogram twd based on clk notifier Mike Turquette
2011-12-14 8:52 ` Linus Walleij
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=1323837088-2469-5-git-send-email-mturquette@ti.com \
--to=mturquette@ti.com \
--cc=amit.kucheria@linaro.org \
--cc=andrew@lunn.ch \
--cc=arnd.bergmann@linaro.org \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dsaxena@linaro.org \
--cc=eric.miao@linaro.org \
--cc=grant.likely@secretlab.ca \
--cc=jeremy.kerr@canonical.com \
--cc=khilman@ti.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mturquette@linaro.org \
--cc=patches@linaro.org \
--cc=paul@pwsan.com \
--cc=richard.zhao@linaro.org \
--cc=rnayak@ti.com \
--cc=sboyd@quicinc.com \
--cc=shawn.guo@freescale.com \
--cc=skannan@quicinc.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
/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).