* Re: [PATCH] clk/samsung: exynos542x: mark some clocks as critical
2016-12-22 9:44 ` [PATCH] clk/samsung: exynos542x: mark some clocks as critical Marek Szyprowski
@ 2016-12-22 13:07 ` Javier Martinez Canillas
2016-12-23 17:00 ` Chanwoo Choi
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Javier Martinez Canillas @ 2016-12-22 13:07 UTC (permalink / raw)
To: Marek Szyprowski, linux-clk, linux-samsung-soc
Cc: Sylwester Nawrocki, Krzysztof Kozlowski,
Bartlomiej Zolnierkiewicz, Chanwoo Choi
Hello Marek,
On 12/22/2016 06:44 AM, Marek Szyprowski wrote:
> Some parent clocks of the Exynos542x clock blocks, which have separate
> power domains (like DISP, MFC, MSC, GSC, FSYS and G2D) must be always
> enabled to access any register related to power management unit or devices
> connected to it. For the time being, until a proper solution based on
> runtime PM is applied, mark those clocks as critical (instead of ignore
> unused or even no flags) to prevent disabling them.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> drivers/clk/samsung/clk-exynos5420.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
And on an Exynos5800 Peach Pi Chromebook:
Tested-by: Javier Martinez Canillas <javier@osg.samsung.com>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] clk/samsung: exynos542x: mark some clocks as critical
2016-12-22 9:44 ` [PATCH] clk/samsung: exynos542x: mark some clocks as critical Marek Szyprowski
2016-12-22 13:07 ` Javier Martinez Canillas
@ 2016-12-23 17:00 ` Chanwoo Choi
2016-12-27 8:14 ` Marek Szyprowski
2017-01-09 12:30 ` Sylwester Nawrocki
2017-01-10 0:11 ` Stephen Boyd
3 siblings, 1 reply; 8+ messages in thread
From: Chanwoo Choi @ 2016-12-23 17:00 UTC (permalink / raw)
To: Marek Szyprowski
Cc: linux-clk, linux-samsung-soc, Sylwester Nawrocki,
Krzysztof Kozlowski, Bartlomiej Zolnierkiewicz, Chanwoo Choi
Dear Marek,
I have a question. I agree some clocks should be always on with CLK_IS_CRITICAL.
CLK_ACLK333 is only used on exynos5420.dtsi. So, I understand to add
CLK_IS_CRITICAL flag to CLK_ACLK333.
Except for CLK_ACLK333, the remaining clocks with CLK_IS_CRITICAL were
not used on mainline kernel (arch/arm/boot/dts/*). It means that the
remaining clocks might be ON before applying this patch. So,
CLK_IGNORE_UNUSED might be enough to maintain their ON state.
If we don't add the CLK_IGNORE_UNUSED flag to clocks except for
CLK_ACLK333, are there any problem?
But, if bootloader don't turn on these clocks, this patch is necessary.
Best Regards,
Chanwoo Choi
2016-12-22 18:44 GMT+09:00 Marek Szyprowski <m.szyprowski@samsung.com>:
> Some parent clocks of the Exynos542x clock blocks, which have separate
> power domains (like DISP, MFC, MSC, GSC, FSYS and G2D) must be always
> enabled to access any register related to power management unit or devices
> connected to it. For the time being, until a proper solution based on
> runtime PM is applied, mark those clocks as critical (instead of ignore
> unused or even no flags) to prevent disabling them.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> drivers/clk/samsung/clk-exynos5420.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/clk/samsung/clk-exynos5420.c b/drivers/clk/samsung/clk-exynos5420.c
> index 8c8b495cbf0d..cdc092a1d9ef 100644
> --- a/drivers/clk/samsung/clk-exynos5420.c
> +++ b/drivers/clk/samsung/clk-exynos5420.c
> @@ -586,7 +586,7 @@ static void __init exynos5420_clk_sleep_init(void) {}
> GATE(CLK_ACLK550_CAM, "aclk550_cam", "mout_user_aclk550_cam",
> GATE_BUS_TOP, 24, 0, 0),
> GATE(CLK_ACLK432_SCALER, "aclk432_scaler", "mout_user_aclk432_scaler",
> - GATE_BUS_TOP, 27, 0, 0),
> + GATE_BUS_TOP, 27, CLK_IS_CRITICAL, 0),
> };
>
> static const struct samsung_mux_clock exynos5420_mux_clks[] __initconst = {
> @@ -956,20 +956,20 @@ static void __init exynos5420_clk_sleep_init(void) {}
> GATE(CLK_SMMU_G2D, "smmu_g2d", "aclk333_g2d", GATE_IP_G2D, 7, 0, 0),
>
> GATE(0, "aclk200_fsys", "mout_user_aclk200_fsys",
> - GATE_BUS_FSYS0, 9, CLK_IGNORE_UNUSED, 0),
> + GATE_BUS_FSYS0, 9, CLK_IS_CRITICAL, 0),
> GATE(0, "aclk200_fsys2", "mout_user_aclk200_fsys2",
> GATE_BUS_FSYS0, 10, CLK_IGNORE_UNUSED, 0),
>
> GATE(0, "aclk333_g2d", "mout_user_aclk333_g2d",
> GATE_BUS_TOP, 0, CLK_IGNORE_UNUSED, 0),
> GATE(0, "aclk266_g2d", "mout_user_aclk266_g2d",
> - GATE_BUS_TOP, 1, CLK_IGNORE_UNUSED, 0),
> + GATE_BUS_TOP, 1, CLK_IS_CRITICAL, 0),
> GATE(0, "aclk300_jpeg", "mout_user_aclk300_jpeg",
> GATE_BUS_TOP, 4, CLK_IGNORE_UNUSED, 0),
> GATE(0, "aclk333_432_isp0", "mout_user_aclk333_432_isp0",
> GATE_BUS_TOP, 5, 0, 0),
> GATE(0, "aclk300_gscl", "mout_user_aclk300_gscl",
> - GATE_BUS_TOP, 6, CLK_IGNORE_UNUSED, 0),
> + GATE_BUS_TOP, 6, CLK_IS_CRITICAL, 0),
> GATE(0, "aclk333_432_gscl", "mout_user_aclk333_432_gscl",
> GATE_BUS_TOP, 7, CLK_IGNORE_UNUSED, 0),
> GATE(0, "aclk333_432_isp", "mout_user_aclk333_432_isp",
> @@ -983,20 +983,20 @@ static void __init exynos5420_clk_sleep_init(void) {}
> GATE(0, "aclk166", "mout_user_aclk166",
> GATE_BUS_TOP, 14, CLK_IGNORE_UNUSED, 0),
> GATE(CLK_ACLK333, "aclk333", "mout_user_aclk333",
> - GATE_BUS_TOP, 15, CLK_IGNORE_UNUSED, 0),
> + GATE_BUS_TOP, 15, CLK_IS_CRITICAL, 0),
> GATE(0, "aclk400_isp", "mout_user_aclk400_isp",
> GATE_BUS_TOP, 16, 0, 0),
> GATE(0, "aclk400_mscl", "mout_user_aclk400_mscl",
> GATE_BUS_TOP, 17, 0, 0),
> GATE(0, "aclk200_disp1", "mout_user_aclk200_disp1",
> - GATE_BUS_TOP, 18, 0, 0),
> + GATE_BUS_TOP, 18, CLK_IS_CRITICAL, 0),
> GATE(CLK_SCLK_MPHY_IXTAL24, "sclk_mphy_ixtal24", "mphy_refclk_ixtal24",
> GATE_BUS_TOP, 28, 0, 0),
> GATE(CLK_SCLK_HSIC_12M, "sclk_hsic_12m", "ff_hsic_12m",
> GATE_BUS_TOP, 29, 0, 0),
>
> GATE(0, "aclk300_disp1", "mout_user_aclk300_disp1",
> - SRC_MASK_TOP2, 24, 0, 0),
> + SRC_MASK_TOP2, 24, CLK_IS_CRITICAL, 0),
>
> GATE(CLK_MAU_EPLL, "mau_epll", "mout_mau_epll_clk",
> SRC_MASK_TOP7, 20, 0, 0),
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] clk/samsung: exynos542x: mark some clocks as critical
2016-12-23 17:00 ` Chanwoo Choi
@ 2016-12-27 8:14 ` Marek Szyprowski
2016-12-27 8:24 ` Chanwoo Choi
0 siblings, 1 reply; 8+ messages in thread
From: Marek Szyprowski @ 2016-12-27 8:14 UTC (permalink / raw)
To: cwchoi00
Cc: linux-clk, linux-samsung-soc, Sylwester Nawrocki,
Krzysztof Kozlowski, Bartlomiej Zolnierkiewicz, Chanwoo Choi
Dear Chanwoo,
On 2016-12-23 18:00, Chanwoo Choi wrote:
> Dear Marek,
>
> I have a question. I agree some clocks should be always on with CLK_IS_CRITICAL.
> CLK_ACLK333 is only used on exynos5420.dtsi. So, I understand to add
> CLK_IS_CRITICAL flag to CLK_ACLK333.
>
> Except for CLK_ACLK333, the remaining clocks with CLK_IS_CRITICAL were
> not used on mainline kernel (arch/arm/boot/dts/*). It means that the
> remaining clocks might be ON before applying this patch. So,
> CLK_IGNORE_UNUSED might be enough to maintain their ON state.
>
> If we don't add the CLK_IGNORE_UNUSED flag to clocks except for
> CLK_ACLK333, are there any problem?
> But, if bootloader don't turn on these clocks, this patch is necessary.
Please note that CLK_IGNORE_UNUSED doesn't protect clock from turning off as
a result of turn off operation on one of the child-clocks. This patch fixes
the boot hang caused by changes in SYSMMU driver, which resulted in turning
off some clocks for G2D domain. Similar issues might happen for other
domains
depending on the probe order. Till now it worked only by a luck, because
there was child clock enabled early enough, which protected one of those
clocks from turning off.
>
> Best Regards,
> Chanwoo Choi
>
> 2016-12-22 18:44 GMT+09:00 Marek Szyprowski <m.szyprowski@samsung.com>:
>> Some parent clocks of the Exynos542x clock blocks, which have separate
>> power domains (like DISP, MFC, MSC, GSC, FSYS and G2D) must be always
>> enabled to access any register related to power management unit or devices
>> connected to it. For the time being, until a proper solution based on
>> runtime PM is applied, mark those clocks as critical (instead of ignore
>> unused or even no flags) to prevent disabling them.
>>
>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> ---
>> drivers/clk/samsung/clk-exynos5420.c | 14 +++++++-------
>> 1 file changed, 7 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/clk/samsung/clk-exynos5420.c b/drivers/clk/samsung/clk-exynos5420.c
>> index 8c8b495cbf0d..cdc092a1d9ef 100644
>> --- a/drivers/clk/samsung/clk-exynos5420.c
>> +++ b/drivers/clk/samsung/clk-exynos5420.c
>> @@ -586,7 +586,7 @@ static void __init exynos5420_clk_sleep_init(void) {}
>> GATE(CLK_ACLK550_CAM, "aclk550_cam", "mout_user_aclk550_cam",
>> GATE_BUS_TOP, 24, 0, 0),
>> GATE(CLK_ACLK432_SCALER, "aclk432_scaler", "mout_user_aclk432_scaler",
>> - GATE_BUS_TOP, 27, 0, 0),
>> + GATE_BUS_TOP, 27, CLK_IS_CRITICAL, 0),
>> };
>>
>> static const struct samsung_mux_clock exynos5420_mux_clks[] __initconst = {
>> @@ -956,20 +956,20 @@ static void __init exynos5420_clk_sleep_init(void) {}
>> GATE(CLK_SMMU_G2D, "smmu_g2d", "aclk333_g2d", GATE_IP_G2D, 7, 0, 0),
>>
>> GATE(0, "aclk200_fsys", "mout_user_aclk200_fsys",
>> - GATE_BUS_FSYS0, 9, CLK_IGNORE_UNUSED, 0),
>> + GATE_BUS_FSYS0, 9, CLK_IS_CRITICAL, 0),
>> GATE(0, "aclk200_fsys2", "mout_user_aclk200_fsys2",
>> GATE_BUS_FSYS0, 10, CLK_IGNORE_UNUSED, 0),
>>
>> GATE(0, "aclk333_g2d", "mout_user_aclk333_g2d",
>> GATE_BUS_TOP, 0, CLK_IGNORE_UNUSED, 0),
>> GATE(0, "aclk266_g2d", "mout_user_aclk266_g2d",
>> - GATE_BUS_TOP, 1, CLK_IGNORE_UNUSED, 0),
>> + GATE_BUS_TOP, 1, CLK_IS_CRITICAL, 0),
>> GATE(0, "aclk300_jpeg", "mout_user_aclk300_jpeg",
>> GATE_BUS_TOP, 4, CLK_IGNORE_UNUSED, 0),
>> GATE(0, "aclk333_432_isp0", "mout_user_aclk333_432_isp0",
>> GATE_BUS_TOP, 5, 0, 0),
>> GATE(0, "aclk300_gscl", "mout_user_aclk300_gscl",
>> - GATE_BUS_TOP, 6, CLK_IGNORE_UNUSED, 0),
>> + GATE_BUS_TOP, 6, CLK_IS_CRITICAL, 0),
>> GATE(0, "aclk333_432_gscl", "mout_user_aclk333_432_gscl",
>> GATE_BUS_TOP, 7, CLK_IGNORE_UNUSED, 0),
>> GATE(0, "aclk333_432_isp", "mout_user_aclk333_432_isp",
>> @@ -983,20 +983,20 @@ static void __init exynos5420_clk_sleep_init(void) {}
>> GATE(0, "aclk166", "mout_user_aclk166",
>> GATE_BUS_TOP, 14, CLK_IGNORE_UNUSED, 0),
>> GATE(CLK_ACLK333, "aclk333", "mout_user_aclk333",
>> - GATE_BUS_TOP, 15, CLK_IGNORE_UNUSED, 0),
>> + GATE_BUS_TOP, 15, CLK_IS_CRITICAL, 0),
>> GATE(0, "aclk400_isp", "mout_user_aclk400_isp",
>> GATE_BUS_TOP, 16, 0, 0),
>> GATE(0, "aclk400_mscl", "mout_user_aclk400_mscl",
>> GATE_BUS_TOP, 17, 0, 0),
>> GATE(0, "aclk200_disp1", "mout_user_aclk200_disp1",
>> - GATE_BUS_TOP, 18, 0, 0),
>> + GATE_BUS_TOP, 18, CLK_IS_CRITICAL, 0),
>> GATE(CLK_SCLK_MPHY_IXTAL24, "sclk_mphy_ixtal24", "mphy_refclk_ixtal24",
>> GATE_BUS_TOP, 28, 0, 0),
>> GATE(CLK_SCLK_HSIC_12M, "sclk_hsic_12m", "ff_hsic_12m",
>> GATE_BUS_TOP, 29, 0, 0),
>>
>> GATE(0, "aclk300_disp1", "mout_user_aclk300_disp1",
>> - SRC_MASK_TOP2, 24, 0, 0),
>> + SRC_MASK_TOP2, 24, CLK_IS_CRITICAL, 0),
>>
>> GATE(CLK_MAU_EPLL, "mau_epll", "mout_mau_epll_clk",
>> SRC_MASK_TOP7, 20, 0, 0),
>> --
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] clk/samsung: exynos542x: mark some clocks as critical
2016-12-27 8:14 ` Marek Szyprowski
@ 2016-12-27 8:24 ` Chanwoo Choi
0 siblings, 0 replies; 8+ messages in thread
From: Chanwoo Choi @ 2016-12-27 8:24 UTC (permalink / raw)
To: Marek Szyprowski, cwchoi00
Cc: linux-clk, linux-samsung-soc, Sylwester Nawrocki,
Krzysztof Kozlowski, Bartlomiej Zolnierkiewicz
Dear Marek,
On 2016년 12월 27일 17:14, Marek Szyprowski wrote:
> Dear Chanwoo,
>
>
> On 2016-12-23 18:00, Chanwoo Choi wrote:
>> Dear Marek,
>>
>> I have a question. I agree some clocks should be always on with CLK_IS_CRITICAL.
>> CLK_ACLK333 is only used on exynos5420.dtsi. So, I understand to add
>> CLK_IS_CRITICAL flag to CLK_ACLK333.
>>
>> Except for CLK_ACLK333, the remaining clocks with CLK_IS_CRITICAL were
>> not used on mainline kernel (arch/arm/boot/dts/*). It means that the
>> remaining clocks might be ON before applying this patch. So,
>> CLK_IGNORE_UNUSED might be enough to maintain their ON state.
>>
>> If we don't add the CLK_IGNORE_UNUSED flag to clocks except for
>> CLK_ACLK333, are there any problem?
>> But, if bootloader don't turn on these clocks, this patch is necessary.
>
> Please note that CLK_IGNORE_UNUSED doesn't protect clock from turning off as
> a result of turn off operation on one of the child-clocks. This patch fixes
Right. It was my mistake that I thought the 'aclk_*' clocks are leaf clock.
> the boot hang caused by changes in SYSMMU driver, which resulted in turning
> off some clocks for G2D domain. Similar issues might happen for other domains
> depending on the probe order. Till now it worked only by a luck, because
> there was child clock enabled early enough, which protected one of those
> clocks from turning off.
This patch makes sense.
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Regards,
Chanwoo Choi
[snip]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] clk/samsung: exynos542x: mark some clocks as critical
2016-12-22 9:44 ` [PATCH] clk/samsung: exynos542x: mark some clocks as critical Marek Szyprowski
2016-12-22 13:07 ` Javier Martinez Canillas
2016-12-23 17:00 ` Chanwoo Choi
@ 2017-01-09 12:30 ` Sylwester Nawrocki
2017-01-10 0:10 ` Stephen Boyd
2017-01-10 0:11 ` Stephen Boyd
3 siblings, 1 reply; 8+ messages in thread
From: Sylwester Nawrocki @ 2017-01-09 12:30 UTC (permalink / raw)
To: Stephen Boyd, Mike Turquette
Cc: Marek Szyprowski, linux-clk, linux-samsung-soc,
Krzysztof Kozlowski, Bartlomiej Zolnierkiewicz, Chanwoo Choi
On 12/22/2016 10:44 AM, Marek Szyprowski wrote:
> Some parent clocks of the Exynos542x clock blocks, which have separate
> power domains (like DISP, MFC, MSC, GSC, FSYS and G2D) must be always
> enabled to access any register related to power management unit or devices
> connected to it. For the time being, until a proper solution based on
> runtime PM is applied, mark those clocks as critical (instead of ignore
> unused or even no flags) to prevent disabling them.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Stephen, Mike, could you apply the $subject patch directly? Due to recent
Exynos IOMMU related changes that patch is needed as a regression fix
for v4.10.
Thanks,
Sylwester
> ---
> drivers/clk/samsung/clk-exynos5420.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/clk/samsung/clk-exynos5420.c
b/drivers/clk/samsung/clk-exynos5420.c
> index 8c8b495cbf0d..cdc092a1d9ef 100644
> --- a/drivers/clk/samsung/clk-exynos5420.c
> +++ b/drivers/clk/samsung/clk-exynos5420.c
> @@ -586,7 +586,7 @@ static void __init exynos5420_clk_sleep_init(void) {}
> GATE(CLK_ACLK550_CAM, "aclk550_cam", "mout_user_aclk550_cam",
> GATE_BUS_TOP, 24, 0, 0),
> GATE(CLK_ACLK432_SCALER, "aclk432_scaler", "mout_user_aclk432_scaler",
> - GATE_BUS_TOP, 27, 0, 0),
> + GATE_BUS_TOP, 27, CLK_IS_CRITICAL, 0),
> };
>
> static const struct samsung_mux_clock exynos5420_mux_clks[] __initconst = {
> @@ -956,20 +956,20 @@ static void __init exynos5420_clk_sleep_init(void) {}
> GATE(CLK_SMMU_G2D, "smmu_g2d", "aclk333_g2d", GATE_IP_G2D, 7, 0, 0),
>
> GATE(0, "aclk200_fsys", "mout_user_aclk200_fsys",
> - GATE_BUS_FSYS0, 9, CLK_IGNORE_UNUSED, 0),
> + GATE_BUS_FSYS0, 9, CLK_IS_CRITICAL, 0),
> GATE(0, "aclk200_fsys2", "mout_user_aclk200_fsys2",
> GATE_BUS_FSYS0, 10, CLK_IGNORE_UNUSED, 0),
>
> GATE(0, "aclk333_g2d", "mout_user_aclk333_g2d",
> GATE_BUS_TOP, 0, CLK_IGNORE_UNUSED, 0),
> GATE(0, "aclk266_g2d", "mout_user_aclk266_g2d",
> - GATE_BUS_TOP, 1, CLK_IGNORE_UNUSED, 0),
> + GATE_BUS_TOP, 1, CLK_IS_CRITICAL, 0),
> GATE(0, "aclk300_jpeg", "mout_user_aclk300_jpeg",
> GATE_BUS_TOP, 4, CLK_IGNORE_UNUSED, 0),
> GATE(0, "aclk333_432_isp0", "mout_user_aclk333_432_isp0",
> GATE_BUS_TOP, 5, 0, 0),
> GATE(0, "aclk300_gscl", "mout_user_aclk300_gscl",
> - GATE_BUS_TOP, 6, CLK_IGNORE_UNUSED, 0),
> + GATE_BUS_TOP, 6, CLK_IS_CRITICAL, 0),
> GATE(0, "aclk333_432_gscl", "mout_user_aclk333_432_gscl",
> GATE_BUS_TOP, 7, CLK_IGNORE_UNUSED, 0),
> GATE(0, "aclk333_432_isp", "mout_user_aclk333_432_isp",
> @@ -983,20 +983,20 @@ static void __init exynos5420_clk_sleep_init(void) {}
> GATE(0, "aclk166", "mout_user_aclk166",
> GATE_BUS_TOP, 14, CLK_IGNORE_UNUSED, 0),
> GATE(CLK_ACLK333, "aclk333", "mout_user_aclk333",
> - GATE_BUS_TOP, 15, CLK_IGNORE_UNUSED, 0),
> + GATE_BUS_TOP, 15, CLK_IS_CRITICAL, 0),
> GATE(0, "aclk400_isp", "mout_user_aclk400_isp",
> GATE_BUS_TOP, 16, 0, 0),
> GATE(0, "aclk400_mscl", "mout_user_aclk400_mscl",
> GATE_BUS_TOP, 17, 0, 0),
> GATE(0, "aclk200_disp1", "mout_user_aclk200_disp1",
> - GATE_BUS_TOP, 18, 0, 0),
> + GATE_BUS_TOP, 18, CLK_IS_CRITICAL, 0),
> GATE(CLK_SCLK_MPHY_IXTAL24, "sclk_mphy_ixtal24", "mphy_refclk_ixtal24",
> GATE_BUS_TOP, 28, 0, 0),
> GATE(CLK_SCLK_HSIC_12M, "sclk_hsic_12m", "ff_hsic_12m",
> GATE_BUS_TOP, 29, 0, 0),
>
> GATE(0, "aclk300_disp1", "mout_user_aclk300_disp1",
> - SRC_MASK_TOP2, 24, 0, 0),
> + SRC_MASK_TOP2, 24, CLK_IS_CRITICAL, 0),
>
> GATE(CLK_MAU_EPLL, "mau_epll", "mout_mau_epll_clk",
> SRC_MASK_TOP7, 20, 0, 0),
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] clk/samsung: exynos542x: mark some clocks as critical
2017-01-09 12:30 ` Sylwester Nawrocki
@ 2017-01-10 0:10 ` Stephen Boyd
0 siblings, 0 replies; 8+ messages in thread
From: Stephen Boyd @ 2017-01-10 0:10 UTC (permalink / raw)
To: Sylwester Nawrocki
Cc: Mike Turquette, Marek Szyprowski, linux-clk, linux-samsung-soc,
Krzysztof Kozlowski, Bartlomiej Zolnierkiewicz, Chanwoo Choi
On 01/09, Sylwester Nawrocki wrote:
> On 12/22/2016 10:44 AM, Marek Szyprowski wrote:
> > Some parent clocks of the Exynos542x clock blocks, which have separate
> > power domains (like DISP, MFC, MSC, GSC, FSYS and G2D) must be always
> > enabled to access any register related to power management unit or devices
> > connected to it. For the time being, until a proper solution based on
> > runtime PM is applied, mark those clocks as critical (instead of ignore
> > unused or even no flags) to prevent disabling them.
> >
> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>
> Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
>
> Stephen, Mike, could you apply the $subject patch directly? Due to recent
> Exynos IOMMU related changes that patch is needed as a regression fix
> for v4.10.
>
Sure, no problem.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] clk/samsung: exynos542x: mark some clocks as critical
2016-12-22 9:44 ` [PATCH] clk/samsung: exynos542x: mark some clocks as critical Marek Szyprowski
` (2 preceding siblings ...)
2017-01-09 12:30 ` Sylwester Nawrocki
@ 2017-01-10 0:11 ` Stephen Boyd
3 siblings, 0 replies; 8+ messages in thread
From: Stephen Boyd @ 2017-01-10 0:11 UTC (permalink / raw)
To: Marek Szyprowski
Cc: linux-clk, linux-samsung-soc, Sylwester Nawrocki,
Krzysztof Kozlowski, Bartlomiej Zolnierkiewicz, Chanwoo Choi
On 12/22, Marek Szyprowski wrote:
> Some parent clocks of the Exynos542x clock blocks, which have separate
> power domains (like DISP, MFC, MSC, GSC, FSYS and G2D) must be always
> enabled to access any register related to power management unit or devices
> connected to it. For the time being, until a proper solution based on
> runtime PM is applied, mark those clocks as critical (instead of ignore
> unused or even no flags) to prevent disabling them.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
Applied to clk-fixes
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
^ permalink raw reply [flat|nested] 8+ messages in thread