public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: zhengxing@rock-chips•com (Xing Zheng)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 0/3] Rockchip: rk3399: Add core dtsi for rk3399
Date: Fri, 01 Apr 2016 11:50:56 +0800	[thread overview]
Message-ID: <56FDF020.9070705@rock-chips.com> (raw)
In-Reply-To: <16060533.TL0fcROj1E@phil>

Hi Heiko,
     I also updated some clock patches for RK3399 recently, and I will 
continue to update clock patches_V7 in future.
Please note them. :-)

Thanks.

On 2016?04?01? 11:23, Heiko Stuebner wrote:
> Hi Jianqun,
>
> Am Freitag, 1. April 2016, 10:55:09 schrieb jay.xu:
>> After talking with xing, we plan to summit dtsi after xing's patches are
>> applied,
>> and I will update the patch for rk3399 core dtsi quickly
> Not sure if you have seen it, but I picked up Xing's most recent clock
> patches already [0]. So go ahead when you have time :-)
>
>
> Heiko
>
>
> [0] https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/log/?h=v4.7-clk/next
>
>
>> On 2016?04?01? 05:48, Heiko Stuebner wrote:
>>> Hi Jianqun,
>>>
>>> Am Dienstag, 1. M?rz 2016, 14:39:58 schrieb Jianqun Xu:
>>>> There is the new SoCs from Rockchip which named rk3399, the
>>>> patches are added to support them.
>>> is this still valid or does it need an update?
>>> The clock-series from Xing saw changes, so I'm guessing the devicetree
>>> side might also need some update?
>>>
>>> Especially an actual board-file would be nice ;-) .
>>>
>>>
>>> Thanks
>>> Heiko
>
>
>


-- 
- Xing Zheng

      reply	other threads:[~2016-04-01  3:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23  7:01 [PATCH 0/4] Rockchip: rk3399: Add core dtsi for rk3399 jianqun.xu
2016-02-23  7:01 ` [PATCH 1/4] soc: rockchip: add bindings for Rockchip grf jianqun.xu
2016-02-23 22:15   ` Rob Herring
2016-02-24  0:18     ` Jianqun Xu
2016-02-24 14:35   ` Heiko Stuebner
2016-02-23  7:01 ` [PATCH 2/4] dt-bindings: add bindings for rk3399 clock controller jianqun.xu
2016-02-23 22:17   ` Rob Herring
2016-02-23  7:01 ` [PATCH 3/4] clk: rockchip: add dt-binding header for rk3399 jianqun.xu
2016-02-24 13:27   ` Heiko Stuebner
2016-02-25  0:42     ` Jianqun Xu
2016-02-23  7:01 ` [PATCH 4/4] ARM64: dts: rockchip: add core dtsi file " jianqun.xu
2016-02-26  3:12 ` [PATCH v2 0/3] Rockchip: rk3399: Add core dtsi " Jianqun Xu
2016-02-26  3:12   ` [PATCH v2 1/3] dt-bindings: add bindings for rk3399 clock controller Jianqun Xu
2016-02-26  3:12   ` [PATCH v2 2/3] clk: rockchip: add dt-binding header for rk3399 Jianqun Xu
2016-02-26  3:12   ` [PATCH v2 3/3] ARM64: dts: rockchip: add core dtsi file " Jianqun Xu
2016-03-01  6:39   ` [PATCH v3 0/3] Rockchip: rk3399: Add core dtsi " Jianqun Xu
2016-03-01  6:39     ` [PATCH v3 1/3] dt-bindings: add bindings for rk3399 clock controller Jianqun Xu
2016-03-01  6:40     ` [PATCH v3 2/3] clk: rockchip: add dt-binding header for rk3399 Jianqun Xu
2016-03-01  9:19       ` Xing Zheng
2016-03-01  6:40     ` [PATCH v3 3/3] ARM64: dts: rockchip: add core dtsi file " Jianqun Xu
2016-03-31 21:48     ` [PATCH v3 0/3] Rockchip: rk3399: Add core dtsi " Heiko Stuebner
2016-04-01  2:55       ` jay.xu
2016-04-01  3:23         ` Heiko Stuebner
2016-04-01  3:50           ` 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=56FDF020.9070705@rock-chips.com \
    --to=zhengxing@rock-chips$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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