[PATCH RFC 0/2] remoteproc: qcom: wcss-sec: add IPQ8074 with a separate M3 image

[John Macias]

This adds IPQ8074 to the WCSS secure PIL driver, on top of v14 of
"Add new driver for WCSS secure PIL loading":
https://lore.kernel.org/all/20260803-rproc-v14-0-a1f87b0b0ad2@xxxxxxxxxxxxxxxx/

IPQ8074 needs the PRNG AHB clock, and its firmware ships the M3 image
separately from Q6 with its own load address. On the board I have, the
M3 image goes into its own reserved region with board data between the
two. Patch 1 lets IPQ8074 name its regions "q6" and "m3" and give a
second firmware name; patch 2 loads M3 into that region before the
authenticated Q6 image. Without memory-region-names nothing changes for
any compatible.

Testing:
- dt_binding_check (dtschema 2026.9) passes; the schema also rejects
  named regions on other compatibles and a named IPQ8074 node with only
  one region or one firmware name.
- arm64 W=1 build of the driver as a module, no warnings.
- Not booted in this form. The equivalent change on OpenWrt's earlier
  copy of this driver has run on every boot of a Netgear RAX120 v1
  (IPQ8074 hw1.0, WLAN.HK.2.0-01792-QCAHKSWPL_SILICONZ-1).

Varadarajan, would you rather fold this into your series, or should I
resend it once v14 is merged? I am happy to test either way on that
board.

This work was developed with AI assistance (Assisted-by tags on each
patch).

John Macias (2):
  dt-bindings: remoteproc: qcom: wcss-sec: add IPQ8074
  remoteproc: qcom: wcss-sec: add IPQ8074 support

 .../remoteproc/qcom,ipq5018-wcss-sec-pil.yaml | 96 ++++++++++++++++--
 drivers/remoteproc/qcom_q6v5_wcss_sec.c       | 97 ++++++++++++++++++-
 2 files changed, 184 insertions(+), 9 deletions(-)

-- 
2.47.3