From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip driver changes for 5.19 #1
Date: Thu, 12 May 2022 01:42:48 +0200 [thread overview]
Message-ID: <3998951.tdWV9SEqCh@phil> (raw)
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-drivers1
for you to fetch changes up to add9f6f30e54b5c07e7a0260cda459ef1d9646b7:
soc: rockchip: Fix compile-testing SoC drivers (2022-04-30 15:06:14 +0200)
----------------------------------------------------------------
Powerdomain fixes and improvements, some GRF compatible properties
and a rk3566 GRF clocksource default setup.
----------------------------------------------------------------
Brian Norris (3):
soc: rockchip: Clean up Kconfig whitespace
soc: rockchip: power-domain: Replace dsb() with smb()
soc: rockchip: Fix compile-testing SoC drivers
Johan Jonker (1):
dt-bindings: soc: rockchip: add naneng combo phy register compatible
Peter Geis (2):
dt-bindings: soc: rockchip: add rk3566-pipe-grf compatible
soc: rockchip: set dwc3 clock for rk3566
Sebastian Fricke (1):
soc: rockchip: pm_domains: Fix typo in comment
.../devicetree/bindings/soc/rockchip/grf.yaml | 3 +++
drivers/soc/Makefile | 2 +-
drivers/soc/rockchip/Kconfig | 24 +++++++++++-----------
drivers/soc/rockchip/grf.c | 17 +++++++++++++++
drivers/soc/rockchip/pm_domains.c | 10 ++++-----
5 files changed, 38 insertions(+), 18 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-05-11 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3998951.tdWV9SEqCh@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).