devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nickolay Goppen <setotau@mainlining.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: 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>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht, linux@mainlining.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: sdm630/660: Add CDSP-related nodes
Date: Mon, 20 Oct 2025 18:27:25 +0300	[thread overview]
Message-ID: <f8daddfd-e0ec-4acd-afc5-cf0969aebb9f@mainlining.org> (raw)
In-Reply-To: <5hbc24lihvau7s2opzcxxgxkzugmbqmdtqwy23m45j4po23lnh@jyjlbgfjaddw>


20.10.2025 16:14, Dmitry Baryshkov пишет:
> On Sun, Oct 19, 2025 at 07:27:06PM +0300, Nickolay Goppen wrote:
>> In order to enable CDSP support for SDM660 SoC:
>>   * add shared memory p2p nodes for CDSP
>>   * add CDSP-specific smmu node
>>   * add CDSP peripheral image loader node
>>
>> Memory region for CDSP in SDM660 occupies the same spot as
>> TZ buffer mem defined in sdm630.dtsi (which does not have CDSP).
>> In sdm660.dtsi replace buffer_mem inherited from SDM630 with
>> cdsp_region, which is also larger in size.
>>
>> SDM636 also doesn't have CDSP, so remove inherited from sdm660.dtsi
>> related nodes and add buffer_mem back.
>>
>> Signed-off-by: Nickolay Goppen <setotau@mainlining.org>
>> ---
>>   arch/arm64/boot/dts/qcom/sdm630.dtsi |   2 +-
>>   arch/arm64/boot/dts/qcom/sdm636.dtsi |  14 ++++
>>   arch/arm64/boot/dts/qcom/sdm660.dtsi | 152 +++++++++++++++++++++++++++++++++++
>>   3 files changed, 167 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sdm630.dtsi b/arch/arm64/boot/dts/qcom/sdm630.dtsi
>> index 8b1a45a4e56e..a6a1933229b9 100644
>> --- a/arch/arm64/boot/dts/qcom/sdm630.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sdm630.dtsi
>> @@ -563,7 +563,7 @@ modem_smp2p_in: slave-kernel {
>>   		};
>>   	};
>>   
>> -	soc@0 {
>> +	soc: soc@0 {
>>   		#address-cells = <1>;
>>   		#size-cells = <1>;
>>   		ranges = <0 0 0 0xffffffff>;
>> diff --git a/arch/arm64/boot/dts/qcom/sdm636.dtsi b/arch/arm64/boot/dts/qcom/sdm636.dtsi
>> index ae15d81fa3f9..41e4e97f7747 100644
>> --- a/arch/arm64/boot/dts/qcom/sdm636.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sdm636.dtsi
>> @@ -16,6 +16,20 @@
>>    * be addressed when the aforementioned
>>    * peripherals will be enabled upstream.
>>    */
>> +/delete-node/ &cdsp_pil;
>> +/delete-node/ &cdsp_smmu;
>> +/delete-node/ &cdsp_region;
>> +
>> +/ {
>> +	/delete-node/ smp2p-cdsp;
>> +
>> +	reserved-memory {
>> +		buffer_mem: tzbuffer@94a00000 {
>> +			reg = <0x00 0x94a00000 0x00 0x100000>;
>> +			no-map;
>> +		};
>> +	};
>> +};
> This probably means that we need to invert things and make SDM636
> inherit SDM630 and SDM660 inherit SDM636. Would you mind doing that as a
> part of this patchset?
I'd mind
>>   
>>   &adreno_gpu {
>>   	compatible = "qcom,adreno-509.0", "qcom,adreno";

-- 
Best regards,
Nickolay


  reply	other threads:[~2025-10-20 15:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-19 16:27 [PATCH 0/2] arm64: dts: qcom: Add support for SDM660 CDSP and ADSP FastRPC Nickolay Goppen
2025-10-19 16:27 ` [PATCH 1/2] arm64: dts: qcom: sdm630/660: Add CDSP-related nodes Nickolay Goppen
2025-10-20 12:27   ` Konrad Dybcio
2025-10-20 12:38     ` Nickolay Goppen
2025-10-20 12:39       ` Konrad Dybcio
2025-10-20 13:14   ` Dmitry Baryshkov
2025-10-20 15:27     ` Nickolay Goppen [this message]
2025-10-20 15:42       ` Nickolay Goppen
2025-10-22 17:17         ` Konrad Dybcio
2025-10-23 14:23           ` Dmitry Baryshkov
2025-10-19 16:27 ` [PATCH 2/2] arm64: dts: qcom: sdm630: Add FastRPC nodes to ADSP Nickolay Goppen
2025-10-20 12:29   ` Konrad Dybcio

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=f8daddfd-e0ec-4acd-afc5-cf0969aebb9f@mainlining.org \
    --to=setotau@mainlining.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@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=linux@mainlining.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;
as well as URLs for NNTP newsgroup(s).