From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Ananthu C V <ananthu.cv@oss.qualcomm.com>,
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>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v5 2/3] arm64: dts: qcom: fix SoCCP memory mappings for Glymur
Date: Thu, 16 Jul 2026 17:16:56 +0200 [thread overview]
Message-ID: <9e0ea6cf-ec91-4017-a14d-a1f7c4921f37@oss.qualcomm.com> (raw)
In-Reply-To: <20260707-glymur-soccp-v5-2-053993f0c6fe@oss.qualcomm.com>
On 7/7/26 12:12 PM, Ananthu C V wrote:
> The currently listed SoCCP and SoCCP DTB reserved memory regions
> don't align with the memory requested by the SoCCP Firmware. Fix
> this by updating the SoCCP/SoCCP DTB memory regions to reflect the
> memory region requirements of the SoCCP firmware, as described in
> the Glymur v21 memory map release.
>
> Signed-off-by: Ananthu C V <ananthu.cv@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/glymur.dtsi | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/glymur.dtsi b/arch/arm64/boot/dts/qcom/glymur.dtsi
> index 20b49af7298e..9ec7c256b80a 100644
> --- a/arch/arm64/boot/dts/qcom/glymur.dtsi
> +++ b/arch/arm64/boot/dts/qcom/glymur.dtsi
> @@ -602,13 +602,13 @@ spss_region_mem: spss@88a00000 {
> no-map;
> };
>
> - soccpdtb_mem: soccpdtb@892e0000 {
> - reg = <0x0 0x892e0000 0x0 0x20000>;
> + soccp_mem: soccp@88e00000 {
> + reg = <0x0 0x88e00000 0x0 0x400000>;
> no-map;
> };
>
> - soccp_mem: soccp@89300000 {
> - reg = <0x0 0x89300000 0x0 0x400000>;
> + soccpdtb_mem: soccpdtb@89200000 {
> + reg = <0x0 0x89200000 0x0 0x20000>;
> no-map;
> };
The updated regions point to "SOCCP Boot [DTB]", whereas the old
regions point to "SOCCP [DTB]". I'm assuming HLOS potentially loading
FW to the boot regions is fine?
Konrad
next prev parent reply other threads:[~2026-07-16 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 10:12 [PATCH v5 0/3] Add remoteproc PAS loader for SoCCP on Glymur DT Ananthu C V
2026-07-07 10:12 ` [PATCH v5 1/3] remoteproc: qcom: pas: add needs_tzmem flag to trigger shmbridge creation Ananthu C V
2026-07-09 7:11 ` Mukesh Ojha
2026-07-07 10:12 ` [PATCH v5 2/3] arm64: dts: qcom: fix SoCCP memory mappings for Glymur Ananthu C V
2026-07-09 7:14 ` Mukesh Ojha
2026-07-09 12:01 ` Ananthu C V
2026-07-16 15:16 ` Konrad Dybcio [this message]
2026-07-17 8:42 ` Ananthu C V
2026-07-07 10:12 ` [PATCH v5 3/3] arm64: dts: qcom: add SoCCP DT node " Ananthu C V
2026-07-16 14:49 ` Konrad Dybcio
2026-07-17 8:46 ` Ananthu C V
2026-07-10 18:07 ` (subset) [PATCH v5 0/3] Add remoteproc PAS loader for SoCCP on Glymur DT Bjorn Andersson
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=9e0ea6cf-ec91-4017-a14d-a1f7c4921f37@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=ananthu.cv@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®