From: romain.perier@gmail.com (Romain Perier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188
Date: Sun, 23 Aug 2015 11:32:37 +0200 [thread overview]
Message-ID: <1440322357-2621-1-git-send-email-romain.perier@gmail.com> (raw)
Now that the rockchip clock subsystem does clock gating with GPIO banks,
these are no longer enabled once during probe and no longer stay enabled
for eternity. When all these clocks are disabled, the parent clock pclk_peri
might be disabled too, as no other child claims it. So, we need to add pclk_peri
to the critical clocks.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Tested-by: Michael Niewoehner <linux@mniewoehner.de>
---
changes in v2:
- Improved commit messages
- Added "Tested-by" from Michael Niewoehner, as he tested v1 and no code changed
drivers/clk/rockchip/clk-rk3188.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/rockchip/clk-rk3188.c b/drivers/clk/rockchip/clk-rk3188.c
index bf20214..839a22a 100644
--- a/drivers/clk/rockchip/clk-rk3188.c
+++ b/drivers/clk/rockchip/clk-rk3188.c
@@ -717,6 +717,7 @@ static const char *const rk3188_critical_clocks[] __initconst = {
"aclk_peri",
"hclk_peri",
"pclk_cpu",
+ "pclk_peri",
};
static void __init rk3188_common_clk_init(struct device_node *np)
--
2.1.4
next reply other threads:[~2015-08-23 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 9:32 Romain Perier [this message]
2015-08-31 14:42 ` [PATCH v2] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188 Romain Perier
2015-09-04 6:50 ` Romain Perier
2015-09-04 16:24 ` Stephen Boyd
2015-09-05 16:12 ` Romain Perier
2015-09-09 17:58 ` Romain Perier
2015-09-09 21:47 ` Stephen Boyd
2015-09-10 7:05 ` Romain Perier
2015-09-10 16:40 ` Michael Niewoehner
2015-09-10 20:51 ` Stephen Boyd
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=1440322357-2621-1-git-send-email-romain.perier@gmail.com \
--to=romain.perier@gmail.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).