[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8709975b-1f1b-42d3-b0aa-762b2b606c77@oss.qualcomm.com>
Date: Fri, 6 Dec 2024 11:52:18 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] arm64: dts: qcom: sm8750: Add CDSP
On 6.12.2024 10:10 AM, Krzysztof Kozlowski wrote:
> On 05/12/2024 18:32, Konrad Dybcio wrote:
>> On 22.11.2024 4:26 PM, Krzysztof Kozlowski wrote:
>>> Add nodes for the CDSP and its SMP2P. These are compatible with earlier
>>> SM8650 with difference in one more interrupt.
>>>
>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>>> ---
>>
>> [...]
>>
>>> +
>>> + remoteproc_cdsp: remoteproc@...00000 {
>>> + compatible = "qcom,sm8750-cdsp-pas", "qcom,sm8650-cdsp-pas";
>>> + reg = <0x0 0x32300000 0x0 0x1400000>;
>>
>> The size seems to be 0x100000
> Even 0x10000 (one less 0) according to downstream DTS. 0x100000 would be
> entire touring qdsp6v7 map (1 MB).
>
> However we always - sm8450, sm8550, sm8650 - map here 20 MB for some
> reason. Any ideas?
No clue. I made this comment based on what the computer told me.
Maybe some Q6 folks would know..
> Let's correct all platforms to 0x100000?
After we figure it out, sure
Konrad
Powered by blists - more mailing lists