| Message ID | 20240401-msm8996-remoteproc-v1-3-f02ab47fc728@linaro.org (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | arm64: dts: qcom: msm8996: enable fastrpc and glink-edge | expand |
On 31.03.2024 11:10 PM, Dmitry Baryshkov wrote: > From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> > > The ADSP provides fastrpc/compute capabilities. Enable support for the > fastrpc on this DSP. > > Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> > --- > arch/arm64/boot/dts/qcom/msm8996.dtsi | 57 +++++++++++++++++++++++++++++++++++ > 1 file changed, 57 insertions(+) > > diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi > index 7ae499fa7d91..cf7ab01f3af6 100644 > --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi > +++ b/arch/arm64/boot/dts/qcom/msm8996.dtsi > @@ -3545,6 +3545,63 @@ q6routing: routing { > }; > }; > }; > + > + fastrpc { > + compatible = "qcom,fastrpc"; > + qcom,smd-channels = "fastrpcsmd-apps-dsp"; > + label = "adsp"; > + qcom,non-secure-domain; > + #address-cells = <1>; > + #size-cells = <0>; > + > + cb@8 { > + compatible = "qcom,fastrpc-compute-cb"; > + reg = <8>; > + iommus = <&lpass_q6_smmu 8>; > + }; > + > + cb@9 { > + compatible = "qcom,fastrpc-compute-cb"; > + reg = <9>; > + iommus = <&lpass_q6_smmu 9>; > + }; > + > + cb@10 { > + compatible = "qcom,fastrpc-compute-cb"; > + reg = <10>; > + iommus = <&lpass_q6_smmu 10>; > + }; > + > + cb@11 { > + compatible = "qcom,fastrpc-compute-cb"; > + reg = <11>; > + iommus = <&lpass_q6_smmu 11>; > + }; > + > + cb@12 { > + compatible = "qcom,fastrpc-compute-cb"; > + reg = <12>; > + iommus = <&lpass_q6_smmu 12>; > + }; > + > + cb@5 { > + compatible = "qcom,fastrpc-compute-cb"; > + reg = <5>; No need to copy downstream's creative alphabetical-but-not-numerical sorting.. The entries look OK though.. although, any reason we have such a weird binding including faux child nodes and not just an array of iommus? Is the only way to discover the fastrpc nodes' properties such as qcom,non-secure-domain or vmid belonging through hardcoding? Konrad Konrad
On Tue, 2 Apr 2024 at 17:47, Konrad Dybcio <konrad.dybcio@linaro.org> wrote: > > On 31.03.2024 11:10 PM, Dmitry Baryshkov wrote: > > From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> > > > > The ADSP provides fastrpc/compute capabilities. Enable support for the > > fastrpc on this DSP. > > > > Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> > > --- > > arch/arm64/boot/dts/qcom/msm8996.dtsi | 57 +++++++++++++++++++++++++++++++++++ > > 1 file changed, 57 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi > > index 7ae499fa7d91..cf7ab01f3af6 100644 > > --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi > > +++ b/arch/arm64/boot/dts/qcom/msm8996.dtsi > > @@ -3545,6 +3545,63 @@ q6routing: routing { > > }; > > }; > > }; > > + > > + fastrpc { > > + compatible = "qcom,fastrpc"; > > + qcom,smd-channels = "fastrpcsmd-apps-dsp"; > > + label = "adsp"; > > + qcom,non-secure-domain; > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + cb@8 { > > + compatible = "qcom,fastrpc-compute-cb"; > > + reg = <8>; > > + iommus = <&lpass_q6_smmu 8>; > > + }; > > + > > + cb@9 { > > + compatible = "qcom,fastrpc-compute-cb"; > > + reg = <9>; > > + iommus = <&lpass_q6_smmu 9>; > > + }; > > + > > + cb@10 { > > + compatible = "qcom,fastrpc-compute-cb"; > > + reg = <10>; > > + iommus = <&lpass_q6_smmu 10>; > > + }; > > + > > + cb@11 { > > + compatible = "qcom,fastrpc-compute-cb"; > > + reg = <11>; > > + iommus = <&lpass_q6_smmu 11>; > > + }; > > + > > + cb@12 { > > + compatible = "qcom,fastrpc-compute-cb"; > > + reg = <12>; > > + iommus = <&lpass_q6_smmu 12>; > > + }; > > + > > + cb@5 { > > + compatible = "qcom,fastrpc-compute-cb"; > > + reg = <5>; > > No need to copy downstream's creative alphabetical-but-not-numerical > sorting.. Ack, I'll fix the order. > The entries look OK though.. although, any reason we have > such a weird binding including faux child nodes and not just an array > of iommus? Is the only way to discover the fastrpc nodes' properties > such as qcom,non-secure-domain or vmid belonging through hardcoding? No idea here. This is how fastrpc nodes are defined on all existing platforms. Maybe Srini knows the story and the reason behind the bindings??
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi index 7ae499fa7d91..cf7ab01f3af6 100644 --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi +++ b/arch/arm64/boot/dts/qcom/msm8996.dtsi @@ -3545,6 +3545,63 @@ q6routing: routing { }; }; }; + + fastrpc { + compatible = "qcom,fastrpc"; + qcom,smd-channels = "fastrpcsmd-apps-dsp"; + label = "adsp"; + qcom,non-secure-domain; + #address-cells = <1>; + #size-cells = <0>; + + cb@8 { + compatible = "qcom,fastrpc-compute-cb"; + reg = <8>; + iommus = <&lpass_q6_smmu 8>; + }; + + cb@9 { + compatible = "qcom,fastrpc-compute-cb"; + reg = <9>; + iommus = <&lpass_q6_smmu 9>; + }; + + cb@10 { + compatible = "qcom,fastrpc-compute-cb"; + reg = <10>; + iommus = <&lpass_q6_smmu 10>; + }; + + cb@11 { + compatible = "qcom,fastrpc-compute-cb"; + reg = <11>; + iommus = <&lpass_q6_smmu 11>; + }; + + cb@12 { + compatible = "qcom,fastrpc-compute-cb"; + reg = <12>; + iommus = <&lpass_q6_smmu 12>; + }; + + cb@5 { + compatible = "qcom,fastrpc-compute-cb"; + reg = <5>; + iommus = <&lpass_q6_smmu 5>; + }; + + cb@6 { + compatible = "qcom,fastrpc-compute-cb"; + reg = <6>; + iommus = <&lpass_q6_smmu 6>; + }; + + cb@7 { + compatible = "qcom,fastrpc-compute-cb"; + reg = <7>; + iommus = <&lpass_q6_smmu 7>; + }; + }; }; };