From: Heiko Stuebner <heiko@sntech.de>
To: Xing Zheng <zhengxing@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, keescook@google.com,
leozwang@google.com, Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: rockchip: rk3036: Add apll as the critical clock
Date: Thu, 21 Jan 2016 10:21:50 +0100 [thread overview]
Message-ID: <7538210.fX6mmzZ75v@phil> (raw)
In-Reply-To: <1453279037-23971-1-git-send-email-zhengxing@rock-chips.com>
Hi Xing,
Am Mittwoch, 20. Januar 2016, 16:37:17 schrieb Xing Zheng:
> The apll may be closed if there are some child clock nodes below
> it when the device startup. Therefore, the apll should be keep
> critical.
>
> The apll tree like this:
> pll_apll
> apll
> armclk
> pclk_dbg
> aclk_core_pre
> aclk_hvec
> uart_pll_clk
> uart2_src
> uart2_frac
> uart1_src
> uart1_frac
> uart0_src
> uart0_frac
can you find out which of those clocks does cause your hang?
Because things like the uart-clocks for example should be handled by their
driver already, at the time the clk_disable_unused runs(). So I'd really
like the critical clock to be the actually needed clock.
Thanks
Heiko
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
> ---
>
> drivers/clk/rockchip/clk-rk3036.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/rockchip/clk-rk3036.c
> b/drivers/clk/rockchip/clk-rk3036.c index ebce980..483913b 100644
> --- a/drivers/clk/rockchip/clk-rk3036.c
> +++ b/drivers/clk/rockchip/clk-rk3036.c
> @@ -425,6 +425,7 @@ static struct rockchip_clk_branch
> rk3036_clk_branches[] __initdata = { };
>
> static const char *const rk3036_critical_clocks[] __initconst = {
> + "apll",
> "aclk_cpu",
> "aclk_peri",
> "hclk_peri",
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: rk3036: Add apll as the critical clock
Date: Thu, 21 Jan 2016 10:21:50 +0100 [thread overview]
Message-ID: <7538210.fX6mmzZ75v@phil> (raw)
In-Reply-To: <1453279037-23971-1-git-send-email-zhengxing@rock-chips.com>
Hi Xing,
Am Mittwoch, 20. Januar 2016, 16:37:17 schrieb Xing Zheng:
> The apll may be closed if there are some child clock nodes below
> it when the device startup. Therefore, the apll should be keep
> critical.
>
> The apll tree like this:
> pll_apll
> apll
> armclk
> pclk_dbg
> aclk_core_pre
> aclk_hvec
> uart_pll_clk
> uart2_src
> uart2_frac
> uart1_src
> uart1_frac
> uart0_src
> uart0_frac
can you find out which of those clocks does cause your hang?
Because things like the uart-clocks for example should be handled by their
driver already, at the time the clk_disable_unused runs(). So I'd really
like the critical clock to be the actually needed clock.
Thanks
Heiko
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
> ---
>
> drivers/clk/rockchip/clk-rk3036.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/rockchip/clk-rk3036.c
> b/drivers/clk/rockchip/clk-rk3036.c index ebce980..483913b 100644
> --- a/drivers/clk/rockchip/clk-rk3036.c
> +++ b/drivers/clk/rockchip/clk-rk3036.c
> @@ -425,6 +425,7 @@ static struct rockchip_clk_branch
> rk3036_clk_branches[] __initdata = { };
>
> static const char *const rk3036_critical_clocks[] __initconst = {
> + "apll",
> "aclk_cpu",
> "aclk_peri",
> "hclk_peri",
next prev parent reply other threads:[~2016-01-21 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 8:37 [PATCH] clk: rockchip: rk3036: Add apll as the critical clock Xing Zheng
2016-01-20 8:37 ` Xing Zheng
2016-01-21 9:21 ` Heiko Stuebner [this message]
2016-01-21 9:21 ` Heiko Stuebner
2016-01-22 7:49 ` Xing Zheng
2016-01-22 7:49 ` Xing Zheng
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=7538210.fX6mmzZ75v@phil \
--to=heiko@sntech.de \
--cc=keescook@google.com \
--cc=leozwang@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=zhengxing@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.