From: Xing Zheng <zhengxing@rock-chips.com>
To: Jianqun Xu <jay.xu@rock-chips.com>,
Doug Anderson <dianders@chromium.org>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Tao Huang" <huangtao@rock-chips.com>,
elaine.zhang@rock-chips.com
Subject: Re: [RESEND PATCH v2 5/5] clk: rockchip: add clock controller for the RK3399
Date: Wed, 9 Mar 2016 09:26:34 +0800 [thread overview]
Message-ID: <56DF7BCA.3000900@rock-chips.com> (raw)
In-Reply-To: <56DF7393.4020600@rock-chips.com>
Hi Doug,
Yes, I will resend my patch series include the previous patches
(header file and dt-bindings) of the Jianqun, and update the header file
for the MMC defines.
Thanks.
On 2016年03月09日 08:51, Jianqun Xu wrote:
> Hi Doug:
>
> 在 09/03/2016 07:34, Doug Anderson 写道:
>> Xing Zheng,
>>
>> On Tue, Mar 1, 2016 at 2:15 AM, Xing Zheng <zhengxing@rock-chips.com>
>> wrote:
>>> + MMC(SCLK_SDMMC_DRV, "emmc_drv", "clk_sdmmc",
>>> RK3399_SDMMC_CON0, 1),
>>> + MMC(SCLK_SDMMC_SAMPLE, "emmc_sample", "clk_sdmmc",
>>> RK3399_SDMMC_CON1, 1),
>>
>> Can you and Jianqun Xu please coordinate? Though I don't have a TRM
>> for rk3399 and I haven't looked through this whole patch, I know for
>> sure there's a problem when I pick the latest patch series from both
>> of you it doesn't compile.
>>
>> I believe this is the latest from each of you in patchwork:
>>
>> 8462411 [v3,1/3] dt-bindings: add bindings for rk3399 clock controller
>> 8462431 [v3,2/3] clk: rockchip: add dt-binding header for rk3399
>> 8462441 [v3,3/3] ARM64: dts: rockchip: add core dtsi file for rk3399
>>
>> 8463741 [RESEND,v2,1/5] clk: rockchip: add more mux parameters for
>> new pll sources
>> 8463801 [RESEND,v2,2/5] clk: rockchip: Add support for multiple
>> clock providers
>> 8463771 [RESEND,v2,3/5] clk: rockchip: add new pll-type for rk3399
>> and similar socs
>> 8463781 [RESEND,v2,4/5] clk: rockchip: add a
>> COMPOSITE_FRACMUX_NOGATE type
>> 8463831 [RESEND,v2,5/5] clk: rockchip: add clock controller for the
>> RK3399
>>
>>
>> Specifically your patch from March 1st refers to SCLK_SDMMC_DRV and
>> SCLK_SDMMC_SAMPLE. Those defines existed in Jianqun Xu's patch back
>> on Feb 19th <https://patchwork.kernel.org/patch/8355411/>, but his
>> latest patch series from March 1st
>> <https://patchwork.kernel.org/patch/8462431/> no longer has those
>> #defines.
>>
>> Can you two resolve this so I can pick both patch series and see that
>> they compile? ...or let me know where I messed up, of course.
>>
> ok, we will upload dtsi later after the clk-rk3399 driver been applied.
> xing will send the patches for rk3399 together.
>
> We hope the dtsi could be applied first but depends on clk driver, but
> it seems
> not a good idea, we will resend dtsi patch after more drivers are
> applied.
>
> Thanks Doug.
>
>> Thanks!
>>
>> -Doug
>>
>>
>>
>
>
>
--
- Xing Zheng
prev parent reply other threads:[~2016-03-09 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 10:14 [RESEND PATCH v2 0/5] Add more clock compatible features and support the RK3399 clock Xing Zheng
2016-03-01 10:14 ` [RESEND PATCH v2 1/5] clk: rockchip: add more mux parameters for new pll sources Xing Zheng
2016-03-09 1:12 ` Heiko Stuebner
2016-03-01 10:14 ` [RESEND PATCH v2 2/5] clk: rockchip: Add support for multiple clock providers Xing Zheng
2016-03-01 10:14 ` [RESEND PATCH v2 3/5] clk: rockchip: add new pll-type for rk3399 and similar socs Xing Zheng
2016-03-09 1:22 ` Heiko Stuebner
2016-03-09 2:20 ` Xing Zheng
2016-03-01 10:14 ` [RESEND PATCH v2 4/5] clk: rockchip: add a COMPOSITE_FRACMUX_NOGATE type Xing Zheng
2016-03-01 10:15 ` [RESEND PATCH v2 5/5] clk: rockchip: add clock controller for the RK3399 Xing Zheng
2016-03-08 23:34 ` Doug Anderson
2016-03-09 0:51 ` Jianqun Xu
2016-03-09 1:26 ` Xing Zheng [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=56DF7BCA.3000900@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox