From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: linux-rockchip@lists.infradead.org, soc@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Rockchip DT64 changes for 5.4 - round2
Date: Thu, 05 Sep 2019 14:18:54 +0200 [thread overview]
Message-ID: <43564855.cWDBQSyQMS@phil> (raw)
In-Reply-To: <1718334.9BoTfW0Ujv@phil>
The following changes since commit fc702ed49a8668a17343811ee28214d845bfc5e6:
arm64: dts: rockchip: Add dts for Leez RK3399 P710 SBC (2019-08-16 14:39:20 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.4-rockchip-dts64-2
for you to fetch changes up to 03e61929c0d227ed3e1c322fc3804216ea298b7e:
arm64: dts: rockchip: limit clock rate of MMC controllers for RK3328 (2019-09-01 03:00:17 +0200)
----------------------------------------------------------------
RK3328 mmc clockrate limit and addition of vpu node as well
as a regulator fix for the rk3328-rock64.
----------------------------------------------------------------
Jonas Karlman (1):
arm64: dts: rockchip: add rk3328 VPU node
Kever Yang (1):
arm64: dts: rockchip: fix vcc_host_5v regulator for usb3 host
Shawn Lin (1):
arm64: dts: rockchip: limit clock rate of MMC controllers for RK3328
arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 11 ++---------
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 17 ++++++++++++++++-
2 files changed, 18 insertions(+), 10 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-05 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 12:18 [GIT PULL 1/2] Rockchip DT32 changes for 5.4 - round2 Heiko Stuebner
2019-09-05 12:18 ` Heiko Stuebner [this message]
2019-09-05 15:54 ` [GIT PULL 2/2] Rockchip DT64 " Arnd Bergmann
2019-09-05 15:53 ` [GIT PULL 1/2] Rockchip DT32 " 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=43564855.cWDBQSyQMS@phil \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=soc@kernel.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).