From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Mukesh Ojha" <quic_mojha@quicinc.com>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
<cros-qcom-dts-watchers@chromium.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Matti Lehtimäki" <matti.lehtimaki@gmail.com>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/9] arm64: dts: qcom: sc7280: Add CDSP node
Date: Mon, 30 Oct 2023 10:12:14 +0100 [thread overview]
Message-ID: <CWLNP6QNUXN1.SNVACF2IEGI8@fairphone.com> (raw)
In-Reply-To: <7934a36a-9438-719a-2ed0-4a78757b044b@quicinc.com>
On Mon Oct 30, 2023 at 10:04 AM CET, Mukesh Ojha wrote:
>
>
> On 10/27/2023 7:50 PM, Luca Weiss wrote:
> > Add the node for the ADSP found on the SC7280 SoC, using standard
> > Qualcomm firmware.
> >
> > The memory region for sc7280-chrome-common.dtsi is taken from msm-5.4
> > yupik.dtsi since the other areas also seem to match that file there,
> > though I cannot be sure there.
> >
> > Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> > ---
> > arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi | 5 +
> > arch/arm64/boot/dts/qcom/sc7280.dtsi | 138 +++++++++++++++++++++
> > 2 files changed, 143 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi b/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi
> > index eb55616e0892..6e5a9d4c1fda 100644
> > --- a/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi
> > @@ -29,6 +29,11 @@ adsp_mem: memory@86700000 {
> > no-map;
> > };
> >
> > + cdsp_mem: memory@88f00000 {
> > + reg = <0x0 0x88f00000 0x0 0x1e00000>;
> > + no-map;
> > + };
> > +
>
> Just a question, why to do it here, if chrome does not use this ?
Other memory regions in sc7280.dtsi also get referenced but not actually
defined in that file, like mpss_mem and wpss_mem. Alternatively we can
also try and solve this differently, but then we should probably also
adjust mpss and wpss to be consistent.
Apart from either declaring cdsp_mem in sc7280.dtsi or
"/delete-property/ memory-region;" for CDSP I don't really have better
ideas though.
I also imagine these ChromeOS devices will want to enable cdsp at some
point but I don't know any plans there.
Regards
Luca
>
> -Mukesh
>
> > camera_mem: memory@8ad00000 {
> > reg = <0x0 0x8ad00000 0x0 0x500000>;
> > no-map;
> > diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi b/arch/arm64/boot/dts/qcom/sc7280.dtsi
> > index cc153f4e6979..e15646289bf7 100644
> > --- a/arch/arm64/boot/dts/qcom/sc7280.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi
> > @@ -3815,6 +3815,144 @@ nsp_noc: interconnect@a0c0000 {
> > qcom,bcm-voters = <&apps_bcm_voter>;
> > };
> >
> > + remoteproc_cdsp: remoteproc@a300000 {
> > + compatible = "qcom,sc7280-cdsp-pas";
> > + reg = <0 0x0a300000 0 0x10000>;
> > +
> > + interrupts-extended = <&intc GIC_SPI 578 IRQ_TYPE_LEVEL_HIGH>,
> > + <&cdsp_smp2p_in 0 IRQ_TYPE_EDGE_RISING>,
> > + <&cdsp_smp2p_in 1 IRQ_TYPE_EDGE_RISING>,
> > + <&cdsp_smp2p_in 2 IRQ_TYPE_EDGE_RISING>,
> > + <&cdsp_smp2p_in 3 IRQ_TYPE_EDGE_RISING>,
> > + <&cdsp_smp2p_in 7 IRQ_TYPE_EDGE_RISING>;
> > + interrupt-names = "wdog", "fatal", "ready", "handover",
> > + "stop-ack", "shutdown-ack";
> > +
> > + clocks = <&rpmhcc RPMH_CXO_CLK>;
> > + clock-names = "xo";
> > +
> > + power-domains = <&rpmhpd SC7280_CX>,
> > + <&rpmhpd SC7280_MX>;
> > + power-domain-names = "cx", "mx";
> > +
> > + interconnects = <&nsp_noc MASTER_CDSP_PROC 0 &mc_virt SLAVE_EBI1 0>;
> > +
> > + memory-region = <&cdsp_mem>;
> > +
> > + qcom,qmp = <&aoss_qmp>;
> > +
> > + qcom,smem-states = <&cdsp_smp2p_out 0>;
> > + qcom,smem-state-names = "stop";
> > +
> > + status = "disabled";
> > +
> > + glink-edge {
> > + interrupts-extended = <&ipcc IPCC_CLIENT_CDSP
> > + IPCC_MPROC_SIGNAL_GLINK_QMP
> > + IRQ_TYPE_EDGE_RISING>;
> > + mboxes = <&ipcc IPCC_CLIENT_CDSP
> > + IPCC_MPROC_SIGNAL_GLINK_QMP>;
> > +
> > + label = "cdsp";
> > + qcom,remote-pid = <5>;
> > +
> > + fastrpc {
> > + compatible = "qcom,fastrpc";
> > + qcom,glink-channels = "fastrpcglink-apps-dsp";
> > + label = "cdsp";
> > + qcom,non-secure-domain;
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + compute-cb@1 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <1>;
> > + iommus = <&apps_smmu 0x11a1 0x0420>,
> > + <&apps_smmu 0x1181 0x0420>;
> > + };
> > +
> > + compute-cb@2 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <2>;
> > + iommus = <&apps_smmu 0x11a2 0x0420>,
> > + <&apps_smmu 0x1182 0x0420>;
> > + };
> > +
> > + compute-cb@3 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <3>;
> > + iommus = <&apps_smmu 0x11a3 0x0420>,
> > + <&apps_smmu 0x1183 0x0420>;
> > + };
> > +
> > + compute-cb@4 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <4>;
> > + iommus = <&apps_smmu 0x11a4 0x0420>,
> > + <&apps_smmu 0x1184 0x0420>;
> > + };
> > +
> > + compute-cb@5 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <5>;
> > + iommus = <&apps_smmu 0x11a5 0x0420>,
> > + <&apps_smmu 0x1185 0x0420>;
> > + };
> > +
> > + compute-cb@6 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <6>;
> > + iommus = <&apps_smmu 0x11a6 0x0420>,
> > + <&apps_smmu 0x1186 0x0420>;
> > + };
> > +
> > + compute-cb@7 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <7>;
> > + iommus = <&apps_smmu 0x11a7 0x0420>,
> > + <&apps_smmu 0x1187 0x0420>;
> > + };
> > +
> > + compute-cb@8 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <8>;
> > + iommus = <&apps_smmu 0x11a8 0x0420>,
> > + <&apps_smmu 0x1188 0x0420>;
> > + };
> > +
> > + /* note: secure cb9 in downstream */
> > +
> > + compute-cb@11 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <11>;
> > + iommus = <&apps_smmu 0x11ab 0x0420>,
> > + <&apps_smmu 0x118b 0x0420>;
> > + };
> > +
> > + compute-cb@12 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <12>;
> > + iommus = <&apps_smmu 0x11ac 0x0420>,
> > + <&apps_smmu 0x118c 0x0420>;
> > + };
> > +
> > + compute-cb@13 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <13>;
> > + iommus = <&apps_smmu 0x11ad 0x0420>,
> > + <&apps_smmu 0x118d 0x0420>;
> > + };
> > +
> > + compute-cb@14 {
> > + compatible = "qcom,fastrpc-compute-cb";
> > + reg = <14>;
> > + iommus = <&apps_smmu 0x11ae 0x0420>,
> > + <&apps_smmu 0x118e 0x0420>;
> > + };
> > + };
> > + };
> > + };
> > +
> > usb_1: usb@a6f8800 {
> > compatible = "qcom,sc7280-dwc3", "qcom,dwc3";
> > reg = <0 0x0a6f8800 0 0x400>;
> >
next prev parent reply other threads:[~2023-10-30 9:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231027-sc7280-remoteprocs-v1-0-05ce95d9315a@fairphone.com>
[not found] ` <20231027-sc7280-remoteprocs-v1-1-05ce95d9315a@fairphone.com>
2023-10-28 8:01 ` [PATCH 1/9] dt-bindings: remoteproc: qcom: sc7180-pas: Fix SC7280 MPSS PD-names Krzysztof Kozlowski
[not found] ` <20231027-sc7280-remoteprocs-v1-2-05ce95d9315a@fairphone.com>
2023-10-28 8:04 ` [PATCH 2/9] arm64: dts: qcom: sc7280: Remove unused second MPSS reg Krzysztof Kozlowski
[not found] ` <20231027-sc7280-remoteprocs-v1-3-05ce95d9315a@fairphone.com>
2023-10-28 8:05 ` [PATCH 3/9] dt-bindings: remoteproc: qcom: sc7180-pas: Add SC7280 compatibles Krzysztof Kozlowski
[not found] ` <20231027-sc7280-remoteprocs-v1-6-05ce95d9315a@fairphone.com>
2023-10-28 8:05 ` [PATCH 6/9] arm64: dts: qcom: sc7280: Add ADSP node Krzysztof Kozlowski
[not found] ` <20231027-sc7280-remoteprocs-v1-7-05ce95d9315a@fairphone.com>
2023-10-28 8:06 ` [PATCH 7/9] arm64: dts: qcom: sc7280: Add CDSP node Krzysztof Kozlowski
2023-10-30 9:04 ` Mukesh Ojha
2023-10-30 9:12 ` Luca Weiss [this message]
2023-10-30 14:11 ` Doug Anderson
2023-10-30 14:43 ` Luca Weiss
2023-10-30 15:03 ` Doug Anderson
2023-10-31 6:44 ` Mukesh Ojha
2023-10-31 6:51 ` Luca Weiss
[not found] ` <20231027-sc7280-remoteprocs-v1-8-05ce95d9315a@fairphone.com>
2023-10-30 19:26 ` [PATCH 8/9] arm64: dts: qcom: qcm6490-fairphone-fp5: Enable various remoteprocs Konrad Dybcio
2023-10-31 10:32 ` Luca Weiss
[not found] ` <20231027-sc7280-remoteprocs-v1-9-05ce95d9315a@fairphone.com>
2023-10-30 19:26 ` [PATCH 9/9] arm64: dts: qcom: qcm6490-fairphone-fp5: Enable WiFi Konrad Dybcio
2023-10-31 10:31 ` Luca Weiss
2023-10-31 10:32 ` Konrad Dybcio
2023-11-04 13:23 ` Dmitry Baryshkov
2023-11-13 12:22 ` Kalle Valo
2023-11-13 12:50 ` Luca Weiss
2023-11-13 14:10 ` Kalle Valo
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=CWLNP6QNUXN1.SNVACF2IEGI8@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=matti.lehtimaki@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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