From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: SoC fixes for 6.11, part 3
Date: Wed, 11 Sep 2024 15:08:02 +0000 [thread overview]
Message-ID: <58c9776e-0e3a-4b00-bea8-47a7bcf2af37@app.fastmail.com> (raw)
The following changes since commit 9cc7b1705141d1a077493dc107ed626e8dc84681:
Merge tag 'at91-fixes-6.11' of https://git.kernel.org/pub/scm/linux/kernel/git/at91/linux into arm/fixes (2024-08-30 19:52:28 +0000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/arm-fixes-6.11-3
for you to fetch changes up to 0e7af99aef5f58b4bae00e45fd1c2626a987f7bb:
Merge tag 'riscv-soc-fixes-for-v6.11-final' of https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux into arm/fixes (2024-09-11 08:54:37 +0000)
----------------------------------------------------------------
ARM: SoC fixes for 6.11, part 3
The bulk of the changes this time are for device tree files in the
rockchips platform, addressing correctness issues on individual
boards, plus one change in the rk356x SoC file to make it match
the binding.
The only other changes that came in are
- a CPU frequencey scaling fix for JH7110 (RISC-V)
- a build fix for the cznic hwrandom driver
- a fix for a deadlock in qualcomm uefi secure
application firmware driver
----------------------------------------------------------------
Alexander Shiyan (1):
arm64: dts: rockchip: Remove broken tsadc pinctrl binding for rk356x
Arnd Bergmann (4):
Merge tag 'qcom-drivers-fixes-for-6.11-2' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into arm/fixes
Merge tag 'v6.11-rockchip-dtsfixes' of https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip into arm/fixes
platform: cznic: turris-omnia-mcu: fix HW_RANDOM dependency
Merge tag 'riscv-soc-fixes-for-v6.11-final' of https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux into arm/fixes
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
Dan Carpenter (1):
firmware: qcom: uefisecapp: Fix deadlock in qcuefi_acquire()
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
Xingyu Wu (1):
riscv: dts: starfive: jh7110-common: Fix lower rate of CPUfreq by setting PLL0 rate to 1.5GHz
.../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 ++--
arch/riscv/boot/dts/starfive/jh7110-common.dtsi | 6 ++++
drivers/firmware/qcom/qcom_qseecom_uefisecapp.c | 4 +++
drivers/platform/cznic/Kconfig | 2 +-
8 files changed, 60 insertions(+), 13 deletions(-)
next reply other threads:[~2024-09-11 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 15:08 Arnd Bergmann [this message]
2024-09-11 18:31 ` pr-tracker-bot
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=58c9776e-0e3a-4b00-bea8-47a7bcf2af37@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®