From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: rockchip: add pclk_cpu to the list of rk3188 critical clocks
Date: Mon, 17 Aug 2015 21:55:11 +0200 [thread overview]
Message-ID: <14545587.HIDVkPerl6@phil> (raw)
In-Reply-To: <F5234F5E-2A91-4B63-B260-3F20A4D16A9D@mniewoehner.de>
Am Montag, 17. August 2015, 21:50:53 schrieb Michael Niewoehner:
> pclk_cpu needs to keep running because it is needed for devices like
> the act8865 regulator but with the recent gpio clock handling this is
> not always the case anymore. So add it to the list of critical clocks.
>
> Signed-off-by: Michael Niewoehner <linux@mniewoehner.de>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> ---
> Changes in v2:
> - adapt commit message
> - add Linus Walleij to recipients, as the patch is related to the gpio clock
> change in the rockchip pinctrl driver it should go through his tree as well
>
> 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 19:55 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
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 [this message]
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=14545587.HIDVkPerl6@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).