From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vignesh Viswanathan <quic_viswanat@quicinc.com>
Subject: Re: [PATCH] arm64: dts: qcom: ipq5424: Add reserved memory for TF-A
Date: Wed, 25 Jun 2025 10:20:57 +0530 [thread overview]
Message-ID: <7d641576-7ec7-46f2-ad53-e0b8b36351d1@oss.qualcomm.com> (raw)
In-Reply-To: <0826de9f-0125-44d9-84cd-1c52ba199a4a@oss.qualcomm.com>
On 6/24/2025 6:57 PM, Konrad Dybcio wrote:
> On 6/24/25 12:36 PM, Kathiravan Thirumoorthy wrote:
>> From: Vignesh Viswanathan <quic_viswanat@quicinc.com>
>>
>> IPQ5424 supports both TZ and TF-A as secure software options and various
>> DDR sizes. In most cases, TF-A or TZ is loaded at the same memory
>> location, but in the 256MB DDR configuration TF-A is loaded at a different
>> region.
>>
>> So, add the reserved memory node for TF-A and keep it disabled by default.
>> During bootup, U-Boot will detect which secure software is running and
>> enable or disable the node accordingly.
>>
>> Signed-off-by: Vignesh Viswanathan <quic_viswanat@quicinc.com>
>> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
>> ---
> Can the said u-boot simply dynamically add the reservation then?
Yeah it could have been done in U-Boot itself but it wasn't. 256MB DDR
configuration solution is already shipped out and the stock U-Boot
enable this node to avoid the random issues.
>
> Konrad
next prev parent reply other threads:[~2025-06-25 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 10:36 Kathiravan Thirumoorthy
2025-06-24 13:27 ` Konrad Dybcio
2025-06-25 4:50 ` Kathiravan Thirumoorthy [this message]
2025-07-23 7:04 ` Kathiravan Thirumoorthy
2025-08-05 13:22 ` Konrad Dybcio
2025-08-07 10:33 ` Kathiravan Thirumoorthy
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=7d641576-7ec7-46f2-ad53-e0b8b36351d1@oss.qualcomm.com \
--to=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@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=quic_viswanat@quicinc.com \
--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®