From: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
To: Nickolay Goppen <setotau@mainlining.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@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,
~postmarketos/upstreaming@lists.sr.ht,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v2 2/3] arm64: dts: qcom: sdm630: set adsp compute-cbs' regs properly
Date: Mon, 20 Apr 2026 16:14:12 +0530 [thread overview]
Message-ID: <e93efcbd-42e1-4f1b-a5cf-c6dc500db63b@oss.qualcomm.com> (raw)
In-Reply-To: <20260420-qcom-sdm660-cdsp-adsp-fastrpc-dts-fix-v2-2-f6c7ab3c889a@mainlining.org>
On 20-04-2026 15:12, Nickolay Goppen wrote:
> Changing FastRPC compute-cbs' reg values to matching iommu streams
> solves SMMU translation errors when trying to use FastRPC on ADSP
> so change FastRPC compute-cbs' reg values that way
>
> Fixes: af2ce7296643 ("arm64: dts: qcom: sdm630: Add FastRPC nodes to ADSP")
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> Signed-off-by: Nickolay Goppen <setotau@mainlining.org>
> ---
> arch/arm64/boot/dts/qcom/sdm630.dtsi | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm630.dtsi b/arch/arm64/boot/dts/qcom/sdm630.dtsi
> index bef3213165d6..4b47efdb57b2 100644
> --- a/arch/arm64/boot/dts/qcom/sdm630.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm630.dtsi
> @@ -2459,27 +2459,27 @@ fastrpc {
> #address-cells = <1>;
> #size-cells = <0>;
>
> - compute-cb@1 {
> + compute-cb@3 {
> compatible = "qcom,fastrpc-compute-cb";
> - reg = <1>;
> + reg = <3>;
> iommus = <&lpass_smmu 3>;
> };
>
> - compute-cb@2 {
> + compute-cb@7 {
> compatible = "qcom,fastrpc-compute-cb";
> - reg = <2>;
> + reg = <7>;
> iommus = <&lpass_smmu 7>;
> };
>
> - compute-cb@3 {
> + compute-cb@8 {
> compatible = "qcom,fastrpc-compute-cb";
> - reg = <3>;
> + reg = <8>;
> iommus = <&lpass_smmu 8>;
> };
>
> - compute-cb@4 {
> + compute-cb@9 {
> compatible = "qcom,fastrpc-compute-cb";
> - reg = <4>;
> + reg = <9>;
> iommus = <&lpass_smmu 9>;
> };
> };
>
Reviewed-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
next prev parent reply other threads:[~2026-04-20 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 9:42 [PATCH v2 0/3] arm64: dts: qcom: sdm630/660 FastRPC fixes Nickolay Goppen
2026-04-20 9:42 ` [PATCH v2 1/3] arm64: dts: qcom: sdm660: set cdsp compute-cbs' regs properly Nickolay Goppen
2026-04-20 10:43 ` Ekansh Gupta
2026-04-20 9:42 ` [PATCH v2 2/3] arm64: dts: qcom: sdm630: set adsp " Nickolay Goppen
2026-04-20 10:44 ` Ekansh Gupta [this message]
2026-04-20 9:42 ` [PATCH v2 3/3] arm64: dts: qcom: sdm630: assign adsp_mem region to ADSP FastRPC node Nickolay Goppen
2026-04-20 10:42 ` Ekansh Gupta
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=e93efcbd-42e1-4f1b-a5cf-c6dc500db63b@oss.qualcomm.com \
--to=ekansh.gupta@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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=setotau@mainlining.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