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 1/2] Rockchip dts32 updates for 5.2
Date: Tue, 02 Apr 2019 11:05:16 +0200 [thread overview]
Message-ID: <13182220.1UgD4fsNbT@phil> (raw)
Hi Arnd, Kevin Olof,
please find below and in the reply round1 of Rockchip devicetree updates
targetted at 5.2. Nothing major, some new boards and a number of
general updates - Please pull
Thanks
Heiko
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.2-rockchip-dts32-1
for you to fetch changes up to 4b028ebd4e3d86c61161b3a937b746043006dcbe:
ARM: dts: rockchip: enable vop0 and hdmi nodes to rk3066a-mk808 (2019-03-31 17:28:05 +0200)
----------------------------------------------------------------
Quite a bit of love for the rk3288-veyron chromeos devices and a number
of cleanups for rk3288 from that area, hdmi support for the old rk3066
a small rv1108-eglin-r1 cleanup and wifi+hdmi-cec for the tinker board.
----------------------------------------------------------------
David Summers (1):
ARM: dts: rockchip: Enable WiFi on rk3288-tinker
Douglas Anderson (7):
ARM: dts: rockchip: Fix gic/efuse sort ordering for rk3288
dt-bindings: ARM: dts: rockchip: Add rk3288-veyron-jerry rev 10-15
ARM: dts: rockchip: Add rk3288-veyron-jerry rev 10-15
ARM: dts: rockchip: Add dvs-gpios to rk3288-veyron-jerry
ARM: dts: rockchip: Add vdd_logic to rk3288-veyron
dt-bindings: ARM: dts: rockchip: Add bindings for rk3288-veyron-mighty
ARM: dts: rockchip: Add device tree for rk3288-veyron-mighty
Johan Jonker (2):
ARM: dts: rockchip: remove disable-wp from rv1108-elgin-r1 emmc node
ARM: dts: rockchip: enable vop0 and hdmi nodes to rk3066a-mk808
Jonas Karlman (2):
ARM: dts: rockchip: Enable HDMI CEC on rk3288-tinker-s
ARM: dts: rockchip: add grf reference in rk3288 tsadc node
Zheng Yang (1):
ARM: dts: rockchip: add rk3066 hdmi nodes
.../devicetree/bindings/arm/rockchip.yaml | 19 ++++++-
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/rk3066a-mk808.dts | 29 +++++++++++
arch/arm/boot/dts/rk3066a.dtsi | 59 ++++++++++++++++++++++
arch/arm/boot/dts/rk3288-tinker-s.dts | 5 ++
arch/arm/boot/dts/rk3288-tinker.dtsi | 37 ++++++++++++++
arch/arm/boot/dts/rk3288-veyron-jerry.dts | 9 +++-
arch/arm/boot/dts/rk3288-veyron-mighty.dts | 34 +++++++++++++
arch/arm/boot/dts/rk3288-veyron.dtsi | 17 +++++++
arch/arm/boot/dts/rk3288.dtsi | 27 +++++-----
arch/arm/boot/dts/rv1108-elgin-r1.dts | 1 -
11 files changed, 221 insertions(+), 17 deletions(-)
create mode 100644 arch/arm/boot/dts/rk3288-veyron-mighty.dts
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-04-02 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 9:05 Heiko Stuebner [this message]
2019-04-02 9:05 ` [GIT PULL 2/2] Rockchip dts64 updates for 5.2 Heiko Stuebner
2019-04-28 19:16 ` Olof Johansson
2019-04-28 19:15 ` [GIT PULL 1/2] 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=13182220.1UgD4fsNbT@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).