From: Konrad Dybcio <konrad.dybcio@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>,
Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH 3/4] arm64: dts: qcom: sdm630: describe adsp_mem region properly
Date: Wed, 15 Apr 2026 11:52:17 +0200 [thread overview]
Message-ID: <70d4dbe7-0e5b-4065-858e-b5a57bbf45e3@oss.qualcomm.com> (raw)
In-Reply-To: <20260415-qcom-sdm660-cdsp-adsp-fastrpc-dts-fix-v1-3-03b475b29554@mainlining.org>
On 4/15/26 11:40 AM, Nickolay Goppen wrote:
> Downstream [1] this region is marked as shared and reusable so
> describe it that way.
>
> [1]: https://github.com/xiaomi-sdm660/android_kernel_xiaomi_sdm660/blob/11-EAS/arch/arm/boot/dts/qcom/sdm660.dtsi#L448
>
> Signed-off-by: Nickolay Goppen <setotau@mainlining.org>
> ---
+Ekansh some insight, please?
We're giving away that memory via qcom_scm_assign_mem() anyway
and I would assume that making it not-"no-map" could introduce issues
when the OS tries to access that region
Konrad
> arch/arm64/boot/dts/qcom/sdm630.dtsi | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm630.dtsi b/arch/arm64/boot/dts/qcom/sdm630.dtsi
> index 4b47efdb57b2..13094b5e9339 100644
> --- a/arch/arm64/boot/dts/qcom/sdm630.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm630.dtsi
> @@ -495,8 +495,9 @@ venus_region: venus@9f800000 {
> };
>
> adsp_mem: adsp-region@f6000000 {
> + compatible = "shared-dma-pool";
> reg = <0x0 0xf6000000 0x0 0x800000>;
> - no-map;
> + reusable;
> };
>
> qseecom_mem: qseecom-region@f6800000 {
>
next prev parent reply other threads:[~2026-04-15 9:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 9:40 [PATCH 0/4] arm64: dts: qcom: sdm630/660 FastRPC fixes Nickolay Goppen
2026-04-15 9:40 ` [PATCH 1/4] arm64: dts: qcom: sdm660: set cdsp compute-cbs' regs properly Nickolay Goppen
2026-04-15 9:43 ` Konrad Dybcio
2026-04-17 18:08 ` Dmitry Baryshkov
2026-04-15 9:40 ` [PATCH 2/4] arm64: dts: qcom: sdm630: set adsp " Nickolay Goppen
2026-04-15 9:50 ` Konrad Dybcio
2026-04-17 18:08 ` Dmitry Baryshkov
2026-04-15 9:40 ` [PATCH 3/4] arm64: dts: qcom: sdm630: describe adsp_mem region properly Nickolay Goppen
2026-04-15 9:52 ` Konrad Dybcio [this message]
2026-04-15 10:03 ` Nickolay Goppen
2026-04-17 15:15 ` Ekansh Gupta
2026-04-17 17:36 ` Nickolay Goppen
2026-04-18 1:17 ` Ekansh Gupta
2026-04-21 8:29 ` Ekansh Gupta
2026-04-21 8:32 ` Nickolay Goppen
2026-04-22 9:38 ` Ekansh Gupta
2026-04-22 10:24 ` Konrad Dybcio
2026-04-22 15:29 ` Dmitry Baryshkov
2026-04-15 9:40 ` [PATCH 4/4] arm64: dts: qcom: sdm630: assign adsp_mem region to ADSP FastRPC node Nickolay Goppen
2026-04-17 18:12 ` Dmitry Baryshkov
2026-04-18 1:20 ` 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=70d4dbe7-0e5b-4065-858e-b5a57bbf45e3@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ekansh.gupta@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