diff options
| author | Stefan Eichenberger <stefan.eichenberger@toradex.com> | 2024-02-23 14:57:35 +0100 |
|---|---|---|
| committer | Francesco Dolcini <francesco.dolcini@toradex.com> | 2024-02-23 14:24:18 +0000 |
| commit | 756e3199ba82d68ba07e5acf555d13aaa1da3da1 (patch) | |
| tree | d3ad01fc75879464188af2c8e2da1c1ce5a53c89 | |
| parent | 167b8e8e0f8bb7638eb065d72012a2fd76a19a21 (diff) | |
arm64: dts: imx8mp-verdin: overwrite alloc-ranges property
With commit 1263f108fb28 ("arm64: dts: imx8mp-verdin: fix cma memory
region") we introduced a new problem for modules with more than 3GB of
RAM. The VPU driver Hantro is currently unable to cross 32bit
boundaries. However, since the cma region is at the end of the RAM, we
have crossed the boundary for modules with more than 3GB of RAM. We set
the alloc-ranges property to the same value that is used in imx8mp.dtsi.
We do this to be consistent between Verdin iMX8MM and Verdin iMX8MP.
Upstream-Status: Inappropriate [other]
We use the kernel configuration to define the CMA size and don't use the
linux,cma node in the device tree. However, we need to verify that the
upstream hantro driver can handle 64 bit addresses.
Signed-off-by: Stefan Eichenberger <stefan.eichenberger@toradex.com>
| -rw-r--r-- | arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi b/arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi index c861aed5cdcf..9d6298748c4d 100644 --- a/arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi +++ b/arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi @@ -193,7 +193,7 @@ linux,cma { size = <0 0x20000000>; - /delete-property/ alloc-ranges; + alloc-ranges = <0 0x40000000 0 0xC0000000>; }; }; }; |