From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Alexey Minnekhanov <alexeymin@minlexx.ru>,
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: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v3 3/4] arm64: dts: qcom: sdm630: describe adsp_mem region properly
Date: Thu, 2 Jul 2026 14:09:57 +0200 [thread overview]
Message-ID: <9281844d-5570-4100-8517-d1bac4e08a30@oss.qualcomm.com> (raw)
In-Reply-To: <edf331e2-73a5-4afd-9a44-56cb786626c5@minlexx.ru>
On 7/1/26 5:31 PM, Alexey Minnekhanov wrote:
> On 01.07.2026 15:48, Konrad Dybcio wrote:
>> On 4/27/26 5:20 PM, Nickolay Goppen wrote:
>>>
>>> 27.04.2026 14:49, Konrad Dybcio wrote:
>>>> Please make this = <0x0 0x80000000 0x0 0x80000000>; instead, since the RAM
>>>> starts at 0x80000000
>>>
>>> +Alexey Min found out that on 3 GiB xiaomi-lavender RAM starts at 0x40000000
>>>
>>> 40000000-855fffff : System RAM
>>> 40080000-41bfffff : Kernel code
>>> 42600000-42fd0fff : Kernel data
>>> 88f00000-8abfffff : System RAM
>>> 95000000-feabffff : System RAM
>>
>> My docs happen to be silent on this subject..
>> Do you have a device that has more/less RAM to compare?
>>
>
> I do have quite a bunch of devices based on sdm630/636/660.
> Logs from UART including longs from stock bootloader are only
> available for lavender, though. For others I collected dumps
> of /proc/iomem (and debug/memblock/memory):
Thanks. Let's do 0x40000000 - 0xff...ff then, I think that Linux
should figure out what to if there's no memory below 0x8..
Konrad
next prev parent reply other threads:[~2026-07-02 12:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 15:39 [PATCH v3 0/4] arm64: dts: qcom: sdm630/660 FastRPC fixes Nickolay Goppen
2026-04-22 15:39 ` [PATCH v3 1/4] arm64: dts: qcom: sdm660: set cdsp compute-cbs' regs properly Nickolay Goppen
2026-04-22 15:39 ` [PATCH v3 2/4] arm64: dts: qcom: sdm630: set adsp " Nickolay Goppen
2026-04-22 15:39 ` [PATCH v3 3/4] arm64: dts: qcom: sdm630: describe adsp_mem region properly Nickolay Goppen
2026-04-22 15:52 ` Dmitry Baryshkov
2026-04-23 9:09 ` Ekansh Gupta
2026-04-27 11:49 ` Konrad Dybcio
2026-04-27 12:00 ` Nickolay Goppen
2026-04-27 12:08 ` Konrad Dybcio
2026-04-27 12:28 ` Nickolay Goppen
2026-04-27 15:20 ` Nickolay Goppen
2026-04-27 15:28 ` Alexey Minnekhanov
2026-07-01 12:48 ` Konrad Dybcio
2026-07-01 15:31 ` Alexey Minnekhanov
2026-07-02 12:09 ` Konrad Dybcio [this message]
2026-04-22 15:39 ` [PATCH v3 4/4] arm64: dts: qcom: sdm630: assign adsp_mem region to ADSP FastRPC node Nickolay Goppen
2026-04-23 9:09 ` Ekansh Gupta
2026-04-23 11:05 ` Konrad Dybcio
2026-04-23 13:06 ` Nickolay Goppen
2026-04-23 13:08 ` Konrad Dybcio
2026-04-23 13:48 ` Nickolay Goppen
2026-04-23 14:39 ` Ekansh Gupta
2026-04-23 15:00 ` Nickolay Goppen
2026-04-24 10:01 ` 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=9281844d-5570-4100-8517-d1bac4e08a30@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=alexeymin@minlexx.ru \
--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