From: Xing Zheng <zhengxing@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, huangtao@rock-chips.com,
jay.xu@rock-chips.com, elaine.zhang@rock-chips.com,
dianders@chromium.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 4/4] clk: rockchip: add clock controller for the RK3399
Date: Mon, 28 Mar 2016 14:11:13 +0800 [thread overview]
Message-ID: <56F8CB01.2070709@rock-chips.com> (raw)
In-Reply-To: <9181730.v9nyazlRXy@phil>
Hi Heiko,
On 2016年03月28日 08:13, Heiko Stuebner wrote:
> Hi Xing,
>
> Am Samstag, 26. März 2016, 14:37:56 schrieb Xing Zheng:
>> Add the clock tree definition for the new RK3399 SoC.
>>
>> Signed-off-by: Xing Zheng<zhengxing@rock-chips.com>
>> ---
> [...]
>
>> + /*
>> + * We use pclkin_cifinv by default GRF_SOC_CON20[9] (GSC20_9) setting in
>> system, + * so we ignore the mux and make clocks nodes as following,
>> + *
>> + * pclkin_cifinv --|-------\
>> + * |GSC20_9|-- pclkin_cifmux
>> + * pclkin_cif --|-------/
>> + */
>> + GATE(PCLK_ISP1_WRAPPER, "pclkin_isp1_wrapper", "pclkin_cifmux",
> please name that source clock pclkin_cif as in the TRM.
> pclkin_cif is the actual input clock - if I'm reading the TRM correctly and
> the inverter is part of the soc or so?
>
> That we currently hide / hardcode the phase-handling should not be part of
> our outside connection - which should be stable even if we implement this
> later.
>
>
Yes, I think I will modify them like this:
GATE(PCLK_ISP1_WRAPPER, "pclkin_isp1_wrapper", "pclkin_cif",
CLK_IGNORE_UNUSED,
RK3399_CLKGATE_CON(27), 6, GFLAGS),
Thanks.
--
- Xing Zheng
WARNING: multiple messages have this Message-ID (diff)
From: zhengxing@rock-chips.com (Xing Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/4] clk: rockchip: add clock controller for the RK3399
Date: Mon, 28 Mar 2016 14:11:13 +0800 [thread overview]
Message-ID: <56F8CB01.2070709@rock-chips.com> (raw)
In-Reply-To: <9181730.v9nyazlRXy@phil>
Hi Heiko,
On 2016?03?28? 08:13, Heiko Stuebner wrote:
> Hi Xing,
>
> Am Samstag, 26. M?rz 2016, 14:37:56 schrieb Xing Zheng:
>> Add the clock tree definition for the new RK3399 SoC.
>>
>> Signed-off-by: Xing Zheng<zhengxing@rock-chips.com>
>> ---
> [...]
>
>> + /*
>> + * We use pclkin_cifinv by default GRF_SOC_CON20[9] (GSC20_9) setting in
>> system, + * so we ignore the mux and make clocks nodes as following,
>> + *
>> + * pclkin_cifinv --|-------\
>> + * |GSC20_9|-- pclkin_cifmux
>> + * pclkin_cif --|-------/
>> + */
>> + GATE(PCLK_ISP1_WRAPPER, "pclkin_isp1_wrapper", "pclkin_cifmux",
> please name that source clock pclkin_cif as in the TRM.
> pclkin_cif is the actual input clock - if I'm reading the TRM correctly and
> the inverter is part of the soc or so?
>
> That we currently hide / hardcode the phase-handling should not be part of
> our outside connection - which should be stable even if we implement this
> later.
>
>
Yes, I think I will modify them like this:
GATE(PCLK_ISP1_WRAPPER, "pclkin_isp1_wrapper", "pclkin_cif",
CLK_IGNORE_UNUSED,
RK3399_CLKGATE_CON(27), 6, GFLAGS),
Thanks.
--
- Xing Zheng
next prev parent reply other threads:[~2016-03-28 6:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 6:37 [PATCH v5 0/4] Add more clock compatible features and support the RK3399 clock Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 6:37 ` [PATCH v5 1/4] clk: rockchip: fix big.LITTLE cores alternate reparent failed Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 8:26 ` kbuild test robot
2016-03-26 8:26 ` kbuild test robot
2016-03-26 8:26 ` kbuild test robot
2016-03-27 21:26 ` Heiko Stübner
2016-03-27 21:26 ` Heiko Stübner
2016-03-27 21:26 ` Heiko Stübner
[not found] ` <1458974276-10325-1-git-send-email-zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-03-26 6:37 ` [PATCH v5 2/4] dt-bindings: add bindings for rk3399 clock controller Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 6:37 ` Xing Zheng
[not found] ` <1458974276-10325-3-git-send-email-zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-03-27 23:52 ` Heiko Stübner
2016-03-27 23:52 ` Heiko Stübner
2016-03-27 23:52 ` Heiko Stübner
2016-03-28 0:07 ` Heiko Stuebner
2016-03-28 0:07 ` Heiko Stuebner
2016-03-28 3:24 ` Xing Zheng
2016-03-28 3:24 ` Xing Zheng
2016-03-28 3:24 ` Xing Zheng
2016-03-28 2:51 ` Xing Zheng
2016-03-28 2:51 ` Xing Zheng
2016-03-26 6:37 ` [PATCH v5 3/4] clk: rockchip: add dt-binding header for rk3399 Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 6:37 ` [PATCH v5 4/4] clk: rockchip: add clock controller for the RK3399 Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 8:41 ` kbuild test robot
2016-03-26 8:41 ` kbuild test robot
2016-03-26 8:41 ` kbuild test robot
2016-03-28 0:13 ` Heiko Stuebner
2016-03-28 0:13 ` Heiko Stuebner
2016-03-28 0:13 ` Heiko Stuebner
2016-03-28 6:11 ` Xing Zheng [this message]
2016-03-28 6:11 ` 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=56F8CB01.2070709@rock-chips.com \
--to=zhengxing@rock-chips.com \
--cc=dianders@chromium.org \
--cc=elaine.zhang@rock-chips.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.