Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH] arm64: dts: ti: k3-am64-main: Add SYSFW reserved ranges
 in OCRAM
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>
References: <20210609140604.9490-1-vigneshr@ti.com>
 <81e61d1a-efde-0bff-719c-607752bfdbc1@ti.com>
From:   Vignesh Raghavendra <vigneshr@ti.com>
Message-ID: <dd2261dd-8285-5a47-526f-5b9e7056aa84@ti.com>
Date:   Fri, 11 Jun 2021 23:59:08 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <81e61d1a-efde-0bff-719c-607752bfdbc1@ti.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


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