From: Heiko Stuebner <heiko@sntech.de>
To: mturquette@baylibre.com, Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: [GIT PULL] Rockchip clock changes for 5.19
Date: Tue, 17 May 2022 21:25:19 +0200 [thread overview]
Message-ID: <8148508.MhkbZ0Pkbq@phil> (raw)
Hi Mike, Stephen,
please find below some Rockchip clock changes for 5.19.
I've split out the conversion from txt to yaml into a separate tag
which'll follow shortly.
Please pull, thanks
Heiko
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.19-rockchip-clk1
for you to fetch changes up to b21445db9818ccb9fa1c0ba81fd3705eb8d347e3:
dt-binding: clock: Add missing rk3568 cru bindings (2022-05-14 12:40:41 +0200)
----------------------------------------------------------------
Some fixes for recent yaml conversion of clock bindinds
and making the hclk_vo critical for rk3568.
----------------------------------------------------------------
Johan Jonker (4):
dt-bindings: clock: fix some conversion style issues for rockchip,rk3399-cru.yaml
dt-bindings: clock: replace a maintainer for rockchip,rk3399-cru.yaml
dt-bindings: clock: use generic node name for pmucru example in rockchip,rk3399-cru.yaml
dt-bindings: clock: fix rk3399 cru clock issues
Peter Geis (1):
dt-binding: clock: Add missing rk3568 cru bindings
Sascha Hauer (1):
clk: rockchip: Mark hclk_vo as critical on rk3568
.../bindings/clock/rockchip,rk3399-cru.yaml | 33 ++++++++--------------
.../bindings/clock/rockchip,rk3568-cru.yaml | 13 +++++++++
drivers/clk/rockchip/clk-rk3568.c | 1 +
3 files changed, 26 insertions(+), 21 deletions(-)
next reply other threads:[~2022-05-17 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 19:25 Heiko Stuebner [this message]
2022-05-17 22:19 ` [GIT PULL] Rockchip clock changes for 5.19 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=8148508.MhkbZ0Pkbq@phil \
--to=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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