From: yong.shen@freescale.com (yong.shen at freescale.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] ARM: i.MX5: uart clock bug fix
Date: Tue, 11 Jan 2011 20:54:24 +0800 [thread overview]
Message-ID: <1294750464-8660-5-git-send-email-yong.shen@freescale.com> (raw)
In-Reply-To: <1294750464-8660-1-git-send-email-yong.shen@freescale.com>
From: Yong Shen <yong.shen@freescale.com>
uart clk is from pll3 on mx53 instead of mx51
Signed-off-by: Yong Shen <yong.shen@freescale.com>
---
arch/arm/mach-mx5/clock-mx51-mx53.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-mx5/clock-mx51-mx53.c b/arch/arm/mach-mx5/clock-mx51-mx53.c
index a20d0c0..3fb7ff8 100644
--- a/arch/arm/mach-mx5/clock-mx51-mx53.c
+++ b/arch/arm/mach-mx5/clock-mx51-mx53.c
@@ -1370,7 +1370,6 @@ int __init mx51_clocks_init(unsigned long ckil, unsigned long osc,
clk_tree_init();
- clk_set_parent(&uart_root_clk, &pll3_sw_clk);
clk_enable(&cpu_clk);
clk_enable(&main_bus_clk);
@@ -1413,6 +1412,7 @@ int __init mx53_clocks_init(unsigned long ckil, unsigned long osc,
clk_tree_init();
+ clk_set_parent(&uart_root_clk, &pll3_sw_clk);
clk_enable(&cpu_clk);
clk_enable(&main_bus_clk);
--
1.7.1
prev parent reply other threads:[~2011-01-11 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 12:54 ARM: i.MX53: spi related patches yong.shen at freescale.com
2011-01-11 12:54 ` [PATCH v2 1/4] ARM: i.MX53: enable spi support yong.shen at freescale.com
2011-01-21 10:40 ` Sascha Hauer
2011-01-21 14:36 ` Yong Shen
2011-01-11 12:54 ` [PATCH v2 2/4] ARM: i.MX53 EVK: add spi device yong.shen at freescale.com
2011-01-11 12:54 ` [PATCH v2 3/4] ARM: i.MX53 EVK: add spi nor device yong.shen at freescale.com
2011-01-11 12:54 ` yong.shen at freescale.com [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=1294750464-8660-5-git-send-email-yong.shen@freescale.com \
--to=yong.shen@freescale.com \
--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).