From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: add pclk_cpu to the list of rk3188 critical clocks
Date: Mon, 17 Aug 2015 20:01:32 +0200 [thread overview]
Message-ID: <5275855.eah07vmf4I@phil> (raw)
In-Reply-To: <5400BEF8-5245-4F7B-845B-D326A7BC56B5@mniewoehner.de>
Hi,
Am Montag, 17. August 2015, 19:38:22 schrieb Michael Niewoehner:
> gpio clock is getting disabled to save power but pclk_cpu is needed for
> act8865 regulator
Please refine the commit message a bit :-) . Something along
pclk_cpu needs to keep running and with the recent gpio clock
handling this is not always the case anymore. So add it to the list
of critical clocks.
and also please add "Linus Walleij <linus.walleij@linaro.org>" to the list of
recipients. As the gpio clock handling change does go through his tree, the
matching critical clock handling should also go through him.
Heiko
>
> Signed-off-by: Michael Niewoehner <linux@mniewoehner.de>
> ---
> 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 e4f9d47..1c93229 100644
> --- a/drivers/clk/rockchip/clk-rk3188.c
> +++ b/drivers/clk/rockchip/clk-rk3188.c
> @@ -708,6 +708,7 @@ static const char *const rk3188_critical_clocks[]
> __initconst = { "aclk_cpu",
> "aclk_peri",
> "hclk_peri",
> + "pclk_cpu",
> };
>
> static void __init rk3188_common_clk_init(struct device_node *np)
next prev parent reply other threads:[~2015-08-17 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 17:38 [PATCH] clk: rockchip: add pclk_cpu to the list of rk3188 critical clocks Michael Niewoehner
2015-08-17 18:01 ` Heiko Stuebner [this message]
2015-08-17 18:51 ` Michael Niewoehner
2015-08-17 19:37 ` Heiko Stuebner
2015-08-17 19:50 ` [PATCH v2] " Michael Niewoehner
2015-08-17 19:55 ` Heiko Stuebner
2015-08-25 18:59 ` Michael Turquette
2015-08-25 20:17 ` Heiko Stuebner
2015-08-25 20:22 ` [PATCH v3] " Michael Niewoehner
2015-08-27 16:52 ` Michael Turquette
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=5275855.eah07vmf4I@phil \
--to=heiko@sntech.de \
--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).