From: Vignesh Raghavendra <vigneshr@ti.com>
To: Lokesh Vutla <lokeshvutla@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: Fri, 11 Jun 2021 23:59:08 +0530 [thread overview]
Message-ID: <dd2261dd-8285-5a47-526f-5b9e7056aa84@ti.com> (raw)
In-Reply-To: <81e61d1a-efde-0bff-719c-607752bfdbc1@ti.com>
On 6/9/21 8:56 PM, Lokesh Vutla wrote:
>
>
> On 09/06/21 7:36 pm, 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.
>>
>> 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>
>
> You might want to re-base on top of Aswath's patch updating ATF address. Otherwise:
>
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
>
Actually, this patch should go in before Aswath's patch as moving ATF
location around exposed issue of drivers getting memory allocations
overlapping SYSFW reserved ranges
Regards
Vignesh
next prev parent reply other threads:[~2021-06-11 18:29 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 [this message]
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
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=dd2261dd-8285-5a47-526f-5b9e7056aa84@ti.com \
--to=vigneshr@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@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®