From: Heiko Stuebner <heiko@sntech.de>
To: Stephen Boyd <sboyd@codeaurora.org>,
mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: [GIT PULL] Rockchip clock updates for 4.19
Date: Mon, 06 Aug 2018 10:50:24 +0200 [thread overview]
Message-ID: <29493561.nOART3tDXq@phil> (raw)
Hi Mike, Stephen,
This one change on top of the previous changes that adds a critical clock
on rk3399 to prevent random hangs due to it supplying the vdd_log
cpu core supply.
Please pull
Heiko
The following changes since commit a64ad008980c65d38e6cf6858429c78e6b740c41:
clk: rockchip: fix clk_i2sout parent selection bits on rk3399 (2018-07-08 00:19:19 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.19-rockchip-clk2
for you to fetch changes up to 508fc689cfe514228cb0b91f94d5542ec11881b1:
clk: rockchip: Add pclk_rkpwm_pmu to PMU critical clocks in rk3399 (2018-08-06 10:03:13 +0200)
----------------------------------------------------------------
pclk_rkpwm_pmu as critical clock, due to it supplying the pwm
used to drive the logic supply of the rk3399 core.
----------------------------------------------------------------
Levin Du (1):
clk: rockchip: Add pclk_rkpwm_pmu to PMU critical clocks in rk3399
drivers/clk/rockchip/clk-rk3399.c | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2018-08-06 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 8:50 Heiko Stuebner [this message]
2018-08-06 21:59 ` [GIT PULL v2] Rockchip clock updates for 4.19 - round 2 Heiko Stuebner
2018-08-08 5:54 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2018-07-11 14:22 [GIT PULL] Rockchip clock updates for 4.19 Heiko Stuebner
2018-07-11 17:38 ` Stephen Boyd
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=29493561.nOART3tDXq@phil \
--to=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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