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 v2] Rockchip dts64 changes for 5.19 #2
Date: Fri, 27 May 2022 20:25:16 +0200 [thread overview]
Message-ID: <7695907.Sb9uPGUboI@phil> (raw)
The following changes since commit bc405bb3eeee4b711830ab569e7f3811b92196ab:
arm64: dts: rockchip: enable otg/drd operation of usb_host0_xhci in rk356x (2022-05-11 06:09:55 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.19-rockchip-dts64-2
for you to fetch changes up to cd414d5ac1fdeecf0617737e688a1af00858253a:
arm64: dts: rockchip: rename Quartz64-A bluetooth gpios (2022-05-27 19:31:24 +0200)
----------------------------------------------------------------
Clock properties for cru nodes to match the yaml-converted bindings
and renaming of Quartz-A bluetooth pin nodename to not conflict with
Yaml constraints.
----------------------------------------------------------------
Johan Jonker (2):
arm64: dts: rockchip: add clocks property to cru node rk3308
arm64: dts: rockchip: add clocks property to cru node rk3368
Peter Geis (2):
arm64: dts: rockchip: add clocks to rk356x cru
arm64: dts: rockchip: rename Quartz64-A bluetooth gpios
arch/arm64/boot/dts/rockchip/rk3308.dtsi | 5 +++--
arch/arm64/boot/dts/rockchip/rk3368.dtsi | 2 ++
arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.dts | 4 ++--
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 2 ++
4 files changed, 9 insertions(+), 4 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-27 18:26 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=7695907.Sb9uPGUboI@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).