From: thomas.abraham@linaro.org (Thomas Abraham)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 11/12] ARM: Exynos: use fin_pll clock as the tick clock source for mct
Date: Sun, 25 Nov 2012 02:48:04 +0530 [thread overview]
Message-ID: <1353791885-2566-12-git-send-email-thomas.abraham@linaro.org> (raw)
In-Reply-To: <1353791885-2566-1-git-send-email-thomas.abraham@linaro.org>
With the migration of Exynos4 clocks to use common clock framework, the old
styled 'xtal' clock is not used anymore. Instead, the clock 'fin_pll' is used
as the tick clock for mct controller.
Cc: Kukjin Kim <kgene.kim@samsung.com>
Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
---
arch/arm/mach-exynos/mct.c | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-exynos/mct.c b/arch/arm/mach-exynos/mct.c
index 448ce86..71e1502 100644
--- a/arch/arm/mach-exynos/mct.c
+++ b/arch/arm/mach-exynos/mct.c
@@ -487,10 +487,22 @@ static struct local_timer_ops exynos4_mct_tick_ops __cpuinitdata = {
static void __init exynos4_timer_resources(struct device_node *np)
{
+#ifdef CONFIG_COMMON_CLK
+ struct clk *tick_clk;
+
+ tick_clk = clk_get(NULL, "fin_pll");
+ if (IS_ERR(tick_clk))
+ panic("%s: unable to determine tick clock rate\n", __func__);
+ clk_rate = clk_get_rate(tick_clk);
+#else
+ /*
+ * todo: remove this legacy code after adding common clock support for
+ * exynos5250.
+ */
struct clk *mct_clk;
mct_clk = clk_get(NULL, "xtal");
-
clk_rate = clk_get_rate(mct_clk);
+#endif
reg_base = np ? of_iomap(np, 0) : S5P_VA_SYSTIMER;
if (!reg_base)
--
1.7.4.4
next prev parent reply other threads:[~2012-11-24 21:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 21:17 [PATCH v4 00/12] clk: exynos4: migrate to common clock framework Thomas Abraham
2012-11-24 21:17 ` [PATCH v4 01/12] clk: samsung: add common clock framework helper functions for Samsung platforms Thomas Abraham
2012-11-24 21:17 ` [PATCH v4 02/12] clk: samsung: add pll clock registration helper functions Thomas Abraham
2012-11-24 21:17 ` [PATCH v4 03/12] clk: exynos4: register clocks using common clock framework Thomas Abraham
2012-11-24 21:17 ` [PATCH v4 04/12] ARM: Exynos: Rework timer initialization sequence Thomas Abraham
2012-11-24 21:17 ` [PATCH v4 05/12] ARM: Exynos4: Migrate clock support to common clock framework Thomas Abraham
2012-11-24 21:17 ` [PATCH v4 06/12] ARM: dts: add exynos4 clock controller nodes Thomas Abraham
2012-11-24 21:18 ` [PATCH v4 07/12] ARM: dts: add xxti and xusbxti fixed rate clock nodes for exynos4 based platforms Thomas Abraham
2012-11-24 21:18 ` [PATCH v4 08/12] ARM: Exynos4: allow legacy board support to specify xxti and xusbxti clock speed Thomas Abraham
2012-11-24 21:18 ` [PATCH v4 09/12] ARM: dts: add clock provider information for all controllers in Exynos4 SoC Thomas Abraham
2012-11-24 21:18 ` [PATCH v4 10/12] ARM: Exynos4: remove auxdata table from machine file Thomas Abraham
2012-11-24 21:18 ` Thomas Abraham [this message]
2012-11-24 21:18 ` [PATCH v4 12/12] ARM: Exynos: add support for mct clock setup Thomas Abraham
2012-11-26 19:31 ` [PATCH v4 00/12] clk: exynos4: migrate to common clock framework Mike Turquette
2012-11-27 0:57 ` Kukjin Kim
2012-11-27 17:31 ` Mike Turquette
2012-11-27 8:54 ` Thomas Abraham
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=1353791885-2566-12-git-send-email-thomas.abraham@linaro.org \
--to=thomas.abraham@linaro.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).