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 dts fixes for 6.11
Date: Sun, 01 Sep 2024 23:39:02 +0200 [thread overview]
Message-ID: <7602696.A5hrfCrGMc@diego> (raw)
Hi Arnd, Kevin, Olof,
please find a below a collection of fixes for the current release 6.11
cycle.
Please pull
Thanks
Heiko
The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.11-rockchip-dtsfixes
for you to fetch changes up to 5956ee09c8254273c587b07f5b4d42da59a0325c:
arm64: dts: rockchip: Fix compatibles for RK3588 VO{0,1}_GRF (2024-08-29 13:54:33 +0200)
----------------------------------------------------------------
A number of pin fixes for Puma, Rock-Pi-E and rk356x, and as it turns
out the VO0 and VO1 general register files are not identical as suggested
by their original compatible. As there are no users of those yet,
everybody agreed that we should fix the compatibles.
----------------------------------------------------------------
Alexander Shiyan (1):
arm64: dts: rockchip: Remove broken tsadc pinctrl binding for rk356x
Cristian Ciocaltea (2):
dt-bindings: soc: rockchip: Fix compatibles for RK3588 VO{0,1}_GRF
arm64: dts: rockchip: Fix compatibles for RK3588 VO{0,1}_GRF
FUKAUMI Naoki (1):
arm64: dts: rockchip: fix PMIC interrupt pin in pinctrl for ROCK Pi E
Quentin Schulz (2):
arm64: dts: rockchip: fix eMMC/SPI corruption when audio has been used on RK3399 Puma
arm64: dts: rockchip: override BIOS_DISABLE signal via GPIO hog on RK3399 Puma
.../devicetree/bindings/soc/rockchip/grf.yaml | 10 +++++-
arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dts | 2 +-
arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 36 ++++++++++++++++++++--
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 7 ++---
arch/arm64/boot/dts/rockchip/rk3588-base.dtsi | 6 ++--
5 files changed, 49 insertions(+), 12 deletions(-)
reply other threads:[~2024-09-01 21:38 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=7602696.A5hrfCrGMc@diego \
--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