From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] Rockchip dts32 updates for 4.18 round 1
Date: Tue, 15 May 2018 12:38:49 +0200 [thread overview]
Message-ID: <2461510.NP0ZiRnFEz@phil> (raw)
In-Reply-To: <2000491.bLgWuj0xar@phil>
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.18-rockchip-dts32-1
for you to fetch changes up to 08624814cbec12b1ce877bf80f6990ad2b9cdcd7:
ARM: dts: rockchip: default serial for rk3288 Tinker Board (2018-04-20 14:55:07 +0200)
----------------------------------------------------------------
Fixed pin numbers for uart4 on rk3288, iommu clocks and small changes
over multiple boards like default serial setting for rk3288-tinker,
output selection for the dp83867 on the phycore-som and the newly
added pwm-backlight delay properties for veyron boards.
----------------------------------------------------------------
Daniel Schultz (1):
ARM: dts: rockchip: Add dp83867 CLK_OUT muxing on rk3288-phycore-som
Enric Balletbo i Serra (2):
ARM: dts: rockchip: set PWM delay backlight settings for Veyron
ARM: dts: rockchip: set PWM delay backlight settings for Minnie
Heinrich Schuchardt (1):
ARM: dts: rockchip: default serial for rk3288 Tinker Board
Jacob Chen (1):
ARM: dts: rockchip: fix uart4 pin-numbers for rk3288
Jeffy Chen (1):
ARM: dts: rockchip: add clocks in iommu nodes
arch/arm/boot/dts/rk3036.dtsi | 2 ++
arch/arm/boot/dts/rk322x.dtsi | 8 ++++++++
arch/arm/boot/dts/rk3288-phycore-som.dtsi | 1 +
arch/arm/boot/dts/rk3288-tinker.dts | 4 ++++
arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi | 3 ++-
arch/arm/boot/dts/rk3288-veyron-minnie.dts | 2 ++
arch/arm/boot/dts/rk3288.dtsi | 20 ++++++++++++++++----
7 files changed, 35 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2018-05-15 10:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 10:38 [GIT PULL 1/4] Rockchip driver updates for 4.18 round 1 Heiko Stuebner
2018-05-15 10:38 ` Heiko Stuebner [this message]
2018-05-15 20:52 ` [GIT PULL 2/4] Rockchip dts32 " Olof Johansson
2018-05-15 10:39 ` [GIT PULL 3/4] Rockchip dts64 " Heiko Stuebner
2018-05-15 20:52 ` Olof Johansson
2018-05-15 10:40 ` [GIT PULL 4/4] Rockchip arm64 defconfig " Heiko Stuebner
2018-05-15 20:53 ` Olof Johansson
2018-05-15 21:41 ` Heiko Stübner
2018-05-15 20:51 ` [GIT PULL 1/4] Rockchip driver " Olof Johansson
2018-07-11 14:28 ` [GIT PULL 1/2] Rockchip dts32 updates for 4.19 " Heiko Stuebner
2018-07-11 14:29 ` [GIT PULL 2/2] Rockchip dts64 " Heiko Stuebner
2018-07-14 21:06 ` Olof Johansson
2018-07-14 21:06 ` [GIT PULL 1/2] Rockchip dts32 " Olof Johansson
2018-07-30 22:35 ` [GIT PULL 1/2] Rockchip dts64 updates for 4.19 round 2 Heiko Stuebner
2018-07-30 22:37 ` [GIT PULL 2/2] Rockchip defconfig64 updates for 4.19 Heiko Stuebner
2018-08-01 2:15 ` Olof Johansson
2018-08-01 2:13 ` [GIT PULL 1/2] Rockchip dts64 updates for 4.19 round 2 Olof Johansson
2018-08-06 8:46 ` [GIT PULL] Rockchip dts64 updates for 4.19 round 3 Heiko Stuebner
2018-08-14 11:02 ` Heiko Stuebner
2018-08-24 15:36 ` 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=2461510.NP0ZiRnFEz@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