From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] Rockchip dts64 updates for 4.13 part1
Date: Fri, 09 Jun 2017 12:14:36 +0200 [thread overview]
Message-ID: <3220808.DiVK6dvI90@phil> (raw)
In-Reply-To: <2090243.QTRV0U63fj@phil>
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.13-rockchip-dts64-1
for you to fetch changes up to 5fd3ffb92d33f86a5c0757ef879f7d785beeec92:
arm64: dts: rockchip: update common rk3399 operating points (2017-05-30 12:12:07 +0200)
----------------------------------------------------------------
Support for the new rk3399 firefly board; extending the pcie ranges to
make usage of pci switches possible; some more qos and pinctrl nodes on
rk3399; updates for the rk3399 cpu operating points including separate
opps for the higher rates OP1 variant of the chip and mmc-nodes for
the rk3328.
----------------------------------------------------------------
Heiko Stuebner (5):
arm64: dts: rockchip: bring rk3399-firefly power-tree in line
arm64: dts: rockchip: add ethernet0 alias on rk3399
arm64: dts: rockchip: enable usb3 controllers on rk3399-firefly
arm64: dts: rockchip: introduce rk3399-op1 operating points
arm64: dts: rockchip: update common rk3399 operating points
Kever Yang (4):
dt-bindings: add firefly-rk3399 board support
arm64: dts: rockchip: add support for firefly-rk3399 board
arm64: dts: rockchip: add some missing qos nodes on rk3399
arm64: dts: rockchip: add pinctrl settings for some rk3399 peripherals
Shawn Lin (3):
arm64: dts: rockchip: extent bus-ranges of PCIe for rk3399
arm64: dts: rockchip: extent IORESOURCE_MEM_64 of PCIe for rk3399
arm64: dts: rockchip: add sdmmc/sdio/emmc nodes for RK3328 SoCs
Documentation/devicetree/bindings/arm/rockchip.txt | 4 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 33 +
arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 718 +++++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 2 +-
arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi | 145 +++++
arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi | 18 +-
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 165 ++++-
8 files changed, 1064 insertions(+), 22 deletions(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
next prev parent reply other threads:[~2017-06-09 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 10:13 [GIT PULL 1/3] Rockchip dts32 updates for 4.13 part1 Heiko Stuebner
2017-06-09 10:14 ` Heiko Stuebner [this message]
2017-06-19 2:08 ` [GIT PULL 2/3] Rockchip dts64 " Olof Johansson
2017-06-09 10:15 ` [GIT PULL 3/3] Rockchip soc32 " Heiko Stuebner
2017-06-19 2:08 ` Olof Johansson
2017-06-19 2:07 ` [GIT PULL 1/3] Rockchip dts32 " Olof Johansson
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=3220808.DiVK6dvI90@phil \
--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).