From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188
Date: Fri, 21 Aug 2015 20:24:25 +0200 [thread overview]
Message-ID: <1855234.LF6EVPIbW1@phil> (raw)
In-Reply-To: <1440180627-4566-1-git-send-email-romain.perier@gmail.com>
Hi Romain,
Am Freitag, 21. August 2015, 18:10:27 schrieb Romain Perier:
> Clocks for bank GPIO3 and GPIO4 are supplied by pclk_peri. These clocks need
> to stay on, otherwise pinctrl hangs the system when the driver is probed.
I don't agree with the commit message.
The issue you see does not originate from the pinctrl driver itself. Instead
only the new flexible clock handling causes some other (still unhandled)
component reyling on pclk_peri to hang the system.
In the past the clocks for the gpio banks were simply enabled once during
probe, so pclk_peri as parent clock would also stay enabled for eternity. Now
we enable the gpio clocks only when necessary, which results in that pclk_peri
might get disabled too when no other component has claimed it - hence its
addition to critical clocks.
Also, please note that Stephen Boyd is now also clock maintainer.
>
> Signed-off-by: Romain Perier <romain.perier@gmail.com>
> ---
> 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 f63a642..596be81 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)
next prev parent reply other threads:[~2015-08-21 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 18:10 [PATCH] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188 Romain Perier
2015-08-21 18:24 ` Heiko Stuebner [this message]
2015-08-22 15:05 ` Michael Niewoehner
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=1855234.LF6EVPIbW1@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).