[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=UjPy-n-53nhxr7yC1t1j+eD6pRt0_i5_6hhY=Rnz6xsw@mail.gmail.com>
Date: Fri, 13 May 2016 12:43:25 -0700
From: Doug Anderson <dianders@...omium.org>
To: Brian Norris <briannorris@...omium.org>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>,
linux-clk <linux-clk@...r.kernel.org>,
Heiko Stuebner <heiko@...ech.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Brian Norris <computersforpeace@...il.com>,
Xing Zheng <zhengxing@...k-chips.com>
Subject: Re: [PATCH 1/2] clk: rockchip: mark rk3399 GIC clocks as critical
Brian,
On Fri, May 13, 2016 at 11:42 AM, Brian Norris <briannorris@...omium.org> wrote:
> 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@...omium.org>
> ---
> drivers/clk/rockchip/clk-rk3399.c | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Douglas Anderson <dianders@...omium.org>
Powered by blists - more mailing lists