[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210611191640.lczsliyzasjie6lm@dismantle>
Date: Fri, 11 Jun 2021 14:16:40 -0500
From: Nishanth Menon <nm@...com>
To: Vignesh Raghavendra <vigneshr@...com>
CC: Rob Herring <robh+dt@...nel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am64-main: Add SYSFW reserved ranges
in OCRAM
On 19:36-20210609, Vignesh Raghavendra wrote:
> Last 256K of OCRAM (256K@...01c0000) 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?
>
> 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@...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@...00000 {
> atf-sram@0 {
> reg = <0x0 0x1a000>;
> };
> +
> + dmsc-sram@...000 {
> + reg = <0x1c0000 0x40000>;
> + };
> };
>
> gic500: interrupt-controller@...0000 {
> --
> 2.31.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists