From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: also protect hclk_peri as critical
Date: Wed, 10 Sep 2014 10:42:35 -0700 [thread overview]
Message-ID: <20140910174235.19023.4888@quantum> (raw)
In-Reply-To: <1950006.Th78Z9O4lJ@diego>
Quoting Heiko St?bner (2014-09-10 08:52:02)
> The dwc2 usb controller also uses agressive clock gating, which in this
> case leads to hclk_peri getting disabled and hanging the system.
> Therefore move it to the critical clocks until we also control that
> part of the system.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Applied to clk-next.
Regards,
Mike
> ---
> drivers/clk/rockchip/clk-rk3188.c | 1 +
> drivers/clk/rockchip/clk-rk3288.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/drivers/clk/rockchip/clk-rk3188.c b/drivers/clk/rockchip/clk-rk3188.c
> index 1892c66..9f9937e 100644
> --- a/drivers/clk/rockchip/clk-rk3188.c
> +++ b/drivers/clk/rockchip/clk-rk3188.c
> @@ -602,6 +602,7 @@ static struct rockchip_clk_branch rk3188_clk_branches[] __initdata = {
> static const char *rk3188_critical_clocks[] __initconst = {
> "aclk_cpu",
> "aclk_peri",
> + "hclk_peri",
> };
>
> static void __init rk3188_common_clk_init(struct device_node *np)
> diff --git a/drivers/clk/rockchip/clk-rk3288.c b/drivers/clk/rockchip/clk-rk3288.c
> index 43e0ad0..c76b16d 100644
> --- a/drivers/clk/rockchip/clk-rk3288.c
> +++ b/drivers/clk/rockchip/clk-rk3288.c
> @@ -683,6 +683,7 @@ static struct rockchip_clk_branch rk3288_clk_branches[] __initdata = {
> static const char *rk3288_critical_clocks[] __initconst = {
> "aclk_cpu",
> "aclk_peri",
> + "hclk_peri",
> };
>
> static void __init rk3288_clk_init(struct device_node *np)
> --
> 2.0.1
>
>
prev parent reply other threads:[~2014-09-10 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 15:52 [PATCH] clk: rockchip: also protect hclk_peri as critical Heiko Stübner
2014-09-10 17:42 ` Mike Turquette [this message]
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=20140910174235.19023.4888@quantum \
--to=mturquette@linaro.org \
--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