From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] Rockchip dts32 fixes for 4.16
Date: Sun, 18 Feb 2018 16:40:49 +0100 [thread overview]
Message-ID: <2137280.MWbT8y5lbZ@phil> (raw)
Hi Arnd, Kevin, Olof,
please find below and in the next mail accumulated fixes for Rockchip
platforms on 4.16.
Please pull. Thanks
Heiko
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.16-rockchip-dts32fixes-1
for you to fetch changes up to e78c637127ee7683d606737f2e62b5da6fd7b1c3:
ARM: dts: rockchip: Fix DWMMC clocks (2018-02-16 10:45:16 +0100)
----------------------------------------------------------------
Fix wrong dwmmc tuning clocks that may make probing HS cards fail to
probe and removal of special opps from the phycore boards that may
run the cpu outside the soc-vendor specs.
----------------------------------------------------------------
Daniel Schultz (1):
ARM: dts: rockchip: Remove 1.8 GHz operation point from phycore som
Robin Murphy (1):
ARM: dts: rockchip: Fix DWMMC clocks
arch/arm/boot/dts/rk3036.dtsi | 4 ++--
arch/arm/boot/dts/rk322x.dtsi | 6 +++---
arch/arm/boot/dts/rk3288-phycore-som.dtsi | 20 --------------------
3 files changed, 5 insertions(+), 25 deletions(-)
next reply other threads:[~2018-02-18 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 15:40 Heiko Stuebner [this message]
2018-02-18 15:41 ` [GIT PULL 2/2] Rockchip dts64 fixes for 4.16 Heiko Stuebner
2018-02-22 16:47 ` Arnd Bergmann
2018-02-22 16:47 ` [GIT PULL 1/2] Rockchip dts32 " Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2018-03-12 8:37 Heiko Stuebner
2018-03-12 14:34 ` 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=2137280.MWbT8y5lbZ@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