[PATCH] clk: rockchip: assign correct id for pclk_ddr and hclk_sd in rk3399
Shawn Lin
shawn.lin at rock-chips.com
Thu Mar 15 06:40:16 PDT 2018
[Correct Doug's email address]
On 2018/3/15 17:12, hl wrote:
> Hi Shawn,
>
>
> On Thursday, March 15, 2018 05:01 PM, Shawn Lin wrote:
>> Hi Huang,
>>
>> On 2018/3/15 16:54, Lin Huang wrote:
>>> Assign id PCLK_DDR to pclk_ddr, id HCLK_SD to hclk_sd, so we can
>>> assign frequency for them in dts.
>>
>> I'm curious under which condition that we need assign frequency for
>> hclk_sd?
> We may set CPLL frequency higher than 800MHz, with that we need assign
> clock
> to hclk_sd, otherwise it will exceed 200MHz, since we use the default
> cru register value to get hclk_sd for now.
> you can check
> https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/956678/5
>
Okay, thanks for pointing me to the actual user case.
I'm fine with that, however, what I am thinking now is:
(1) It's worth elaborating more in the commit msg.
(2) The reason you need set hclk_sd is that it depends on the
defualt settings but lack real owner to explicitly set it to <=200MHz.
So my another question is if that is more about aspect of power
consumption, then it looks okay to me. But if that is a SoC limitation,
then we are under risk for that. Either we should never rely on the
default settings, or we should set its rate range after registering this
clock provider.
Of course, I'm not a clk expert, but just want to learn more bits
from you guys. :)
>>
>>>
>>> Change-Id: I6c4d15d37ddabe4ed34e2351cf26e660672ae9ee
>>> Signed-off-by: Lin Huang <hl at rock-chips.com>
>>> ---
>>> drivers/clk/rockchip/clk-rk3399.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/clk/rockchip/clk-rk3399.c
>>> b/drivers/clk/rockchip/clk-rk3399.c
>>> index 6847120..a29c99e 100644
>>> --- a/drivers/clk/rockchip/clk-rk3399.c
>>> +++ b/drivers/clk/rockchip/clk-rk3399.c
>>> @@ -670,7 +670,7 @@ static struct rockchip_clk_branch
>>> rk3399_clk_branches[] __initdata = {
>>> RK3399_CLKGATE_CON(9), 7, GFLAGS,
>>> &rk3399_uart3_fracmux),
>>> - COMPOSITE(0, "pclk_ddr", mux_pll_src_cpll_gpll_p,
>>> CLK_IGNORE_UNUSED,
>>> + COMPOSITE(PCLK_DDR, "pclk_ddr", mux_pll_src_cpll_gpll_p,
>>> CLK_IGNORE_UNUSED,
>>> RK3399_CLKSEL_CON(6), 15, 1, MFLAGS, 8, 5, DFLAGS,
>>> RK3399_CLKGATE_CON(3), 4, GFLAGS),
>>> @@ -886,7 +886,7 @@ static struct rockchip_clk_branch
>>> rk3399_clk_branches[] __initdata = {
>>> RK3399_CLKGATE_CON(31), 8, GFLAGS),
>>> /* sdio & sdmmc */
>>> - COMPOSITE(0, "hclk_sd", mux_pll_src_cpll_gpll_p, 0,
>>> + COMPOSITE(HCLK_SD, "hclk_sd", mux_pll_src_cpll_gpll_p, 0,
>>> RK3399_CLKSEL_CON(13), 15, 1, MFLAGS, 8, 5, DFLAGS,
>>> RK3399_CLKGATE_CON(12), 13, GFLAGS),
>>> GATE(HCLK_SDMMC, "hclk_sdmmc", "hclk_sd", 0,
>>>
>>
>>
>>
>
>
>
>
--
Best Regards
Shawn Lin
More information about the Linux-rockchip
mailing list