From: Erin Lo <erin.lo@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Rob Herring <robh@kernel.org>
Cc: John Crispin <blogic@openwrt.org>, Arnd Bergmann <arnd@arndb.de>,
Sascha Hauer <kernel@pengutronix.de>,
Daniel Kurtz <djkurtz@chromium.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <linux-clk@vger.kernel.org>,
<srv_heupstream@mediatek.com>,
James Liao <jamesjj.liao@mediatek.com>
Subject: [PATCH v8 01/10] clk: fix initial state of critical clock's parents
Date: Tue, 17 May 2016 13:05:02 +0800 [thread overview]
Message-ID: <1463461511-25019-2-git-send-email-erin.lo@mediatek.com> (raw)
In-Reply-To: <1463461511-25019-1-git-send-email-erin.lo@mediatek.com>
From: James Liao <jamesjj.liao@mediatek.com>
This patch fixed wrong state of parent clocks if they are registered
after critical clocks.
Signed-off-by: James Liao <jamesjj.liao@mediatek.com>
---
drivers/clk/clk.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index ce39add..bf80e39 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -2388,8 +2388,15 @@ static int __clk_core_init(struct clk_core *core)
hlist_for_each_entry_safe(orphan, tmp2, &clk_orphan_list, child_node) {
struct clk_core *parent = __clk_init_parent(orphan);
- if (parent)
+ if (parent) {
clk_core_reparent(orphan, parent);
+
+ if (orphan->prepare_count)
+ clk_core_prepare(parent);
+
+ if (orphan->enable_count)
+ clk_core_enable(parent);
+ }
}
/*
--
1.9.1
next prev parent reply other threads:[~2016-05-17 5:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 5:05 [PATCH v8 0/10] Add clock support for Mediatek MT2701 Erin Lo
2016-05-17 5:05 ` Erin Lo [this message]
2016-05-17 5:05 ` [PATCH v8 02/10] clk: mediatek: remove __init from clk registration functions Erin Lo
2016-05-17 5:05 ` [PATCH v8 03/10] clk: mediatek: Refine the makefile to support multiple clock drivers Erin Lo
2016-05-17 5:05 ` [PATCH v8 04/10] dt-bindings: ARM: Mediatek: Document bindings for MT2701 Erin Lo
2016-05-17 5:05 ` [PATCH v8 05/10] clk: mediatek: Add dt-bindings for MT2701 clocks Erin Lo
2016-05-17 5:05 ` [PATCH v8 06/10] clk: mediatek: Add MT2701 clock support Erin Lo
2016-05-17 5:05 ` [PATCH v8 07/10] reset: mediatek: Add MT2701 reset controller dt-binding file Erin Lo
2016-05-17 5:05 ` [PATCH v8 08/10] reset: mediatek: Add MT2701 reset driver Erin Lo
2016-05-17 5:05 ` [PATCH v8 09/10] arm: dts: mt2701: Add clock controller device nodes Erin Lo
2016-05-17 5:05 ` [PATCH v8 10/10] arm: dts: mt2701: Use real clock for UARTs Erin Lo
2016-05-17 7:10 ` [PATCH v8 0/10] Add clock support for Mediatek MT2701 erin.lo
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=1463461511-25019-2-git-send-email-erin.lo@mediatek.com \
--to=erin.lo@mediatek.com \
--cc=arnd@arndb.de \
--cc=blogic@openwrt.org \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=jamesjj.liao@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=srv_heupstream@mediatek.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