Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Gokul Sriram Palanisamy <gokul.sriram.p@oss.qualcomm.com>,
	andersson@kernel.org, mathieu.poirier@linaro.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	konradybcio@kernel.org, quic_mmanikan@quicinc.com,
	linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: quic_srichara@quicinc.com, vignesh.viswanathan@oss.qualcomm.com
Subject: Re: [PATCH V5 6/6] arm64: dts: qcom: ipq9574: add nodes to bring up q6
Date: Fri, 25 Apr 2025 22:29:39 +0200	[thread overview]
Message-ID: <40aed2f4-ec33-4087-8245-7c4acf861387@oss.qualcomm.com> (raw)
In-Reply-To: <20250417061245.497803-7-gokul.sriram.p@oss.qualcomm.com>

On 4/17/25 8:12 AM, Gokul Sriram Palanisamy wrote:
> From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
> 
> Enable nodes required for q6 remoteproc bring up.
> 
> Signed-off-by: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
> Signed-off-by: Gokul Sriram Palanisamy <gokul.sriram.p@oss.qualcomm.com>
> ---

[...]

> +		q6v5_wcss: remoteproc@cd00000 {
> +			compatible = "qcom,ipq9574-wcss-sec-pil";
> +			reg = <0x0cd00000 0x4040>;

0x10_000-long

> +			firmware-name = "ath11k/IPQ9574/hw1.0/q6_fw.mbn";
> +			interrupts-extended = <&intc GIC_SPI 325 IRQ_TYPE_EDGE_RISING>,
> +					      <&smp2p_wcss_in 0 IRQ_TYPE_NONE>,
> +					      <&smp2p_wcss_in 1 IRQ_TYPE_NONE>,
> +					      <&smp2p_wcss_in 2 IRQ_TYPE_NONE>,
> +					      <&smp2p_wcss_in 3 IRQ_TYPE_NONE>;
> +			interrupt-names = "wdog",
> +					  "fatal",
> +					  "ready",
> +					  "handover",
> +					  "stop-ack";
> +
> +			qcom,smem-states = <&smp2p_wcss_out 1>,
> +					   <&smp2p_wcss_out 0>;
> +			qcom,smem-state-names = "stop",
> +						"shutdown";
> +			memory-region = <&q6_region>;
> +
> +			glink-edge {
> +				interrupts = <GIC_SPI 321 IRQ_TYPE_EDGE_RISING>;

Shouldn't this be 323?

Konrad

  reply	other threads:[~2025-04-25 20:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17  6:12 [PATCH V5 0/6] Add new driver for WCSS secure PIL loading Gokul Sriram Palanisamy
2025-04-17  6:12 ` [PATCH V5 1/6] firmware: qcom_scm: ipq5332: add support to pass metadata size Gokul Sriram Palanisamy
2025-04-17  6:12 ` [PATCH V5 2/6] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL Gokul Sriram Palanisamy
2025-04-25  6:22   ` Krzysztof Kozlowski
2025-05-05  4:29     ` Gokul Sriram P
2025-04-17  6:12 ` [PATCH V5 3/6] remoteproc: qcom: add hexagon based WCSS secure PIL driver Gokul Sriram Palanisamy
2025-04-25 11:47   ` Konrad Dybcio
2025-05-05 12:30     ` Gokul Sriram P
2025-05-05 13:07       ` Konrad Dybcio
2025-05-05 13:12         ` Gokul Sriram P
2025-05-05 13:10     ` Gokul Sriram P
2025-04-17  6:12 ` [PATCH V5 4/6] arm64: dts: qcom: ipq5332: add nodes to bringup q6 Gokul Sriram Palanisamy
2025-04-25 20:23   ` Konrad Dybcio
2025-05-15  4:16     ` Gokul Sriram P
2025-05-15  8:15       ` Dmitry Baryshkov
2025-05-15 15:32         ` Konrad Dybcio
2025-04-17  6:12 ` [PATCH V5 5/6] arm64: dts: qcom: ipq5424: add nodes to bring up q6 Gokul Sriram Palanisamy
2025-04-25 20:27   ` Konrad Dybcio
2025-05-05 13:47     ` Gokul Sriram P
2025-05-05 13:53       ` Konrad Dybcio
2025-04-17  6:12 ` [PATCH V5 6/6] arm64: dts: qcom: ipq9574: " Gokul Sriram Palanisamy
2025-04-25 20:29   ` Konrad Dybcio [this message]
2025-11-26  5:50     ` Varadarajan Narayanan
2025-11-28 11:09       ` Konrad Dybcio
2025-04-17 13:51 ` [PATCH V5 0/6] Add new driver for WCSS secure PIL loading Rob Herring (Arm)

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=40aed2f4-ec33-4087-8245-7c4acf861387@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gokul.sriram.p@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=quic_mmanikan@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=robh@kernel.org \
    --cc=vignesh.viswanathan@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