From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: rockchip: mark rk3399 GIC clocks as critical
Date: Tue, 17 May 2016 23:10:51 +0200 [thread overview]
Message-ID: <2111538.t2M7m4hXj2@phil> (raw)
In-Reply-To: <1463164937-91089-1-git-send-email-briannorris@chromium.org>
Am Freitag, 13. Mai 2016, 11:42:16 schrieb Brian Norris:
> We never want to kill the GIC.
>
> Noticed when making other clock fixups, and seeing the newly-constructed
> clock tree try to disable cpll, where we had this parent structure:
>
> aclk_gic <------\
>
> |--- aclk_gic_pre <-- cpll <-- pll_cpll
>
> aclk_gic_noc <--/
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
applied both patches to my clk-fixes branch with Dougs review-tags.
Thanks
Heiko
prev parent reply other threads:[~2016-05-17 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 18:42 [PATCH 1/2] clk: rockchip: mark rk3399 GIC clocks as critical Brian Norris
2016-05-13 18:42 ` [PATCH 2/2] clk: rockchip: fix incorrect parent for rk3399's {c, g}pll_aclk_perihp_src Brian Norris
2016-05-13 20:10 ` Doug Anderson
2016-05-14 3:36 ` [PATCH 2/2] clk: rockchip: fix incorrect parent for rk3399's {c,g}pll_aclk_perihp_src Xing Zheng
2016-05-16 15:49 ` [PATCH 2/2] clk: rockchip: fix incorrect parent for rk3399's {c, g}pll_aclk_perihp_src Doug Anderson
2016-08-01 10:08 ` [PATCH 2/2] clk: rockchip: fix incorrect parent for rk3399's {c,g}pll_aclk_perihp_src Xing Zheng
2016-05-13 19:43 ` [PATCH 1/2] clk: rockchip: mark rk3399 GIC clocks as critical Doug Anderson
2016-05-17 21:10 ` Heiko Stuebner [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=2111538.t2M7m4hXj2@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