From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] clk: rockchip: rk3228: make noc and some special clk as critical_clocks
Date: Tue, 28 Mar 2017 22:08:13 +0200 [thread overview]
Message-ID: <3534897.Tc49fhGY27@phil> (raw)
In-Reply-To: <1490695614-3220-3-git-send-email-zhangqing@rock-chips.com>
Hi Elaine,
Am Dienstag, 28. M?rz 2017, 18:06:52 CEST schrieb Elaine Zhang:
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
I really do expect a commit message explaining why the specific clocks
are needed to be critical.
The noc and arbiter clocks I somewhat understand, but I'll need
explanation on clocks like hclk_otg_pmu, hclk_otg_pmu _etc_ [all these
non-noc / non-arbi clocks] on why there is no driver to handle them.
Also please group noc / arbi clocks together.
This applies to all patches in this series.
Thanks
Heiko
> ---
> drivers/clk/rockchip/clk-rk3228.c | 30 +++++++++++++++++++++++++++++-
> 1 file changed, 29 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clk/rockchip/clk-rk3228.c b/drivers/clk/rockchip/clk-rk3228.c
> index db6e5a9e6de6..4d3203f887e2 100644
> --- a/drivers/clk/rockchip/clk-rk3228.c
> +++ b/drivers/clk/rockchip/clk-rk3228.c
> @@ -445,7 +445,7 @@ enum rk3228_plls {
> RK2928_CLKGATE_CON(2), 12, GFLAGS,
> &rk3228_spdif_fracmux),
>
> - GATE(0, "jtag", "ext_jtag", 0,
> + GATE(0, "jtag", "ext_jtag", CLK_IGNORE_UNUSED,
> RK2928_CLKGATE_CON(1), 3, GFLAGS),
>
> GATE(0, "sclk_otgphy0", "xin24m", 0,
> @@ -644,9 +644,37 @@ enum rk3228_plls {
>
> static const char *const rk3228_critical_clocks[] __initconst = {
> "aclk_cpu",
> + "pclk_cpu",
> + "hclk_cpu",
> "aclk_peri",
> "hclk_peri",
> "pclk_peri",
> + "aclk_rga_noc",
> + "aclk_iep_noc",
> + "aclk_vop_noc",
> + "aclk_hdcp_noc",
> + "hclk_vio_ahb_arbi",
> + "hclk_vio_noc",
> + "hclk_vop_noc",
> + "hclk_host0_arb",
> + "hclk_host1_arb",
> + "hclk_host2_arb",
> + "hclk_otg_pmu",
> + "aclk_gpu_noc",
> + "sclk_initmem_mbist",
> + "aclk_initmem",
> + "hclk_rom",
> + "pclk_ddrupctl",
> + "pclk_ddrmon",
> + "pclk_msch_noc",
> + "pclk_stimer",
> + "pclk_ddrphy",
> + "pclk_acodecphy",
> + "pclk_phy_noc",
> + "aclk_vpu_noc",
> + "aclk_rkvdec_noc",
> + "hclk_vpu_noc",
> + "hclk_rkvdec_noc",
> };
>
> static void __init rk3228_clk_init(struct device_node *np)
>
next prev parent reply other threads:[~2017-03-28 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 10:06 [PATCH v2 0/4] make some special clk as critical_clocks Elaine Zhang
2017-03-28 10:06 ` [PATCH v2 1/4] clk: rockchip: rk3036: make pclk_ddrupctl as critical_clock Elaine Zhang
2017-03-28 10:06 ` [PATCH v2 2/4] clk: rockchip: rk3228: make noc and some special clk as critical_clocks Elaine Zhang
2017-03-28 20:08 ` Heiko Stuebner [this message]
2017-03-30 12:44 ` Maxime Ripard
2017-03-30 13:10 ` Heiko Stuebner
2017-03-30 13:19 ` Maxime Ripard
2017-03-28 10:06 ` [PATCH v2 3/4] clk: rockchip: rk3288: " Elaine Zhang
2017-03-28 10:06 ` [PATCH v2 4/4] clk: rockchip: rk3368: make " Elaine Zhang
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=3534897.Tc49fhGY27@phil \
--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).