From: Aswath Govindraju <a-govindraju@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am64-main: Add SYSFW reserved ranges in OCRAM
Date: Mon, 14 Jun 2021 10:18:57 +0530 [thread overview]
Message-ID: <36ff3c65-2f5e-2997-9fb5-a5e8d3230a75@ti.com> (raw)
In-Reply-To: <84e5865f-e107-f0e1-ca8b-b6bd655e92e6@ti.com>
Hi Vignesh,
On 12/06/21 12:51 pm, Vignesh Raghavendra wrote:
> +Aswath
>
> On 6/12/21 12:46 AM, Nishanth Menon wrote:
>> On 19:36-20210609, Vignesh Raghavendra wrote:
>>> Last 256K of OCRAM (256K@0x701c0000) is reserved for SYSFW usage. Hence
>>> add an entry in DT so that its not used for generic pool memory
>>> allocation.
>>
>> Are you really sure?? I know that I had set a budget for 16K in sysfw
>> when I did the memory split up for sysfw of which 16k is actually used.
>>
>> Not sure where this 256K bucket started off from.. am I missing
>> something here?
>>
>
> Per: http://software-dl.ti.com/tisci/esd/latest/5_soc_doc/am64x/firewalls.html
>
> 24 dmsc 0x44060000 0x4407BFFF dmsc,rwcd // alias for 0x701E0000
> 24 dmsc 0x701FC000 0x701FFFFF sproxy_private,rwcd
> 24 dmsc 0x4407C000 0x4407FFFF sproxy_private,rwcd
> 24 dmsc 0x701C0000 0x701DFFFF everyone,rwcd
>
> So it looks like only 128K@0x701E0000 is firewalled off.
> Will update the patch.
>
> This makes me wonder why ATF is being moved to 0x701a0000-0x701c0000
> leaving a hole at 0x701C0000-0x701DFFFF?
>
>
The reason for leaving the hole at 0x701C0000-0x701DFFFF was because
initially there was a bug in SYSFW which lead to the usage of the above
region too by it. However, this bug was recently fixed and the the above
region can be used for ATF.
Thanks,
Aswath
>>
>>>
>>> Without this certain drivers using SRAM as generic shared memory pool
>>> may end up being allocated memory from this range and will lead to boot
>>> time crash when the reserved range is accessed (due to firewall
>>> violation).
>>>
>>> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
>>> ---
>>> arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
>>> index f1c42ef05e52..77b88e536534 100644
>>> --- a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
>>> +++ b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
>>> @@ -16,6 +16,10 @@ oc_sram: sram@70000000 {
>>> atf-sram@0 {
>>> reg = <0x0 0x1a000>;
>>> };
>>> +
>>> + dmsc-sram@1c0000 {
>>> + reg = <0x1c0000 0x40000>;
>>
>>> + };
>>> };
>>>
>>> gic500: interrupt-controller@1800000 {
>>> --
>>> 2.31.1
>>>
>>
next prev parent reply other threads:[~2021-06-14 4:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 14:06 Vignesh Raghavendra
2021-06-09 15:26 ` Lokesh Vutla
2021-06-11 18:29 ` Vignesh Raghavendra
2021-06-11 19:03 ` Nishanth Menon
2021-06-11 19:16 ` Nishanth Menon
2021-06-12 7:21 ` Vignesh Raghavendra
2021-06-14 4:48 ` Aswath Govindraju [this message]
2021-06-14 14:28 ` Nishanth Menon
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=36ff3c65-2f5e-2997-9fb5-a5e8d3230a75@ti.com \
--to=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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®