From: Xing Zheng <zhengxing@rock-chips.com>
To: Brian Norris <briannorris@chromium.org>
Cc: heiko@sntech.de, linux-rockchip@lists.infradead.org,
dianders@chromium.org, huangtao@rock-chips.com,
zhangqing@rock-chips.com,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2 4/8] clk: rockchip: rk3399: fix incorrect GATE bits for {c, g}pll_aclk_perihp_src
Date: Tue, 02 Aug 2016 11:09:16 +0800 [thread overview]
Message-ID: <57A00EDC.7090105@rock-chips.com> (raw)
In-Reply-To: <57A00D08.3070607@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 4674 bytes --]
On 2016?08?02? 11:01, Xing Zheng wrote:
> On 2016?08?02? 04:20, Brian Norris wrote:
>> On Mon, Aug 01, 2016 at 05:53:39PM +0800, Xing Zheng wrote:
>>> Sorry to refer incorrect clock diagram, we double check it that the
>>> bits configuration of the Xpll_aclk_perihp_src need to be fixed:
>>> bit 1 - shows aclk_perihp_cpll_src_en
>>> bit 0 - shows aclk_perihp_gpll_src_en
>> Last time, you confirmed with the IC designers that we had things right.
>> What's different this time? Have you, for instance, done more thorough
>> testing, to show that the logical parent structure this driver outputs
>> is actually what the hardware is doing?
> I tried to proof it throught the testing that plug/unplug the USB
> ethernet cable on kevin board.
>
> 1. the hclk_host0 and hclk_host1 are endpoint clocks.
> cpll --> G5[1] --> aclk_perihp_cpll_src --\ |-->
> hclk_host0
> | -->
> ... ---> |
> gpll --> G5[0] --> aclk_perihp_gpll_src --/ |-->
> hclk_host1
>
> 2. on the kevin, there is no clock below the cpll_aclk_perihp_src, and
> the hclk_hostX are below the gpll_aclk_perihp_src:
> pll_cpll 1 1
> 800000000 0 0
> cpll 7 19
> 800000000 0 0
> cpll_aclk_perihp_src 0 0
> 800000000 0 0
>
> ...
> pll_gpll 1 1
> 594000000 0 0
> gpll 10 10
> 594000000 0 0
> gpll_aclk_perihp_src 2 2
> 594000000 0 0
> hclk_perihp 5 5
> 74250000 0 0
> hclk_host1_arb 2 2
> 74250000 0 0
> hclk_host1 2 2
> 74250000 0 0
> hclk_host0_arb 2 2
> 74250000 0 0
> hclk_host0 2 2
> 74250000 0 0
>
> 3. by default, G5[0] and G5[1] are enabled:
> localhost ~ # mem r 0xff760314
> 0x000003e0
>
> 4. close the G5[1] (aclk_perihp_cpll_src), and plug/unplug USB
> ethernet cable, the DUT still works well:
> localhost ~ # mem w 0xff760314 0xffff03e2
> localhost ~ # mem r 0xff760314
> 0x000003e2
> plug/unplug ok
>
> 5. close the G5[0] (aclk_perihp_gpll_src), , and plug/unplug USB
> ethernet cable, the DUT will be crashed:
> localhost ~ # mem w 0xff760314 0xffff03e1
> localhost ~ # mem r 0xff760314
> 0x000003e1
> plug/unplug crashed
>
> Hence:
> bit 1 - shows aclk_perihp_cpll_src_en
> bit 0 - shows aclk_perihp_gpll_src_en
>
>> I think maybe this would qualify as:
>>
>> Fixes: 3bd14ae9da91 ("clk: rockchip: fix incorrect parent for rk3399's {c,g}pll_aclk_perihp_src")
>>
>> The above is not exactly a pure regression (we really want both
>> changes), but apparently it wasn't a complete fix.
> OK, I will add the commit message
> "Fixes: 3bd14ae9da91 ("clk: rockchip: fix incorrect parent for
> rk3399's {c,g}pll_aclk_perihp_src")"
> at next version.
>>> Signed-off-by: Xing Zheng<zhengxing@rock-chips.com>
>>> ---
>>>
>>> Changes in v2: None
>> Uhh, isn't this patch brand new in v2? I don't think that means
>> "Changes ... None".
> Yes, I will add change log into this patch at next version.
>
> Thanks.
Sorry to change my mind. This patch is only started to be added in
patchset_v2, not be included in my patchset_v1, so I think it should be
"Changes ... None".
Thanks.
>> Brian
>>
>>> 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 2182391..8bf0d19 100644
>>> --- a/drivers/clk/rockchip/clk-rk3399.c
>>> +++ b/drivers/clk/rockchip/clk-rk3399.c
>>> @@ -833,9 +833,9 @@ static struct rockchip_clk_branch rk3399_clk_branches[] __initdata = {
>>>
>>> /* perihp */
>>> GATE(0, "cpll_aclk_perihp_src", "cpll", CLK_IGNORE_UNUSED,
>>> - RK3399_CLKGATE_CON(5), 0, GFLAGS),
>>> - GATE(0, "gpll_aclk_perihp_src", "gpll", CLK_IGNORE_UNUSED,
>>> RK3399_CLKGATE_CON(5), 1, GFLAGS),
>>> + GATE(0, "gpll_aclk_perihp_src", "gpll", CLK_IGNORE_UNUSED,
>>> + RK3399_CLKGATE_CON(5), 0, GFLAGS),
>>> COMPOSITE(ACLK_PERIHP, "aclk_perihp", mux_aclk_perihp_p, CLK_IGNORE_UNUSED,
>>> RK3399_CLKSEL_CON(14), 7, 1, MFLAGS, 0, 5, DFLAGS,
>>> RK3399_CLKGATE_CON(5), 2, GFLAGS),
>>> --
>>> 1.7.9.5
>>>
>>>
>>
>
>
> --
> - Xing Zheng
--
- Xing Zheng
[-- Attachment #2: Type: text/html, Size: 11537 bytes --]
next prev parent reply other threads:[~2016-08-02 3:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 9:53 [RESEND PATCH v2 0/8] fix and optimize some clock configuration for the RK3399 platfom Xing Zheng
2016-08-01 9:53 ` [RESEND PATCH v2 2/8] clk: rockchip: rk3399: export 480M_SRC clock id for usbphy0/usbphy1 Xing Zheng
2016-08-01 9:53 ` [RESEND PATCH v2 3/8] clk: rockchip: rk3399: fix incorrect parent for rk3399's {c, g}pll_aclk_perihp_src Xing Zheng
2016-08-01 20:13 ` Brian Norris
2016-08-02 1:50 ` Xing Zheng
2016-08-01 9:53 ` [RESEND PATCH v2 4/8] clk: rockchip: rk3399: fix incorrect GATE bits for " Xing Zheng
2016-08-01 20:20 ` Brian Norris
2016-08-02 3:01 ` Xing Zheng
2016-08-02 3:09 ` Xing Zheng [this message]
2016-08-01 9:56 ` [RESEND PATCH v2 5/8] clk: rockchip: rk3399: fix incorrect aclk_emmc source gate bits Xing Zheng
2016-08-01 9:58 ` [RESEND PATCH v2 6/8] clk: rockchip: rk3399: add 65MHz and 106.5MHz clocks for HDMI Xing Zheng
2016-08-01 9:58 ` [RESEND PATCH v2 7/8] clk: rockchip: rk3399: delete the CLK_IGNORE_UNUSED for aclk_pcie Xing Zheng
2016-08-01 9:58 ` [RESEND PATCH v2 8/8] clk: rockchip: rk3399: Add support frac mode frequencies Xing Zheng
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=57A00EDC.7090105@rock-chips.com \
--to=zhengxing@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=zhangqing@rock-chips.com \
/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