The bootloader/TF-A configuration we're using is based on the 4.19 CIP
kernel that Renesas released. TF-A, we allocate some memory for the
lossy compression and this memory is not available for Linux. I'd
prefer to not have to use a special TF-A for the mainline Linux, but
what appears to be happening is that Linux doesn't know about the
reserved memory, so memory corruption happens.
The Renesas CIP kernel uses the following to define the space
/* device specific region for Lossy Decompression */
lossy_decompress: linux,lossy_decompress@54000000 {
no-map;
reg = <0x00000000 0x54000000 0x0 0x03000000>;
};
Then uses the following to carve it out so Linux doesn't think it can use it.
mmngr {
compatible = "renesas,mmngr";
memory-region = <&mmp_reserved>, <&lossy_decompress>;
};
Unfortunately, renesas,mmngr doesn't exist upstream.
I thought about changing the memory node to break it up, but it seems
like a hack.
What is the best suggestion for blocking this memory area from Linux
while still appearing to show the full memory size?
adam
