From: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shawn Guo <shengchao.guo@oss.qualcomm.com>
Subject: Re: [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord
Date: Sun, 18 Oct 2026 11:41:35 +0530 [thread overview]
Message-ID: <0324a8fc-fb08-4ace-bfda-d65cefaf3909@oss.qualcomm.com> (raw)
In-Reply-To: <3c9b6695-f292-4bb8-a69d-9de253e36f80@oss.qualcomm.com>
On 10/16/2026 2:22 PM, Konrad Dybcio wrote:
> On 10/16/26 7:39 AM, Anurag Pateriya wrote:
>> Add the SoCCP (System on Chip Control Processor) remoteproc node and
>> its SMP2P configuration at the SoC level in nord.dtsi, and wire up
>> the clock and power-domain dependencies shared by all Nord embedded
>> variants in nord-embedded.dtsi.
>
> [...]
>
>> + remoteproc_soccp: remoteproc@d00000 {
>> + compatible = "qcom,nord-soccp-pas";
>> + reg = <0x0 0x00d00000 0x0 0x200000>;
>> +
>> + interrupts-extended = <&intc GIC_SPI 167 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 0 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 1 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 2 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 3 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 9 IRQ_TYPE_EDGE_RISING>;
>> + interrupt-names = "wdog",
>> + "fatal",
>> + "ready",
>> + "handover",
>> + "stop-ack",
>> + "pong";
>> +
>> + memory-region = <&soccp_mem>;
>> +
>> + qcom,smem-states = <&smp2p_soccp_out 0>,
>> + <&smp2p_soccp_out 8>;
>> + qcom,smem-state-names = "stop",
>> + "ping";
>> +
>> + status = "disabled";
>
> The SoCCP should be always enabled, especially given it's left on by
> the bootloader.
>
Ok, Thanks. I will enable this in next version.
> [...]
>
>> + bwmon_cluster2: pmu@1014400 {
>> + reg = <0x0 0x01014400 0x0 0x600>;
>> + interrupts = <GIC_SPI 739 IRQ_TYPE_LEVEL_HIGH>;
>> + operating-points-v2 = <&bwmon_cluster_opp_table>;
>> + };
>
> This is somehow present yet not mentioned at all by the commit message
>
> Konrad
Yes. I will remove these additional changes.
Thanks,
Anurag
next prev parent reply other threads:[~2026-10-18 6:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 5:39 [PATCH RFC 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya
2026-10-16 5:39 ` [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya
2026-10-16 8:52 ` Konrad Dybcio
2026-10-18 6:11 ` Anurag Pateriya [this message]
2026-10-16 9:05 ` Abel Vesa
2026-10-18 6:15 ` Anurag Pateriya
2026-10-16 5:39 ` [PATCH RFC 2/3] arm64: dts: qcom: nord: Enable SoCCP on RRD board Anurag Pateriya
2026-10-16 8:52 ` Konrad Dybcio
2026-10-18 6:18 ` Anurag Pateriya
2026-10-16 5:39 ` [PATCH RFC 3/3] arm64: dts: qcom: nord: Enable SoCCP on Ride-Embedded board Anurag Pateriya
2026-10-16 9:03 ` Abel Vesa
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=0324a8fc-fb08-4ace-bfda-d65cefaf3909@oss.qualcomm.com \
--to=anurag.pateriya@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shengchao.guo@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