From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: mark rk3399 hdcp_noc and pclk_vio_grf as critical
Date: Fri, 05 Aug 2016 13:02:48 +0200 [thread overview]
Message-ID: <4055149.Zs66lEhv2I@diego> (raw)
In-Reply-To: <1470209784-2665-1-git-send-email-zyw@rock-chips.com>
Hi Chris,
Am Mittwoch, 3. August 2016, 15:36:24 schrieb Chris Zhong:
> The Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc,
> pclk_hdcp_noc, pclk_vio_grf. Mark them as critical to avoid someone
> close them.
>
> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
>
> ---
>
> drivers/clk/rockchip/clk-rk3399.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/clk/rockchip/clk-rk3399.c
> b/drivers/clk/rockchip/clk-rk3399.c index 78e51cb..6c8ed25 100644
> --- a/drivers/clk/rockchip/clk-rk3399.c
> +++ b/drivers/clk/rockchip/clk-rk3399.c
> @@ -1466,6 +1466,9 @@ static struct rockchip_clk_branch
> rk3399_clk_pmu_branches[] __initdata = {
>
> static const char *const rk3399_cru_critical_clocks[] __initconst = {
> "aclk_cci_pre",
> + "aclk_hdcp_noc",
> + "hclk_hdcp_noc",
> + "pclk_hdcp_noc",
> "pclk_perilp0",
> "pclk_perilp0",
> "hclk_perilp0",
ok, we have marked all other noc (interconnect) clocks as critical, so this
looks good.
> @@ -1485,6 +1488,7 @@ static const char *const rk3399_cru_critical_clocks[]
> __initconst = { "gpll_hclk_perilp1_src",
> "gpll_aclk_perilp0_src",
> "gpll_aclk_perihp_src",
> + "pclk_vio_grf",
I don't necessarily agree with this one. It seems for the analogix-dp the
preferred way is to have the driver handle its needed clock, see
"[PATCH v1 6/6] drm/rockchip: dw_hdmi: introduce the pclk for grf" [0]
Heiko
[0] https://patchwork.kernel.org/patch/9223331/
prev parent reply other threads:[~2016-08-05 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 7:36 [PATCH] clk: rockchip: mark rk3399 hdcp_noc and pclk_vio_grf as critical Chris Zhong
2016-08-05 11:02 ` Heiko Stübner [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=4055149.Zs66lEhv2I@diego \
--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;
as well as URLs for NNTP newsgroup(s).