[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251210003729.3909663-1-mr.nuke.me@gmail.com>
Date: Tue, 9 Dec 2025 18:37:22 -0600
From: Alexandru Gagniuc <mr.nuke.me@...il.com>
To: robh@...nel.org,
krzk+dt@...nel.org,
conor+dt@...nel.org,
devicetree@...r.kernel.org
Cc: andersson@...nel.org,
mathieu.poirier@...aro.org,
konradybcio@...nel.org,
linux-arm-msm@...r.kernel.org,
linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Alexandru Gagniuc <mr.nuke.me@...il.com>
Subject: [PATCH RFC 0/3] remoteproc/qcom,q6v5: introduce IPQ9574
I want to enable ath11k on IPQ9574 SoCs, which uses the qcom remoteproc
for communication with firmware. It is similar to qcom,ipq8074-wcss-pil,
and I think it makes sense to extend the IP8074 path. The existing bidings
are not yaml. Am I required to convert the bindings to DT schema before
updating them?
Whom do I add as the maintainer for the YAML binding? Do I add my name? Do
I need to find an existing maintainer who is willing to use their name?
I would like to add the remoteproc node to IPQ8074. One of the resets is
missing from "qcom,gcc-ipq8074.h". Can I use a placeholder value with a
comment? Am I expected to enable the reset in code before adding the
devicetree node?
Alex
---
Alexandru Gagniuc (3):
dt-bindings: remoteproc: qcom,ipq8074-wcss-pil: convert to DT schema
dt-bindings: remoteproc: qcom: add IPQ9574 image loader
arm64: dts: qcom: ipq8074: add remoteproc nodes
.../remoteproc/qcom,ipq9574-wcss-pil.yaml | 269 ++++++++++++++++++
.../bindings/remoteproc/qcom,q6v5.txt | 102 -------
arch/arm64/boot/dts/qcom/ipq8074.dtsi | 79 +++++
3 files changed, 348 insertions(+), 102 deletions(-)
create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,ipq9574-wcss-pil.yaml
delete mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt
--
2.45.1
Powered by blists - more mailing lists