* [v2 PATCH] clk: rockchip: mark rk3399 hdcp_noc and vio_noc as critical
@ 2016-08-10 22:14 ` Guenter Roeck
0 siblings, 0 replies; 13+ messages in thread
From: Guenter Roeck @ 2016-08-10 22:14 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Aug 9, 2016 at 11:02 AM, Chris Zhong <zyw@rock-chips.com> wrote:
> Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With
> this modification, the aclk_vio_noc should be put into critical list,
> since it is required by VOP.
> And the Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc,
> pclk_hdcp_noc. Mark them as critical to avoid someone close them.
>
> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
> ---
>
> drivers/clk/rockchip/clk-rk3399.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c
> index b173711a..676b017 100644
> --- a/drivers/clk/rockchip/clk-rk3399.c
> +++ b/drivers/clk/rockchip/clk-rk3399.c
> @@ -1073,7 +1073,7 @@ static struct rockchip_clk_branch rk3399_clk_branches[] __initdata = {
> /* vio */
> COMPOSITE(ACLK_VIO, "aclk_vio", mux_pll_src_cpll_gpll_ppll_p, CLK_IGNORE_UNUSED,
> RK3399_CLKSEL_CON(42), 6, 2, MFLAGS, 0, 5, DFLAGS,
> - RK3399_CLKGATE_CON(11), 10, GFLAGS),
> + RK3399_CLKGATE_CON(11), 0, GFLAGS),
> COMPOSITE_NOMUX(PCLK_VIO, "pclk_vio", "aclk_vio", 0,
> RK3399_CLKSEL_CON(43), 0, 5, DFLAGS,
> RK3399_CLKGATE_CON(11), 1, GFLAGS),
> @@ -1470,6 +1470,9 @@ static const char *const rk3399_cru_critical_clocks[] __initconst = {
> "aclk_cci_pre",
> "aclk_gic",
> "aclk_gic_noc",
> + "aclk_hdcp_noc",
> + "hclk_hdcp_noc",
> + "pclk_hdcp_noc",
> "pclk_perilp0",
> "pclk_perilp0",
> "hclk_perilp0",
> @@ -1489,6 +1492,7 @@ static const char *const rk3399_cru_critical_clocks[] __initconst = {
> "gpll_hclk_perilp1_src",
> "gpll_aclk_perilp0_src",
> "gpll_aclk_perihp_src",
> + "aclk_vio_noc",
I think there was a previous comment suggesting that this clock should
be handled differently. Has this been resolved ?
Otherwise
Reviewed-by: Guenter Roeck <groeck@chromium.org>
> };
>
> static const char *const rk3399_pmucru_critical_clocks[] __initconst = {
> --
> 1.9.1
>
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: [v2 PATCH] clk: rockchip: mark rk3399 hdcp_noc and vio_noc as critical
@ 2016-08-11 2:31 ` Xing Zheng
0 siblings, 0 replies; 13+ messages in thread
From: Xing Zheng @ 2016-08-11 2:31 UTC (permalink / raw)
To: Guenter Roeck, Chris Zhong
Cc: Heiko Stübner, 姚智情, mturquette, sboyd,
linux-kernel, Tomasz Figa, open list:ARM/Rockchip SoC...,
Douglas Anderson, Guenter Roeck, Stéphane Marchesin, wulf,
linux-clk, linux-arm-kernel
Chris,
On 2016年08月11日 06:14, Guenter Roeck wrote:
> On Tue, Aug 9, 2016 at 11:02 AM, Chris Zhong <zyw@rock-chips.com> wrote:
>> Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With
>> this modification, the aclk_vio_noc should be put into critical list,
>> since it is required by VOP.
>> And the Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc,
>> pclk_hdcp_noc. Mark them as critical to avoid someone close them.
>>
>> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
>> ---
>>
>> drivers/clk/rockchip/clk-rk3399.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c
>> index b173711a..676b017 100644
>> --- a/drivers/clk/rockchip/clk-rk3399.c
>> +++ b/drivers/clk/rockchip/clk-rk3399.c
>> @@ -1073,7 +1073,7 @@ static struct rockchip_clk_branch rk3399_clk_branches[] __initdata = {
>> /* vio */
>> COMPOSITE(ACLK_VIO, "aclk_vio", mux_pll_src_cpll_gpll_ppll_p, CLK_IGNORE_UNUSED,
>> RK3399_CLKSEL_CON(42), 6, 2, MFLAGS, 0, 5, DFLAGS,
>> - RK3399_CLKGATE_CON(11), 10, GFLAGS),
>> + RK3399_CLKGATE_CON(11), 0, GFLAGS),
Sorry to broken copy&paste, thanks to fix the incorrect bit.
Reviewed-by: Xing Zheng <zhengxing@rock-chips.com>
Thanks.
>> COMPOSITE_NOMUX(PCLK_VIO, "pclk_vio", "aclk_vio", 0,
>> RK3399_CLKSEL_CON(43), 0, 5, DFLAGS,
>> RK3399_CLKGATE_CON(11), 1, GFLAGS),
>> @@ -1470,6 +1470,9 @@ static const char *const rk3399_cru_critical_clocks[] __initconst = {
>> "aclk_cci_pre",
>> "aclk_gic",
>> "aclk_gic_noc",
>> + "aclk_hdcp_noc",
>> + "hclk_hdcp_noc",
>> + "pclk_hdcp_noc",
>> "pclk_perilp0",
>> "pclk_perilp0",
>> "hclk_perilp0",
>> @@ -1489,6 +1492,7 @@ static const char *const rk3399_cru_critical_clocks[] __initconst = {
>> "gpll_hclk_perilp1_src",
>> "gpll_aclk_perilp0_src",
>> "gpll_aclk_perihp_src",
>> + "aclk_vio_noc",
> I think there was a previous comment suggesting that this clock should
> be handled differently. Has this been resolved ?
>
> Otherwise
>
> Reviewed-by: Guenter Roeck <groeck@chromium.org>
>
>> };
>>
>> static const char *const rk3399_pmucru_critical_clocks[] __initconst = {
>> --
>> 1.9.1
>>
>
>
--
- Xing Zheng
^ permalink raw reply [flat|nested] 13+ messages in thread* [v2 PATCH] clk: rockchip: mark rk3399 hdcp_noc and vio_noc as critical
@ 2016-08-11 2:31 ` Xing Zheng
0 siblings, 0 replies; 13+ messages in thread
From: Xing Zheng @ 2016-08-11 2:31 UTC (permalink / raw)
To: linux-arm-kernel
Chris,
On 2016?08?11? 06:14, Guenter Roeck wrote:
> On Tue, Aug 9, 2016 at 11:02 AM, Chris Zhong <zyw@rock-chips.com> wrote:
>> Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With
>> this modification, the aclk_vio_noc should be put into critical list,
>> since it is required by VOP.
>> And the Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc,
>> pclk_hdcp_noc. Mark them as critical to avoid someone close them.
>>
>> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
>> ---
>>
>> drivers/clk/rockchip/clk-rk3399.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c
>> index b173711a..676b017 100644
>> --- a/drivers/clk/rockchip/clk-rk3399.c
>> +++ b/drivers/clk/rockchip/clk-rk3399.c
>> @@ -1073,7 +1073,7 @@ static struct rockchip_clk_branch rk3399_clk_branches[] __initdata = {
>> /* vio */
>> COMPOSITE(ACLK_VIO, "aclk_vio", mux_pll_src_cpll_gpll_ppll_p, CLK_IGNORE_UNUSED,
>> RK3399_CLKSEL_CON(42), 6, 2, MFLAGS, 0, 5, DFLAGS,
>> - RK3399_CLKGATE_CON(11), 10, GFLAGS),
>> + RK3399_CLKGATE_CON(11), 0, GFLAGS),
Sorry to broken copy&paste, thanks to fix the incorrect bit.
Reviewed-by: Xing Zheng <zhengxing@rock-chips.com>
Thanks.
>> COMPOSITE_NOMUX(PCLK_VIO, "pclk_vio", "aclk_vio", 0,
>> RK3399_CLKSEL_CON(43), 0, 5, DFLAGS,
>> RK3399_CLKGATE_CON(11), 1, GFLAGS),
>> @@ -1470,6 +1470,9 @@ static const char *const rk3399_cru_critical_clocks[] __initconst = {
>> "aclk_cci_pre",
>> "aclk_gic",
>> "aclk_gic_noc",
>> + "aclk_hdcp_noc",
>> + "hclk_hdcp_noc",
>> + "pclk_hdcp_noc",
>> "pclk_perilp0",
>> "pclk_perilp0",
>> "hclk_perilp0",
>> @@ -1489,6 +1492,7 @@ static const char *const rk3399_cru_critical_clocks[] __initconst = {
>> "gpll_hclk_perilp1_src",
>> "gpll_aclk_perilp0_src",
>> "gpll_aclk_perihp_src",
>> + "aclk_vio_noc",
> I think there was a previous comment suggesting that this clock should
> be handled differently. Has this been resolved ?
>
> Otherwise
>
> Reviewed-by: Guenter Roeck <groeck@chromium.org>
>
>> };
>>
>> static const char *const rk3399_pmucru_critical_clocks[] __initconst = {
>> --
>> 1.9.1
>>
>
>
--
- Xing Zheng
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: [v2 PATCH] clk: rockchip: mark rk3399 hdcp_noc and vio_noc as critical
@ 2016-08-11 2:31 ` Xing Zheng
0 siblings, 0 replies; 13+ messages in thread
From: Xing Zheng @ 2016-08-11 2:31 UTC (permalink / raw)
To: Guenter Roeck, Chris Zhong
Cc: Douglas Anderson, Heiko Stübner, 姚智情,
mturquette-rdvid1DuHRBWk0Htik3J/w, sboyd-sgV2jX0FEOL9JmXXK+q4OQ,
linux-kernel, Tomasz Figa, open list:ARM/Rockchip SoC..., wulf,
Guenter Roeck, Stéphane Marchesin,
linux-clk-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
Chris,
On 2016年08月11日 06:14, Guenter Roeck wrote:
> On Tue, Aug 9, 2016 at 11:02 AM, Chris Zhong <zyw@rock-chips.com> wrote:
>> Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With
>> this modification, the aclk_vio_noc should be put into critical list,
>> since it is required by VOP.
>> And the Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc,
>> pclk_hdcp_noc. Mark them as critical to avoid someone close them.
>>
>> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
>> ---
>>
>> drivers/clk/rockchip/clk-rk3399.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c
>> index b173711a..676b017 100644
>> --- a/drivers/clk/rockchip/clk-rk3399.c
>> +++ b/drivers/clk/rockchip/clk-rk3399.c
>> @@ -1073,7 +1073,7 @@ static struct rockchip_clk_branch rk3399_clk_branches[] __initdata = {
>> /* vio */
>> COMPOSITE(ACLK_VIO, "aclk_vio", mux_pll_src_cpll_gpll_ppll_p, CLK_IGNORE_UNUSED,
>> RK3399_CLKSEL_CON(42), 6, 2, MFLAGS, 0, 5, DFLAGS,
>> - RK3399_CLKGATE_CON(11), 10, GFLAGS),
>> + RK3399_CLKGATE_CON(11), 0, GFLAGS),
Sorry to broken copy&paste, thanks to fix the incorrect bit.
Reviewed-by: Xing Zheng <zhengxing@rock-chips.com>
Thanks.
>> COMPOSITE_NOMUX(PCLK_VIO, "pclk_vio", "aclk_vio", 0,
>> RK3399_CLKSEL_CON(43), 0, 5, DFLAGS,
>> RK3399_CLKGATE_CON(11), 1, GFLAGS),
>> @@ -1470,6 +1470,9 @@ static const char *const rk3399_cru_critical_clocks[] __initconst = {
>> "aclk_cci_pre",
>> "aclk_gic",
>> "aclk_gic_noc",
>> + "aclk_hdcp_noc",
>> + "hclk_hdcp_noc",
>> + "pclk_hdcp_noc",
>> "pclk_perilp0",
>> "pclk_perilp0",
>> "hclk_perilp0",
>> @@ -1489,6 +1492,7 @@ static const char *const rk3399_cru_critical_clocks[] __initconst = {
>> "gpll_hclk_perilp1_src",
>> "gpll_aclk_perilp0_src",
>> "gpll_aclk_perihp_src",
>> + "aclk_vio_noc",
> I think there was a previous comment suggesting that this clock should
> be handled differently. Has this been resolved ?
>
> Otherwise
>
> Reviewed-by: Guenter Roeck <groeck@chromium.org>
>
>> };
>>
>> static const char *const rk3399_pmucru_critical_clocks[] __initconst = {
>> --
>> 1.9.1
>>
>
>
--
- Xing Zheng
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [v2 PATCH] clk: rockchip: mark rk3399 hdcp_noc and vio_noc as critical
2016-08-10 22:14 ` Guenter Roeck
@ 2016-08-11 7:07 ` Heiko Stübner
-1 siblings, 0 replies; 13+ messages in thread
From: Heiko Stübner @ 2016-08-11 7:07 UTC (permalink / raw)
To: Guenter Roeck
Cc: Chris Zhong, Xing Zheng, 姚智情, mturquette,
sboyd, linux-kernel, Tomasz Figa, open list:ARM/Rockchip SoC...,
Douglas Anderson, Guenter Roeck, Stéphane Marchesin, wulf,
linux-clk, linux-arm-kernel
Am Mittwoch, 10. August 2016, 15:14:06 schrieb Guenter Roeck:
> On Tue, Aug 9, 2016 at 11:02 AM, Chris Zhong <zyw@rock-chips.com> wrote:
> > Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With
> > this modification, the aclk_vio_noc should be put into critical list,
> > since it is required by VOP.
> > And the Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc,
> > pclk_hdcp_noc. Mark them as critical to avoid someone close them.
> >
> > Signed-off-by: Chris Zhong <zyw@rock-chips.com>
> > ---
> >
> > drivers/clk/rockchip/clk-rk3399.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/clk/rockchip/clk-rk3399.c
> > b/drivers/clk/rockchip/clk-rk3399.c index b173711a..676b017 100644
> > --- a/drivers/clk/rockchip/clk-rk3399.c
> > +++ b/drivers/clk/rockchip/clk-rk3399.c
> > @@ -1073,7 +1073,7 @@ static struct rockchip_clk_branch
> > rk3399_clk_branches[] __initdata = {>
> > /* vio */
> > COMPOSITE(ACLK_VIO, "aclk_vio", mux_pll_src_cpll_gpll_ppll_p,
> > CLK_IGNORE_UNUSED,>
> > RK3399_CLKSEL_CON(42), 6, 2, MFLAGS, 0, 5, DFLAGS,
> >
> > - RK3399_CLKGATE_CON(11), 10, GFLAGS),
> > + RK3399_CLKGATE_CON(11), 0, GFLAGS),
> >
> > COMPOSITE_NOMUX(PCLK_VIO, "pclk_vio", "aclk_vio", 0,
> >
> > RK3399_CLKSEL_CON(43), 0, 5, DFLAGS,
> > RK3399_CLKGATE_CON(11), 1, GFLAGS),
> >
> > @@ -1470,6 +1470,9 @@ static const char *const
> > rk3399_cru_critical_clocks[] __initconst = {>
> > "aclk_cci_pre",
> > "aclk_gic",
> > "aclk_gic_noc",
> >
> > + "aclk_hdcp_noc",
> > + "hclk_hdcp_noc",
> > + "pclk_hdcp_noc",
> >
> > "pclk_perilp0",
> > "pclk_perilp0",
> > "hclk_perilp0",
> >
> > @@ -1489,6 +1492,7 @@ static const char *const
> > rk3399_cru_critical_clocks[] __initconst = {>
> > "gpll_hclk_perilp1_src",
> > "gpll_aclk_perilp0_src",
> > "gpll_aclk_perihp_src",
> >
> > + "aclk_vio_noc",
>
> I think there was a previous comment suggesting that this clock should
> be handled differently. Has this been resolved ?
The clock getting handled differently was pclk_grf_vio - aka the GRF part
needed. This one is the interconnect clock of the vio port (as far as I
understand that), which we currently don't model at all.
But if we did it would probably handled in some new part but not in the
graphics drivers.
So all looks well like it is here :-)
Heiko
^ permalink raw reply [flat|nested] 13+ messages in thread* [v2 PATCH] clk: rockchip: mark rk3399 hdcp_noc and vio_noc as critical
@ 2016-08-11 7:07 ` Heiko Stübner
0 siblings, 0 replies; 13+ messages in thread
From: Heiko Stübner @ 2016-08-11 7:07 UTC (permalink / raw)
To: linux-arm-kernel
Am Mittwoch, 10. August 2016, 15:14:06 schrieb Guenter Roeck:
> On Tue, Aug 9, 2016 at 11:02 AM, Chris Zhong <zyw@rock-chips.com> wrote:
> > Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With
> > this modification, the aclk_vio_noc should be put into critical list,
> > since it is required by VOP.
> > And the Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc,
> > pclk_hdcp_noc. Mark them as critical to avoid someone close them.
> >
> > Signed-off-by: Chris Zhong <zyw@rock-chips.com>
> > ---
> >
> > drivers/clk/rockchip/clk-rk3399.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/clk/rockchip/clk-rk3399.c
> > b/drivers/clk/rockchip/clk-rk3399.c index b173711a..676b017 100644
> > --- a/drivers/clk/rockchip/clk-rk3399.c
> > +++ b/drivers/clk/rockchip/clk-rk3399.c
> > @@ -1073,7 +1073,7 @@ static struct rockchip_clk_branch
> > rk3399_clk_branches[] __initdata = {>
> > /* vio */
> > COMPOSITE(ACLK_VIO, "aclk_vio", mux_pll_src_cpll_gpll_ppll_p,
> > CLK_IGNORE_UNUSED,>
> > RK3399_CLKSEL_CON(42), 6, 2, MFLAGS, 0, 5, DFLAGS,
> >
> > - RK3399_CLKGATE_CON(11), 10, GFLAGS),
> > + RK3399_CLKGATE_CON(11), 0, GFLAGS),
> >
> > COMPOSITE_NOMUX(PCLK_VIO, "pclk_vio", "aclk_vio", 0,
> >
> > RK3399_CLKSEL_CON(43), 0, 5, DFLAGS,
> > RK3399_CLKGATE_CON(11), 1, GFLAGS),
> >
> > @@ -1470,6 +1470,9 @@ static const char *const
> > rk3399_cru_critical_clocks[] __initconst = {>
> > "aclk_cci_pre",
> > "aclk_gic",
> > "aclk_gic_noc",
> >
> > + "aclk_hdcp_noc",
> > + "hclk_hdcp_noc",
> > + "pclk_hdcp_noc",
> >
> > "pclk_perilp0",
> > "pclk_perilp0",
> > "hclk_perilp0",
> >
> > @@ -1489,6 +1492,7 @@ static const char *const
> > rk3399_cru_critical_clocks[] __initconst = {>
> > "gpll_hclk_perilp1_src",
> > "gpll_aclk_perilp0_src",
> > "gpll_aclk_perihp_src",
> >
> > + "aclk_vio_noc",
>
> I think there was a previous comment suggesting that this clock should
> be handled differently. Has this been resolved ?
The clock getting handled differently was pclk_grf_vio - aka the GRF part
needed. This one is the interconnect clock of the vio port (as far as I
understand that), which we currently don't model at all.
But if we did it would probably handled in some new part but not in the
graphics drivers.
So all looks well like it is here :-)
Heiko
^ permalink raw reply [flat|nested] 13+ messages in thread