From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Rockchip dts64 updates for 5.1
Date: Fri, 01 Feb 2019 12:24:29 +0100 [thread overview]
Message-ID: <1744093.FyxTZ0jN5f@phil> (raw)
In-Reply-To: <2570520.8EeqtpO5V7@phil>
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.1-rockchip-dts64-1
for you to fetch changes up to 79164c99db284d07aa4e84e57b469d225609799c:
arm64: dts: rockchip: clean up the abuse of disable-wp (2019-01-28 10:51:22 +0100)
----------------------------------------------------------------
New boards are the Rock Pi 4, NanoPC-T4 and NanoPi-M4, with the last
two being part of a family and sharing bigger parts of the devicetree.
rk3328 got sound-related upgrades and a wider patch drops mmc display-wp
fields from nodes which shouldn't use it.
----------------------------------------------------------------
Akash Gajjar (1):
arm64: dts: rockchip: add ROCK Pi 4 DTS support
Heiko Stuebner (1):
arm64: dts: rockchip: move rk3328 #sound-dai-cells to the soc dtsi
Katsuhiro Suzuki (2):
arm64: dts: rockchip: add rk3328 ACODEC node
arm64: dts: rockchip: enable analog audio node for rock64
Robin Murphy (4):
arm64: dts: rockchip: Add DT for NanoPi M4
arm64: dts: rockchip: Refine nanopi4 differences
arm64: dts: rockchip: Add NanoPC-T4 IR receiver
arm64: dts: rockchip: 'Fix' nanopi4 uSD card detect
Shawn Lin (1):
arm64: dts: rockchip: clean up the abuse of disable-wp
Tomeu Vizoso (1):
arm64: dts: rockchip: Add devicetree for NanoPC-T4
.../devicetree/bindings/arm/rockchip.yaml | 12 +
arch/arm64/boot/dts/rockchip/Makefile | 3 +
arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 26 +-
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 14 +
arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 1 -
arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts | 1 -
arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi | 1 -
.../boot/dts/rockchip/rk3368-orion-r68-meta.dts | 1 -
arch/arm64/boot/dts/rockchip/rk3368-px5-evb.dts | 1 -
arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 1 -
arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts | 91 +++
arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dts | 66 ++
arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi | 676 +++++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dts | 606 ++++++++++++++++++
.../dts/rockchip/rk3399-sapphire-excavator.dts | 1 -
15 files changed, 1492 insertions(+), 9 deletions(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dts
next prev parent reply other threads:[~2019-02-01 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 11:23 [GIT PULL 1/2] Rockchip dts32 updates for 5.1 Heiko Stuebner
2019-02-01 11:24 ` Heiko Stuebner [this message]
2019-02-15 13:45 ` [GIT PULL 2/2] Rockchip dts64 " Arnd Bergmann
2019-02-15 15:38 ` Arnd Bergmann
2019-02-15 19:32 ` Heiko Stübner
2019-02-15 19:52 ` Arnd Bergmann
2019-02-15 13:36 ` [GIT PULL 1/2] Rockchip dts32 " 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=1744093.FyxTZ0jN5f@phil \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@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).