[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <551ac156-0cfa-29be-335f-d8a1f171cd8a@samsung.com>
Date: Fri, 20 Jan 2017 13:32:18 +0100
From: Sylwester Nawrocki <s.nawrocki@...sung.com>
To: Javier Martinez Canillas <javier@....samsung.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>
Cc: linux-kernel@...r.kernel.org, Inki Dae <inki.dae@...sung.com>,
Andi Shyti <andi.shyti@...sung.com>,
Shuah Khan <shuahkh@....samsung.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Kukjin Kim <kgene@...nel.org>,
Chanwoo Choi <cw00.choi@...sung.com>,
linux-clk@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
Tomasz Figa <tomasz.figa@...il.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] clk: samsung: exynos5420: Mark CLK_ACLK432_SCALER as
CLK_IS_CRITICAL
On 01/20/2017 11:41 AM, Javier Martinez Canillas wrote:
> On Exynos5800 SoC the SCALER block uses 2 input clocks: CLK_ACLK_300_GSCL
> and CLK_ACLK432_SCALER, so both needs to be ungated in order to access it.
>
> But Exynos5420 only has the CLK_ACLK_300_GSCL as gsc_pd clk. So just using
> this definition from exynos5420.dtsi in Exynos5800 leads to the following:
[...]
> So until a proper solution based on runtime PM gets merged, mark the clock
> as critical to prevent it to be gated.
>
> Suggested-by: Marek Szyprowski <m.szyprowski@...sung.com>
> Signed-off-by: Javier Martinez Canillas <javier@....samsung.com>
Acked-by: Sylwester Nawrocki <s.nawrocki@...sung.com>
Powered by blists - more mailing lists