linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] Rockchip dts64 updates for v4.7 - part2
Date: Fri, 29 Apr 2016 00:25:22 +0200	[thread overview]
Message-ID: <14339181.jSmLu3hG44@diego> (raw)
In-Reply-To: <5544434.9tA8JHBIkp@diego>

The following changes since commit 40ac568d0ef07b60ba8cc0f2e88ccdd4dd0e176a:

  Documentation: devicetree: rockchip: Document rk3368-GeekBox (2016-03-31 19:00:09 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.7-rockchip-dts64-2

for you to fetch changes up to 51c454d2610571404917fa027c73048599dc6c3d:

  dt-bindings: document rockchip rk3399-evb board (2016-04-28 22:25:49 +0200)

----------------------------------------------------------------
Adding the new rk3399 core devicetree support as well as a board
dts for the evaluation board of this chip and similar to the arm32
side also move the rk3368 thermal data into the core soc dtsi, as
there really is no need to keep it separate.

----------------------------------------------------------------
Caesar Wang (1):
      arm64: dts: rockchip: move the rk3368 thermal data into rk3368.dtsi

Heiko Stuebner (2):
      clk: rockchip: fix checkpatch errors in rk3399 dt-binding header
      Merge branch 'v4.7-shared/clkids' into v4.7-armsoc/dts64

Jianqun Xu (3):
      arm64: dts: rockchip: add core dtsi file for RK3399 SoCs
      arm64: dts: rockchip: add dts file for RK3399 evaluation board
      dt-bindings: document rockchip rk3399-evb board

Shawn Lin (1):
      dt-bindings: rockchip-dw-mshc: add description for rk3399

Xing Zheng (4):
      clk: rockchip: add dt-binding header for rk3399
      clk: rockchip: add general gpu soft-reset on rk3399
      clk: rockchip: rename rga clock-id on rk3399
      clk: rockchip: export some necessary rk3399 clock ids

 Documentation/devicetree/bindings/arm/rockchip.txt |    6 +-
 .../devicetree/bindings/mmc/rockchip-dw-mshc.txt   |    1 +
 arch/arm64/boot/dts/rockchip/Makefile              |    1 +
 arch/arm64/boot/dts/rockchip/rk3368.dtsi           |   66 +-
 .../{rk3368-thermal.dtsi => rk3399-evb.dts}        |  124 +--
 arch/arm64/boot/dts/rockchip/rk3399.dtsi           | 1013 ++++++++++++++++++++
 include/dt-bindings/clock/rk3399-cru.h             |  755 +++++++++++++++
 7 files changed, 1908 insertions(+), 58 deletions(-)
 rename arch/arm64/boot/dts/rockchip/{rk3368-thermal.dtsi => rk3399-evb.dts} (55%)
 create mode 100644 arch/arm64/boot/dts/rockchip/rk3399.dtsi
 create mode 100644 include/dt-bindings/clock/rk3399-cru.h

  parent reply	other threads:[~2016-04-28 22:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 22:23 [GIT PULL 0/3] Rockchip updates for v4.7 - part2 Heiko Stübner
2016-04-28 22:24 ` [GIT PULL 1/3] Rockchip driver " Heiko Stübner
2016-05-09 14:17   ` Arnd Bergmann
2016-04-28 22:24 ` [GIT PULL 2/3] Rockchip dts32 " Heiko Stübner
2016-05-10 13:39   ` Arnd Bergmann
2016-04-28 22:25 ` Heiko Stübner [this message]
2016-05-10 20:14   ` [GIT PULL 3/3] Rockchip dts64 " Arnd Bergmann

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=14339181.jSmLu3hG44@diego \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).