From: Bjorn Andersson <andersson@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
Tanmay Shah <tanmay.shah@amd.com>, Peng Fan <peng.fan@nxp.com>,
Komal Bajaj <komal.bajaj@oss.qualcomm.com>,
Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>,
Jiafei Pan <Jiafei.Pan@nxp.com>,
Julian Braha <julianbraha@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Shawn Guo <shengchao.guo@oss.qualcomm.com>,
Wasim Nazir <wasim.nazir@oss.qualcomm.com>
Subject: [GIT PULL] remoteproc updates for v7.2
Date: Sat, 20 Jun 2026 09:37:09 -0500 [thread overview]
Message-ID: <20260620143709.1112373-1-andersson@kernel.org> (raw)
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git tags/rproc-v7.2
for you to fetch changes up to b5bfc7d039bb775730186a9c38d0f01afd729638:
remoteproc: qcom: pas: Drop start/stop completion from struct qcom_pas (2026-06-08 21:53:51 -0500)
----------------------------------------------------------------
remoteproc updates for v7.2
Add i.MX94 support to the i.MX remoteproc driver, covering the Cortex-M7
and Cortex-M33 Sync cores. This also fixes programming of non-zero System
Manager CPU/LMM reset vectors.
Move the remoteproc resource table definitions to a separate header, so
they can be used by clients that do not otherwise depend on remoteproc.
Switch the firmware resource handling over to the common iterator.
Update the Xilinx R5F remoteproc driver to check the remote core state
before attaching, drop a binding header dependency, and add
firmware-name based auto boot support.
Add Qualcomm Hawi ADSP/CDSP bindings, together with Shikra RPM bindings
and CDSP, LPAICP, and MPSS PAS support. Fix a Qualcomm minidump leak,
clean up PAS and WCSS reset handling, and make the user-visible Qualcomm
naming consistent.
Remove a duplicate STM32_RPROC Kconfig dependency and make i.MX
remoteproc instances use the device node name so multiple processors can
be distinguished in sysfs.
----------------------------------------------------------------
Alexandru Gagniuc (1):
remoteproc: qcom_q6v5_wcss: drop redundant wcss_q6_bcr_reset
Bibek Kumar Patro (1):
remoteproc: qcom: pas: Add Shikra remoteproc support
Jiafei Pan (1):
remoteproc: imx_rproc: Use device node name as processor name
Julian Braha (1):
remoteproc: Dead code cleanup in Kconfig for STM32_RPROC
Komal Bajaj (2):
dt-bindings: remoteproc: Add Shikra RPM processor compatible
dt-bindings: remoteproc: qcom,shikra-pas: Document Shikra PAS remoteprocs
Krzysztof Kozlowski (1):
remoteproc: qcom: Unify user-visible "Qualcomm" name
Mukesh Ojha (4):
remoteproc: Move resource table data structure to its own header
remoteproc: use rsc_table_for_each_entry() in rproc_handle_resources()
dt-bindings: remoteproc: qcom,sm8550-pas: Add Hawi ADSP compatible
dt-bindings: remoteproc: qcom,sm8550-pas: Add Hawi CDSP compatible
Peng Fan (3):
dt-bindings: remoteproc: imx-rproc: Support i.MX94
remoteproc: imx_rproc: Program non-zero SM CPU/LMM reset vector
remoteproc: imx_rproc: Add support for i.MX94
Shawn Guo (1):
remoteproc: qcom: pas: Drop start/stop completion from struct qcom_pas
Tanmay Shah (4):
remoteproc: xlnx: Check remote core state
remoteproc: xlnx: Remove binding header dependency
dt-bindings: remoteproc: xlnx: Add firmware-name property
remoteproc: xlnx: Enable auto boot feature
Wasim Nazir (1):
remoteproc: qcom: Fix leak when custom dump_segments addition fails
.../bindings/remoteproc/fsl,imx-rproc.yaml | 3 +
.../bindings/remoteproc/qcom,rpm-proc.yaml | 1 +
.../bindings/remoteproc/qcom,shikra-pas.yaml | 167 ++++++++++
.../bindings/remoteproc/qcom,sm8550-pas.yaml | 4 +
.../bindings/remoteproc/xlnx,zynqmp-r5fss.yaml | 4 +
drivers/firmware/xilinx/zynqmp.c | 28 ++
drivers/remoteproc/Kconfig | 3 +-
drivers/remoteproc/imx_rproc.c | 95 +++++-
drivers/remoteproc/imx_rproc.h | 2 +
drivers/remoteproc/qcom_common.c | 14 +-
drivers/remoteproc/qcom_q6v5_pas.c | 51 ++-
drivers/remoteproc/qcom_q6v5_wcss.c | 23 +-
drivers/remoteproc/remoteproc_core.c | 81 +++--
drivers/remoteproc/xlnx_r5_remoteproc.c | 100 ++++--
include/linux/firmware/xlnx-zynqmp.h | 21 ++
include/linux/remoteproc.h | 269 +--------------
include/linux/rsc_table.h | 359 +++++++++++++++++++++
17 files changed, 858 insertions(+), 367 deletions(-)
create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml
create mode 100644 include/linux/rsc_table.h
next reply other threads:[~2026-06-20 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 14:37 Bjorn Andersson [this message]
2026-06-21 6:38 ` [GIT PULL] remoteproc updates for v7.2 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=20260620143709.1112373-1-andersson@kernel.org \
--to=andersson@kernel.org \
--cc=Jiafei.Pan@nxp.com \
--cc=bibek.patro@oss.qualcomm.com \
--cc=julianbraha@gmail.com \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mr.nuke.me@gmail.com \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=peng.fan@nxp.com \
--cc=shengchao.guo@oss.qualcomm.com \
--cc=tanmay.shah@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=wasim.nazir@oss.qualcomm.com \
/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